Allow certain users in a project to update an out-of-date share. This would allow fewer users to be in a Project Manager role. This would be limited to weather or not the user is assigned to the Collaboration Manager role inside the context where the object resides in PDMLink.
Yes, I completely agree. Updates are always available to the person who initiated the share and only members of the Project Manager role in the specific project team. This is a high priority customer request and something we always have at the top of the project list for a new release. Rather than just creating a new role in the team with this single configuration, we'd like to update the underlying code to support the creation of any type of role giving everyone the ability to create the role of their chosing. I cannot share a committed release or date for this functionality yet, but will continue to make it a priority and get it implemented as soon as possible.
What would be better would be to allow the items that have been added to a project to be automatically updated when the PDM items are updated. If the item has been shared and the project has the security given to access it, why shouldn't they always have the latest version available to them? Or at least the ability for that permission to be granted if a company so needs it.
Yes! and by Preferences at the Org and Project level to allow a global default with possibility to override for a specific Project.
The current methodology uses an "internal" baseline to control the items included in the "share". The update process uses the internal baseline to collect updates and dependencies. This works for CAD Docs and Parts today, but not for Documents. If the Shares are automatically updated, would you want the dependencies collected also?
I have always thought it would be cool if the initiator of the Share was sent a notification when the item they shared was updated in PDM with an option to update the share in its respective project(s). You can do the notification with Subscriptions today, but you still need to go to the project and initiate the Update.
If you have feedback, please share.
It would be great to capture some of the use cases and requirements regarding shared content in a project. For instance, I know some customers really like the current capability becuase it allows them to "revision" control the shared content where other customers just want to always have the latest version available in the project.
When ProjectLink is being used for realtime development collaboration with external partners; it would be most beneficial to give the external partner access to some items they may use in their designs. And keep them at the latest version if an authorized change takes place.
Without bothering a 'GateKeeper' to keep the information constantly up-to-date.
The 'Gatekeeper' has more important things to do like make sure that the actual work they need is getting done and checked instead of making sure some referenced part is at the latest version.
Most of the time the reason for going outside is because the team is trying to get the job done with lean resources. Adding housekeeping steps is not always needed in every organization and the software should be flexible enough to work with different use cases.
Currently, there are plans for the 11.0 release to introduce capabilities to automatically update your shared data to projects based on a schedule. With this new capability it should be possible to specify on a project by project basis whether it should be auto-updated.
This is welcome news. Do you know if there will be any conversation in the T.C.s on it?
I don't believe there is a session on this topic during the TCs this year. However, if you would like to chat about it certainly stop by for a visit in the exhibit hall.
Automatic update of PDM Shared objects to a project has been released with Windchill 11.0 F000.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.