one or few properties editable based on role and access group on UI sections
there is requirement to show as few properties editable or read only to user based roles on UI
tried with Attribute based controls but it is restricting / controlling class level need only specific property to be read only or editable based on roles of user
please can you share or update the approach to implement with attribute level controls.
Bluevoir Technologies India Private Limited
IN
Create a section with properties you want to show as editable or read-only and include this section in the main section. you can configure when a rule in the editable options on the Presentation tab of an embedded section layout.
Masking Technology
NL
There are a few possibilities to get this done and it depends on the number of fields they cannot edit and where they are on the screen.
The easiest way to force fields to be read only / hide the fields, is when they are all located on the same section and that section is included in another section. When a section is included in another section, the General tab has a checkbox for associating privileges to the included section.
In the example above, when the user has the privilege Quality Assurance, the section is displayed. If not, the section is not shown. The same for the update privilege. If the user has the privilege Never the section can be updated. If not, the section is shown as read only. But be aware, each field on the section needs the Editable options set to auto, otherwise the when condition will take precedence.
There are a few possibilities to get this done and it depends on the number of fields they cannot edit and where they are on the screen.
The easiest way to force fields to be read only / hide the fields, is when they are all located on the same section and that section is included in another section. When a section is included in another section, the General tab has a checkbox for associating privileges to the included section.
In the example above, when the user has the privilege Quality Assurance, the section is displayed. If not, the section is not shown. The same for the update privilege. If the user has the privilege Never the section can be updated. If not, the section is shown as read only. But be aware, each field on the section needs the Editable options set to auto, otherwise the when condition will take precedence.
The second option is to use when rules on the individual fields. The Edit options as shown above can use a when rule, and you can configure those to look at the roles of the user (HavePrivilege / HaveRole).
The option for your solution really depends on the number of fields, and if they are grouped together or not. When I develop an application I use the first option to show screens to the user in read only. The Never privilege exists and OOTB is not assigned to any role. Making it an easy setup for added read only screens. Any buttons on the section keep working though.
When using when rules you have to be aware. If the when rule is false for a user based on role / privilege, the same input field will be editable on the Review harness!