Process lock on attribute and page refresh
search cancel

Process lock on attribute and page refresh


Article ID: 140926


Updated On:


Clarity PPM On Premise


Is there a way to refresh the screen after hitting save?  A process triggers on update and has a step to lock an attribute.  But the attribute isn't locked yet after the save is performed and the user can change the attribute value again and save it.  If the view is refreshed, the attribute is locked and can't be changed.


Release : All supported Clarity releases


What we suggest in those cases is to educate the users to hit Submit instead of Save. So say a project manager creates a project, updates the field that triggers the process and then they have to hit Submit. This will close the project and they will be back on the Project List page and when they reopen the project the other field will be locked.

This is our usual suggestion.

The other thing that you could do is to lock this field on Create with another process, so nobody will be able to overwrite it.