Why is it not supported? Is it to be retired in the future?
I use a similar function $(if CurrentUserRole() != "Admin" then true else false) for role based permissions when showing buttons in the toolbar. I guess the field could also be set in the roles and permissions if you could go along the role based route?
- You have to read the warning message very carefully when saving the business rule. It may not apply. I know it says not supported in workflows (which makes sense because there is no active user) but for read only rules with a form, there is an active user.
- How seriously do you want to stop them? If the field is audited and you want to prevent accidental changes (vs deliberate), then use the read only logic on the form. It does not prevent a user from bypassing the rule with a quick action, but that is where your audit trail would show who had edited it.
The fact that it is completely custom and unsupported came from HEAT Software support. I've been cautious with customization lately as new patches/hotfixes to broken code in HEAT over this past year have severely crippled our system.
I thought about the role based route but in my organization, we have multiple teams using the same roles. I decided to stick with the expression I posted originally. It works for now.
Thanks. Our users are unable to create or edit quick actions, I reserve that for myself.