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.
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.
I'd love to see more robust script management. Ideally I'd like to see the ability to officially version or rev scripts. In addition to the Save button, you could add a button for Version. This would store the script in its current state with the appropriate verison number.
In addition, I'd like to review previous versions of the script and have the option of making a previous version the current version.
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.
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.
It would be great to have an admin permission that allows users to edit fields that are set as 'non editable' in the field definition. It is very time consuming when testing to have to navigate to the workspace manager and change the field properties. It would also be a useful feature to have as an administrator to make changes and corrections easily.