Dictionary Override vs Business Rule vs Client Script vs UI Policy/Action

VikasY
Kilo Contributor

We have a dictionary override set for the incident state to "Read-Only". This basically greys out the state of the incident and even admins can not modify the state without reversing the dictionary override first.

I tried writing a UI Policy with an onLoad script to check if the logged on user was admin and set the field to "Read Only" to False.

Question 1: Is it true that Dictionary override setting takes precedence over things like Business Rules, Client Scripts etc. ?

Question 2: is there a way to apply an exemption to a dictionary override, so atleast admins or a group of users can change the state of incident?

My last resort is to create a UI Action button for the incident and use that to change the state. UI Action button permissions can be controlled, so I'm fine there. If anyone can provide some guidance around the 2 questions above, I would appreciate it!

 

1 ACCEPTED SOLUTION

Allen Andreas
Administrator
Administrator

Hi,

Yes, dictionary is like the "law" of that field. It's the top rule (outside of ACL). I don't think there's a way to provide an exemption, but this all sounds like it should be handled by ACL. So if you go to your ACL's for Incident table and modify the write ACL that's ther now for state field, then add admin as role, thus it'll be read-only for others.

Please mark reply as Helpful/Correct. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

View solution in original post

4 REPLIES 4

Geeky
Kilo Guru

Only solution to your problem is to create a client script or UI policy on the required table and make the fields readonly when a form loads or based on your requirement. In the condition mention the roles != admin so that it does not apply to admin, hence admins can modify the data.

Allen Andreas
Administrator
Administrator

Hi,

Yes, dictionary is like the "law" of that field. It's the top rule (outside of ACL). I don't think there's a way to provide an exemption, but this all sounds like it should be handled by ACL. So if you go to your ACL's for Incident table and modify the write ACL that's ther now for state field, then add admin as role, thus it'll be read-only for others.

Please mark reply as Helpful/Correct. Thanks!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

VikasY
Kilo Contributor

thank you guys. That's what I was afraid of. This answers my question. Much appreciated for the quick response!

Hi, no problem.

If you can and if my response provided the information you needed and guidance that you'd like to take forward, please mark my reply as Correct so that others can find this information.

Thank you!


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!