It would be great if we could have default folders inside the attachments tab. We are going to have certain folders every project and having the user create them everytime won't be consistant 100% of the time. Also, if a file is attached, but the user needs it in a specific folder they are not able to drag and drop that file down into the folder. If they upload an attachment and they want the name different then what it was put in they have no permission to edit the file name. Case in point, the attachment tab has a lot of work that needs done to make it more effective.
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.
Working through the creation of an Advanced Print View is a tedious process. It's nice to have the Advanced Print View open on one page, and then the actual Print page open in another. Typically this requires a constant refresh of the Print page to see the affects of changed settings on the Advanced Print View.
Currently, on the Advanced Print View when you press the Save button it takes you back to the print views list. Then you need to press Edit for the print view to go back into the view for editing. Then the cycle happens again, ...
This is very tedious.
On the Advanced Print View, it would be nice to have an extra button Save & Close. This would save the view and then close back to the views list.
The existing Save button should be repurposed so that it simply saves the view and leaves the users in the edit mode.
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.
When an item is spawned by a workflow there is an option to link link to the spawned item to the "spawned by" item. There should be an option in the spawing item to automatically link to the item it spawned. I know this can be done with abit of scripting but I think it really should just be a check box/option.