R2.2-Access Status -Read-only Flag issue

Last week, Aditya reported an issue while executing a program that was using a macro from Oncology_stdutil Standard Purpose. On investigation, we found that the system was not able to handle the way we had changed the Access Status of Oncology TA. Following is the details of the issue:

Description:

The system is not setting up the ACLs appropriately if the Access Status of any context (TA, Compound, Drug Program, Candidate Code, Study, Integration) or Purpose or any individual Folder or Artifact is changed from Open to Restricted or Restricted to Open when the flag for Read Only for all Users is set to 'True'.

Workaround Solution:

Change the Access Status of any Context, Purpose, Folder or Artifact to 'Restricted' without keeping the flag for Read Only for all Users as 'True'. Please note that this flag is set to 'False' by default. If required, once the Access Status is 'Restricted', the user can change the Read Only for all Users flag to 'True' as a separate operation.

Change the Access Status of any restricted Context, Purpose, Folder or Artifact to 'Open' only after having the flag for Read Only for all Users as 'False'. If the context had the flag for Read Only for all Users as 'True', please change it to 'False' as a separate operation before changing the Access Status to 'Open'.

Fix: ACLs should apply properly when the access status is updated keeping the “Read-only” as True.