Team,
I have a very secure Windchill product. The general population can only Read and Download one revision of any object.
We accomplish this by setting up a "Public" folder where the general population has read and download.
We also set up a "Private" folder with a custom domain and only the Product Managers have access.
When a new revision gets "Released", the Product Manager moves the old revision out of the Public folder and puts it back in Private, The Product Manager also moves the new revision from Private to Public. While this is labor intensive, it works exactly as desired. We do this because we have problems with users building to the wrong revision.
In the case of a CN Task, nobody except Product Manager can see the new revision. The new revision is still "In Work" or "Under Review" and it's hidden in the private folder.
I'm looking for a way to have the Change Activity workflow extend Read and Download permissions for the Resulting Objects to the Reviewer Role, but only when the Review step is being worked. They can't see the resulting parts or documents unless they are reviewing them.
The LifeCycle template for the Change Activity can change permissions on the Change Activity, but not the Resulting Objects. I thought about putting robots in the workflow to add Ad-Hoc permissions to the resulting objects just before the review step and another robot to remove the Ad-Hoc permissions just after the review step.
Has anyone done anything like this? Any suggestions would be appreciated.
