It would be very helpful to have picklists for Groups that are created that is similar to the Users, ALL by Name picklist. This way, the users would only have to be maintained in the Group and not in a manually entered picklist as well.
Is there a chance that the same ability to move multiple dates out at the same time that is found in the milestones tab, can be replicated in the Project Management tab? With the complex way we are using PLM360 to support project management we cannot utilize the milestones tab.
That said we really like the ability to move multiple task dates out without having to change them one by one.
It would be very helpful to have following workflow features:
1) Export a workflow from one enviornment to Import to Other.
2) It would be nice to have export and import done with all dependencies like Permissions, scripts etc. if not then Import shall display messages for missing dependencies and allow import only if all dependencies are in place. Like the permissions, roles and scripts.
Also on the workflow summary there should be an option(button) for complete information where each Transistion information including Condition script, Validation Script, Action Script, all other selectable options along with Escalation setup.
This would give user to copy this information and version control/document it. Also it can be compared against other enviornment setup.
As of today it is very easy to miss a setting when you are copying your workflow from Dev to Prod.
I've run into a problem where I created a "Basic Workspace with workflow" but did not immediately define any workflow. I'm now 100 records into using the workspace and ready to define a workflow. But I've learned that any workflow I add will only apply to new records, not be retroactive to pre-workflow ones. This is counterintuitive as changes to workflows immediately apply to all records regardless of when they were created. I consider "adding" a workflow to be a "change" and should also apply to all records. Now I have some records with workflow and some without... in the same workspace.
My suggestion is that when a “Basic Workspace with workflow” is created it is pre-populated with at least one default state. This will make it clear when creating records that the workspace is intended to have a workflow and to make it possible to fully define the workflow later on.
Right now you can only use purge on the workspace to remove all the data in that workspace, one issue we are facing is deleted items are appearing in search and other users are finding ways of navigating to them. So basically any user error or duplicate that we deleted sits in our data forever and crops up to cause confusion.
So I am looking for a way to truly hide deleted items, their previous releases, and all the relationships they may have (project, BOM, relationships...). The two options I can think of would be purging those deleted items from the workspace or possibly creating a deleted item view permission.
One very interesting feature from NetSuite is the Field Help. Every field within every form/record is clickable and triggers a small pop up with a short help outline or instructions on how to access/modify. This field help can be configured by the admin for custom fields.
It would be great to add the capability to specify help and instructions on PLM 360 fields and would even allow clients to implement their processes within their workspaces and forms.
Streamline the process for setting up administrator rights including better documentation regarding the Administration [SYSTEM] group and the workspace-agnostic Special Permissions (Administer Users, Setup Administration, and Share Reports). It took me a while to figure out exactly what gives users administrator rights, and I'm still not exactly sure what the pros/cons of the system-protected group is vs using those workspace permissions. It's confusing and illogical to include the administrator permissions in the workspace roles.