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.
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." .
A function where a "desktop folder" can be added inorder to add/view documents from the desktop/finder directly into PLM360. The folder to be added should be connected to a certain workspace, where the user can chose which workspaces should be able to "share" information.
The folder should be a direct connection through the username and password from the user, where permissions should be added depending on what role the user has.
Similar to dropbox, but with the added finess of PLM360.
We have an action script running to sort out the row order of a workspace grid. However, the script will only run when we edit the Item details. This method of sorting the grid rows is a little tedious. It would be great if the script would run by simply editing the grid.
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.
Based on a value or status of a field, the ability to take an action based on changes to a field value.
Example, moving to the next step in the workflow. In the process to create a product name, the Person A asks Person B to create a name and get it approved by Legal. If Person B approves a product name, we would like the workflow to automatically advance to the next stage based on the "approved" status so that there are less clicks for the user and less chance of forgetting to advance the workflow on the Workflow Actions tab.
Form validations on the client side can save the user's time by pointing out errors in the form as they are entered or auto-populating values based on other values in another field.
An example is on a pricing form where there some data relationships that should not be broken and internal logic would be enabled based on values the user selects. If a user selects value 1 from picklist A, then picklist B would show a different set of values than if the user selected value 2.