Empty State field with custom role

SecOpsIM
Tera Contributor

Hi,

 

I created a custom role in sn_si for a special user group.

I was able to fix all the issue you get when you create such a role. However, one issue is driving me crazy:

 

I created a ACL that the new rule can read the State field. Everything works fine. In a next step I created a ACL that the role can write the State field and the fiel goes blank. No current state and no dropdown. As soon as i remove the write ACL, the current state gets displayed.

 

I already checked that the new role can read the date in the sys_choices list. Furthermore, other choices field works in the same form.

 

Any ideas?

 

Thanks,

Steffen

2 REPLIES 2

Tanushree Maiti
Tera Patron

Hi @SecOpsIM 

 

  • Validate Table level ACL : Ensure your custom role has write access on the base table level (like, sn_si_incident.None).
  • Check for Field level ACL: If you haven't already, add a specific write ACL for the State field (like, sn_si_incident.state) and assign your custom role to it

If the ACLs are properly set and the field is still going blank,

 

  • Impersonate a user with the custom role, navigate to System Security > Debug Security > Access Analyzer, and verify if the user passes the write access for the state field.
  • Navigate to UI policies &  search for policies targeting your table with State. Check UI policy actions.
  • Right-click on the State field label, select Configure Dictionary, and look for any Dictionary Overrides that restrict the field for your roles.

Hi,

thanks for the answer. 

I already created a Write ACL for the usergroup for "sn_si_incident", "sn_si_incident.*" and "sn_si_incident.state".

 

 Access Analyzer shows passed for read, write and some others. Furthermore I could not find any Overirdes or UI policy touching this.

 

Thanks,

Steffen