You can define a UI action for an entity that will happen when pressing a button. There are several types of actions:
In parameter mapping you can define which values will be used as parameters. For sequential workflow action, you can also define a client script which will be executed when the result of the action is delivered.
ATTRIBUTES
There are several attributes that are applicable for all action types:
Form | On which screen will the button be visible. |
---|---|
Panel | On which screen section will the button be visible. You can select only a form, only a panel or both to better specify the placement of the button. |
Roles | Required roles to make the button visible. |
Rule | Required rule to make the button visible, e.g. a condition or a field value in the active record. |
ValueType | Possible values are SavedValue and ActualValue . |
ActionType | Select the type of the UI action. Possible values: - - - - - - - |
RefreshAfterReturn | Not applicable for Sequential Workflow Action. Possible values: - - - - |
RefreshAfterWorkflow | Applicable only for Sequential Workflow Action and Menu Action. Possible values: - - - |
ButtonIcon | You can select a saved image that will be displayed above the button caption. |
Mode | Which records will be affected by the action. Possible values: - - MultipleCheckboxes - The action is related to the selected records. If there are no records selected, the action is not available. Selected records can be used as an input for the workflow (passed as "." in parameter mappings). - Always - The action is not related to the records. Data context can be used as an output for the workflow but not as an input. |
Placement | Select if the button will be displayed in the Toolbar for the whole page or in the PanelHeader of the screen section. |
ConfirmationMessage | Select a string that will be displayed before executing the action. |
ConfirmationRule | Select a rule that will be checked before executing the action. |