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.
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.
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.
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.
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." .