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.
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 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." .
byAsingh511-14-201210:52 AM - edited 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.
byjbarnett03-12-201308:01 AM - edited 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.
If a user imports a large number of new items (not BOM items) and realizes a mistake has been made. Now the user has to delete all these item through the UI, which is very painful. The user would like to perform a mass delete with a list of specific items.
It would be nice for the user to use the existing match functionality in the import tool, with the option to delete existing records on match.
I think it would be very useful to be able to "pre-filter" a pick list or linked pick list, using a pre-filtering text field, which can be editable, visible, or hidden. For example, I have a linked pick list in a "Product Family" workspace that points to my Items and BOMs workspace. I want users to be able to select one or more records from the Items and BOMs workspace, but I want them limited to a particular prefix (for example, we use 850- prefix for our SKU's). In my Product Family items and details tab, I could create a hidden field with the text, "850", which could be used to pre-filter the linked pick list to only show items starting with "850". When setting up the pre-filtering rules, it would be important to be able to specify the filter condition...starts with, contains, does not contain, etc.