Action Assignment record conditions

[mattburgess]

In Action Assignment[sys_declarative_action_assignment] record there is a tab called Conditions

When creating a record for Form Action type 

In this tab there are the following fields

• Script Condition - Server condition that must be met before the action is displayed.
• Client Conditions - Model field values that must be met before the action is displayed.
• Record Conditions - Record condition that must be met before the action is displayed.
• Required Roles - Specifies the roles the user must have to view the action.
• Requires create access - Specifies the user must have create access to view the action.
• Requires read access - Specifies the user must have read access to view the action.
• Requires write access - Specifies the user must have write access to view the action.
• Requires delete access - Specifies the user must have delete access to view the action

Does anyone know whether the Action Assignment can have a combination of conditions on a record i.e. Server Conditions and Record Conditions and if so does anyone know what order the conditions are evaluated?

[Sandeep Rajput · Accepted solution]

@mattburgess 

Yes, in Action Assignment (sys_declarative_action_assignment) records, it is possible to use a combination of conditions like Script Conditions, Client Conditions, and Record Conditions. These conditions work together to determine whether an action is displayed. Here’s an overview of how they interact and the evaluation order:

The system evaluates these conditions in the following order:

1. Role and Access Conditions:

Before anything else, the system checks if the user has the required roles and access permissions (create, read, write, delete).
If these are not met, further conditions are not evaluated, and the action is not displayed.
2. Script Condition (Server-Side):

The server-side condition is evaluated next. If it returns false, the action will not be displayed, regardless of the client or record conditions.
3.Record Conditions:

If the server-side script condition passes, the system evaluates the record-level conditions (table-based conditions). These conditions must also evaluate to true.
4.Client Conditions (Client-Side):

Finally, the client conditions are evaluated on the client side. These conditions depend on the current field values or other data available on the form.