You can choose an action type that works in a Turnkey web-client table and avoid placing disabled ViewModel/Context actions in table rows.
Action behavior in web-client tables
When you place an action in a table on a screen, its availability depends on the type of action.
| Action type | Behavior when placed in a table | Example use |
|---|---|---|
| Class action | Works as expected. Its enabled or disabled state is evaluated in the same way as when the action is used elsewhere. | A row-level command such as Approve for the object represented by that row. |
| Action with EAL in a ViewModel | Works as expected, even when the EAL is not linked to an action. Its enabled or disabled state is evaluated as it is elsewhere. | A table command whose behavior is defined by EAL in the ViewModel. |
| ViewModel/Context action | Displayed as disabled in tables in the web client since 2020-09-27. | Do not use this type for an action that must be invoked from a table row. |
Choose an action for a table
Use the following rule when designing a table command:
- Identify whether the command operates on the object represented by each row. For example, if each row represents an order and the command approves that order, use a class action.
- If the command is implemented as EAL in a ViewModel, an action with EAL can also be placed in the table.
- Do not place a ViewModel/Context action in the table when users need to invoke it there. In the web client, it will appear disabled.
The enabled and disabled state of class actions and actions with EAL follows their normal action rules. A table does not make either of these action types permanently enabled.
Example: row-level order command
Assume a table lists orders and each row represents one order.
- Use a class action for an operation on that order, such as Approve. The action is available or unavailable according to its normal conditions.
- Use an action with EAL in the ViewModel when the operation is defined in the ViewModel through EAL.
- Do not use a ViewModel/Context action as the table-row Approve command. Since 2020-09-27, the web client renders that action disabled in tables.
Scope of this limitation
This page describes action placement in tables in the Turnkey web client, including the AngularJS client. It does not describe action behavior in the Windows WPF client.
For list selection, single-row behavior, multi-select configuration, and actions that operate on selected rows, see Documentation:Tables and Grids. For search result size, filtering, pagination, and server-side ordering, see Documentation:Tables, search and ordering.