Problem Coordinators cannot associate closed incidents to Problems in the SOWDescriptionProblem Coordinators are no longer able to relate closed Incidents to Problems in the SOW due to a change in the script include "related_list_edit_helper" (sys_id 052c5b0f7707330022f7f4d268106131) from using GlideRecord to GlideRecordSecure. The MRA in the workspace lists closed incidents for linking but then ACLs block the writing of the record. This is not the case in UI16 as it uses a different script include. It's the extension of PRB1930428 to avoid the issue occurring due to the existing field-level ACLs on the incident table that lack a condition to allow the write operation when an incident is not in a closed/cancelled state, the problem coordinator can have write access.Steps to Reproduce 1. Impersonate a user with the **problem_coordinator** role.2. Open a problem in UI16 and the incident list in another tab3. In the incident list, find a closed incident that was last updated by 'system' and open it4. Check the 'Related Records' section of the incident form and see the 'Problem' field is read only.5. Return to tab with a problem open. In the 'Incidents' related list of the problem record click add , find the incident you were looking at in step 3/4 and add it.6. Go back to the tab with the incident open - Problem field has updated.7. Continue impersonating and try to link a closed incident in the SOW.WorkaroundThe fix has already been shipped to address the issues occurring due to the changes done via of PRB1930428. However, the below ACLs need to be reviewed by the customer and reverted to the OOTB version, and re-activated manually in order to get the latest version:- sys_security_acl_23a1c2bfc3333010a282a539e540dd7b- sys_security_acl_7a693667c3333010a282a539e540dd2c- sys_security_acl_b9193267c3333010a282a539e540dd19- sys_security_acl_c941467fc3333010a282a539e540ddedPlease note that the customer can skip the ACLs which are already inactive on their instance.Related Problem: PRB1941995