I feel there is a need for significant improvements to the project management tab. I have been using it for a while and I have a number of issues. Many of them have bee reported here already (e.g. ability to add columns). However there are some fundamental changes required to make this tab useful for managing anything other than simple projects. Some other issues are;
- it is essential that reports can be run on projects
- milestone dates must be able to be changed and modified through the project UI (regardless of whether they are linked tasks or not)
- milestones and milestone status should be visible in the gantt chart
- Selectable colours
- etc etc etc
I'm a huge advocate of PLM 360 but currently the PM tab is letting it down. I've used another web based project management system before that I think you guys should have a look at. Please PM me for the URL if you're interested.
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.
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.
byAsingh505-31-201310:52 AM - edited 05-31-201310:59 AM
Currently any attachment that is uploaded on PLM360 for a specific item can be downloaded from a user if the correct permission is granted.
If it was possible for a user to only have the preview functionality in the attachment tab permissible, that would be very beneficial in regards to security. This would allow users the access to view the attachment without having the threat of intellectual property being distributed.
Below is an image of the attachments tab. If the links circled below were removed or hidden, that would provide a suitable solution were the user wouldn’t be able to download the attachment.
Also if it were possible to view a larger preview of the attachment, that would enhance the user experience.
I would like the ability to export the data from a workspace view rather than having to create a report first. Second best would be to be able to create reports that mirror workspace views (maybe even keep them linked so that a linked report always matches a particular view).
Looking for the ability to deliver content (Blog, Announcements, Reports etc) for users on their home page. Perhaps a section that is admin controlled and can be filled with mutliple types of content. Could fit in with the social concepts kicked around, however then it would require the Admins being able to set users to follow this content. We are facing the issue of keeping a lasting place of issue resolutions, announcements, and updates for our users inside of PLM 360. We could do it through email or in a workspace, but both lack to this would be visibility upon opening PLM 360.
There are three workspace permissions to view items, historical releases and working versions. They work together as below.
It would be better if there was a way to limit users to only see the latest release and also working versions. We'd like to prevent users from getting older releases and yet still be able to edit working versions while creating new documents. This could be accomplished if "View Historical Releases" and "View Working Versions" were independent instead of working together.
View Historical Release
View Working Versions
Can see the current version
Can see the current version, and old versions
Can see the current version, old versions, and the working version