Overview of Field Security
Field security lets you indicate that certain fields on a screen either cannot be updated or cannot be seen by users with a particular role. For example, although a user role may have the appropriate permissions to display Customer Invoice Modify, you can prevent users in that role from updating the invoice total field.
Field security controls the ability to modify the UI through the Design Mode features. Fields that are restricted through field security cannot be modified using the UI customization features. Conversely, fields that are not restricted in field security can be customized—including disabling or hiding the field—by using the UI customization features.
Field security can be applied to fields that are delivered with the system as well as user-defined fields.
Field security is defined using any combination of business component, activity, role, and field. A system administrator can specify field access rules that define either rights or limitations:
• Component and field. Define a right or limitation for all users in all activities.
• Component, activity, and field. Define a right or limitation for all users in one activity.
• Component, role, and field. Define a right or limitation for at least one role in all activities.
• Component, role, activity, and field. Define a right or limitation for at least one role in at least one activity.
For each combination, only one rule is possible. The more specific a rule is, the higher its precedence over other rules. For example, component and field is the most general rule; component, role, activity, and field is the most specific rule.
Important: In order for any changes to the field security settings to take effect, users must exit from any .NET UI sessions in use while the changes were implemented and then restart the .NET UI.