as sometimes we have to have the Workflow Transition to be finished before being able to "play" with item created within Action Script (Add item to BOM etc...), could it be possible to have some step that are acting as robot... it means that it should launch a scipt when this "robot" script is reached...
in case of failure, we can either cancel previous Transition or if successfull, force next Transition to go to the next "manual" Step...
Currently only way to create a script is through UI in PLM360. Even though these scripts reside with PLM tenants they will change over a period of time and have to be moved from one tenant to another(for e.g. Development to Test to Production).
Following are few suggesstions which can reduce human errors:
1) Provide ability to Export and Import Scripts. This provides users a chance to version control their scripts.
2) It would be even better if PLM360 provides a built in version control, where users can revise and activate scripts, compare two versions of scripts but this may be too much to ask for as all these can be accomplished via version control tool.
I feel we need a lookup function in the scripting functions
The basic Idea would be to duplicate the current function for linked picklists and leverage the benifits of derived fields and filtered picklists.
The script function would simply return a dmsid's or null and be able to search a specified workspace for records that match specified field/values. The return could be an array of the dmsid that could be utilized to then load the found dmsid for use in scripting access to that record for adding or extracting information.
Workspace A = tasks with two fields to identify that record: Project# (Linked Picklist) and Task ID, A third field Task Type, UDP of values (type a, type b etc.)
On Workspace B you have two filtered picklists based on Workspace A (you could use Pre-Filter on the Picklist to restrict by Type).
Use the values selected in the filtered picklist fields in a script lookup function that returns all matching dmsID from WS-A.
Using looping & load item you can then process those id's to add or extract info.
There have been several support forum discussions on this subject and thought it needed to be added to the Idea Station. Help this along by giving Kudos.
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.
It seems useful (to me) to be able to control section expand/collapse within a script. Tying that to workflow steps - expanding / collapsing as I move through the stages of a workflow - would be able to expedite actions and focus users.