Allow fields to be editable after the incident is closed using ACL

[SamuelTse]

I was tasked to allow work notes field to be editable after an incident is closed. I read a few postings here and believe the following logic would work:

1. Allow - incident.[none]
2. Deny - incident.*
3. Allow - incident.work_notes

However, it doesn't work for me because of the existing ACLs, particularly the two incident.[none] write ACLs. I tested this theory in another custom app that I made and it works fine, just doesn't work for incident.

Any idea what needs to be done to have work notes editable after the incident is closed and not affecting the existing ACLs?

Thanks,

Sam

[Subhajit1]

Is your custom app table extending the task table, if not, testing on custom app table would not replicate the scenario, if yes, you are missing something(Security rules) on the Incident table.

Also, set the condition section on the 3rd ACL you write that State is closed.

[SamuelTse]

Hi Subhajit,

The custom app is a standalone app, not based on task table. I added the condition to my third rule but still a no-go:

I tried both state and incident state, it makes no difference. What else do I need to set on the incident table?

Thanks,

Sam

[lokeshreddy23]

I have noticed that you have unchecked admin override, can you check if you have added a role in the related list.

Do not modify existing acls. Create a copy of it and test.

[Subhajit1]

As Lokeswar pointed out, you can either impersonate a user with ITIL role or click on Admin overrides and see if the accesses works properly.