I'd like the ability to run a script by pushing abutton in the workspace item and not have to rely upon a state transition to do so. There are times where I want to create an item but use data from an existing item (the one I'm in at that time) and then link them together via the relationships tab. I want to do this without a state change (because state change would not be needed to simply link to items). I realize I can change behaviors to run a script upon creation that could do much of the same. It just makes sense to NOT to have to navigate away from where I'm at and then remeber what I want to link to. I'm all about automation.
on 08-02-201212:23 PM - last edited on 08-02-201212:25 PM |
It is often both difficult and tedious to manually create relationships between different workspace items (as the picture below illustrates). It would save a lot of time to be able to write scripts to automatically add relationships between workspace items.
Even tying the ability to add relationships into the function createItem('WS_WORKSPACE_ID') would be a huge time saver.
We need access via the Server Side Sripting to both the BOM Tab & Sourcing Tab.
I believe there are several support threads as well as Ideastation references to this functionality but I felt we needed a clear Idea Post for this functionality.
Similar to the new object record item.workflowitems recently added we need to have information contained in the BOM & Sourcing tabs for use in scripting.
An example would be having an assembly shown on an Sakes Quote Grid and a workflow that would explode the BOM children of that assembly into the grid of an RFQ and access the default supplier to create a master RFQ for cloning quoting purposes.
Ideally this would be read/write access for back feed updating of costing etc.
We would like to be able to narrow down a linked picklist for a certain criteria.
Example: We use Product ID as a unique identifier for products. In other workflows, we will link a picklist of Product IDs to a form so that we can assign more attributes to the product. Product ID can have a status of "Assigned," "Orderable" or "Retired." We would like to pre-filter a picklist of products to show only those that are in status "Assigned" but not "Orderable" state. There is no current client-side scripting available today.
Only possible by "chaining" workspaces. Create a new picklist when the item changes status, e.g., when a Product ID is first released, spawn record in another workspace with the narrowed-down population of "Assigned." .
on 11-14-201210:52 AM - last edited on 11-14-201210:53 AM |
When using the import tool, performing a bulk import of values into a "single selection" linking picklist is possible. Unfortunately I cannot select a "Multiple Selection" linking picklist it in my import to do the same thing.
This feature is very important for our company since it would allow us to show our linked product items in one specific field, as opposed to having multiple "single selection picklists"--which doesn’t make a clean visual.
The data I have is in a excel format. With over thousands of entries, having the import tool to bulk import the linking picklist values in the multiple selection picklists would allow me to provide my tenant with the information it needs efficiently and visually appealing.
Conditional form-building in a workspace with workflow. We would like to be able to change a form layout based on a classification. Classification is the capability where we get different fields in a form for different scenarios, for example, in pricing.
The pricing attributes necessary for a product for a price list effective period can change depending on the period or type of product. The actual pricing framework and calculation can change as frequently as every month or any ad hoc period as set by the pricing team.
Framework impacts to forms Ex) We work on about price list effective periods at the same time – the form would be different for a different pricing framework
Per Jared: This is not on the roadmap. The team needs to talk to he product manager responsible for classifications for the expected timeline. The workaround is that we would use a more complex form that needs to accommodate the superset of everything that might be needed. The workaround is not ideal.
on 03-12-201308:01 AM - last edited on 03-12-201308:02 AM |
At this time, all views are by individual. There is not a way to globally configure a view globally. Item Views should be able to be modified for an entire team from the system admin rather than from case to case basis.
Adding Project Management items in the Project Management tab is tedious at times. Being able to add project items through scripting would allow an automated procedure involving less time consumption and tedious routine work.