1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Creo and Windchill admin. All users that submit Windchill Changes Notices (CN) and Windchill admins.
2. What version of Windchill are you currently running?
12.0.2.0
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
The out of the box CN UI and workflow do nothing to validate user access to the Resulting Objects so the CN workflow which runs as wcadmin is able to change the state of read only objects as defined in the Access Control Lists (ACL's). Once or twice a month, users are accidentally leaving read only Library objects and/or Creo drawing formats in their CN Resulting Objects and setting them from Released to Obsolete.
Currently, PTC R&D recommends customizing the CN workflow if you wish to check user access. No example java code was provided. They also said that CN reviewers/approvers should be manually checking all the resulting objects but there may be 100's or 1000's of objects.
Proposed Solution: PTC can reference code from the Promotion Request (PR) GUI that gives desired error of 'Insufficient Permission for promoting an object in this context' that prevents the PR from being submitted. If PTC is worried some companies may wish to ignore a user's access when using CN's then a Windchill Org or Site preference could be added with 3 options (error, warning, no warning), but the suggested default would be to check a user's access before allowing them to submit (or click Finish the Change Task menu).
4. What is the use case for your organization?
Prevent users from modifying objects that they have read only access to.
5. What business value would your suggestion represent for your organization?
- Not having to waste admin time changing objects back from Obsolete to Released every month.
- Not having to customize the out of the box CN workflow. Using tasks within CN workflows is tedious for users compared to a helpful error message before clicking submit CN or finish Change Task.
- Better adoption of CNs (currently our users prefer PR).
