Using business process definitions to manipulate read-only fields

Hi Dave,

I've made an experiment - set up a new Role and named it ReadOnlyRole, then specified the custom field Account Status as "Read Only" for that role and assigned ReadOnlyUser to that role.



Then I've designed a Process Definition that sets Account Status to Processed when Account Type is set to Customer


Now, suppose I log in as ReadOnlyUser and edit the Account record - set Type to Customer. In that case, on record save the Status field is updated automatically  -with Process - despite the fact that the Status is non-editable for the ReadOnlyUser user in the UI:



Is that what you are looking for?

Hi Dmytro,

I believe your suggested approach would work.  In the intervening absence of such an idea, I have implemented Chris Raffle's suggestion of a hidden field. Not as slick as your solution but sufficient for my current needs.

Thanks for your interest and efforts.

Regards,

Dave Hodgman

One thing to note about Dmytro Chupylka's solution is that admin users would be able to make changes to the field in the UI since role-based permissions only apply to non-admin users. 

Since admin users are able to adjust Roles, rewise Teams,  and can reach Studio for setting modules fields editable and non-auditable, and then can make them back read-only and auditable - hence, it's hard to withstand to admin's purpose to change the field's value with any no-code configuration - if such purpose arises...

Since admin users are able to adjust Roles, rewise Teams,  and can reach Studio for setting modules fields editable and non-auditable, and then can make them back read-only and auditable - hence, it's hard to withstand to admin's purpose to change the field's value with any no-code configuration - if such purpose arises...