Recently we created a Soft type for ECNs for Initial Release ECNs. These can be initiated by our engineers. In order to do this we had to allow them to create Change Activities. We realized an issue because they had the ability to Modify the Change Tasks, which would also let them modify our Production ECN Change Activities.
I removed the Modify entry from the ACL so that they can Create, but not Modify. I also updated the Life Cycle to remove the additional grants given to the Submitter of the three Modify permissions. This now prevents the users from Modifying Change Activities.
The problem that we now want to address is for our Soft type ECNs, if the Implementation Plan needs to get Reworked, the submitter no longer has the ability to modify these change tasks. I'm trying to come up with an elegant way to do this, but am stumped. In the ECN the Implementation Plan has not been approved, so the Change Activites are still at an Open state. What would make sense would be to have a way to push the the Change Activities to Rework and create an ACL for Rework that would allow them to modify.
Has anybody else run into similar issues, if so how did you address them?
Thanks,
Steve D.
