After upgrading to San Diego, the users with Business Stakeholders role lost their ability to comment and attach a file

[abrouf]

After upgrading to San Diego, the users with Business Stakeholders (built-in role - sn_incident_comments_write) role lost their ability to comment and attach a file.

It worked before upgrade to San Diego release with the following ACLs:

Name-task.comments, record type Write with a role - snc_internal and condition - opened_by=javascript:gs.getUserID()^ORwatch_listDYNAMIC90d1921e5f510100a9ad2572f2b477fe^EQ

Name-incident.watch_list, record type Write with role - snc_internal and condition - caller_id=javascript:gs.getUserID()^ORopened_by=javascript:gs.getUserID()^ORu_caller_alt=javascript:gs.getUserID()^EQ

Any help, input or comments are greatly appreciated.

Thank you.

abrouf

[Harneet Sital]

Hi Abrouf, Did the users lose snc_internal role? Or how exactly these ACLS were giving write access since they aren't available on the ACl roles list? Review the upgrade logs to see what has changed around the ACLS/ROLES. As a workaround you can update the roles on the ACL or create a new ACL based on your requirements. If the answer has helped you, please mark the answer has helpful/correct based on the impact. - Thanks, Harneet

[abrouf]

Hi Harneet,

Thank you for your response. No, users do not lose the role, the role snc_internal is always both in the user's profile and ACLs. Nothing was reported in upgrade logs. 

-abrouf

[abrouf · Accepted solution]

The issue has been resolved by adding the role-sn_incident_comments_write to one of ACLs, the rest of the partially worked ACLs also work what didn't work after upgrading to San Diego release.

[Harneet Sital]

Hi Abrouf, Glad the workaround worked by adding the sn_incident_comments_write to your existing ACLs. May I please request you to please mark the answer as helpful and correct to close the thread. Thanks, Harneet