You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 48 Next »
UI actions are buttons, links, and context menu items on forms and lists. They allow customizing the UI to be more interactive, adjustable, and comfortable for working.
Role required: admin.
UI action inheritance and override
In SimpleOne, you can inherit the UI actions and then override their logic, scripts, order, name, or any other feature.
Inheritance rules
- The following UI actions are applied to forms and lists:
- UT actions inherited and not overridden by the Overrides by option on the current level of inheritance.
- The overridden on the current level functionality of the inherited UI actions.
- UI actions specified on the current level.
- A UI action inherited on the 1st level with the override functionality specified on the 2nd level cannot be applied on the 3rd level of inheritance. An inherited UI action specified on the 2nd level may be applied to the 3rd one.
- A UI action inherited on the 1st level with the override functionality specified on the 3rd level cannot be overrided on the 2nd level. In this case, the system warns of active override option and requires for its deactivation.
The system provides UI Actions inheritance with the Inherits option. When a UI action has a Table specified, and the Inherits option is defined with TRUE, the system applies this UI action to all children tables of the one specified before.
To child UI actions, the reference Parent option defines an ancestor UI action with functionality options may be overridden if you need it.
To inherit a UI action, complete the steps below:
- Make a UI action parent by setting the Inherits checkbox active and clicking Save.
- Make a UI action child by specifying the Parent field with the UI action you want, then customizing the record. Click Save to apply changes.
To override a UI action, complete the steps below:
- Open the child UI Action form.
- In the Overrides by field, specify a parent UI Action that should be overridden.
UI actions types
- Form button
- Form header button
- Form bottom button
- Form context menu
- Form link
- List banner button
- List bottom button
- List context menu
- List choice
- Dependency map context menu.
UI actions on form
UI actions on list
UI actions customizing
You can create new or customize existing UI actions.
To do this, please complete the following steps:
- Navigate to System Definitions → UI Actions.
- Click New or select existing UI-action.
- Customize UI-action using the form provided.
- Click Save or Save and Exit to apply changes.
You can edit some types of UI actions like buttons, links in a quick way. For this, please complete the steps below:
- Right-click on the UI action you need to edit to open a context menu.
- Click Edit UI action. The specified UI action form appears.
Global UI Actions
You can make a UI action display on all tables.
To do that, follow the steps below:
- Open the UI action record desired.
- On the form, specify Global table in the Table field.
- Click Save or Save and Exit to apply changes.
Most burger menu items and some buttons on forms (New, Save, Save and Exit) and on lists (New, Delete) are global.
Embed a UI Action
UI action functionality allows creating multi-level submenu options by embedding items for the burger menu within forms and lists.
This option is only available for UI actions of the Form context menu and List burger menu types.
To embed a UI action, follow the steps below:
- Create a parent UI action specifying its type with the Form context menu or List burger menu checkboxes on the Position and Style tab.
- Click Save and Exit to leave the form.
- Create a child UI action of the same type specifying its Parent option with Ui action created before.
- (Optional) Set the Inherits option active.
- Click Save to apply changes.
Display condition configuration
The condition option defines situations when UI actions displayed. The Condition field expects using server-side API, but in some cases, it is possible to apply client-side API. To enable client script use, on the UI action form, set the Client option checked. Within Condition, to access a UI action, use the current object. This object may be used only for UI actions displayed on forms.
It makes sense to invoke current within UI actions on updating since this object is defined in this situation. When creating a new UI action, the current value is NULL..
Use logical operators && (AND) and || (OR) for making up the complex conditional expressions.
Condition option allows invoking server-side Script Includes created. In the example below, the function wfContextExists() of Script Include with the same name gets current.sys_id and current.getTableName as recordID and tableName arguments.
The ss object allows invoking the SimpleSystem methods.
This UI action is a reference to the record with the sys_id of the getTableName table. If a record exists, the function returns TRUE, and, in the opposite, it returns FALSE when there is no record found. Depending on the value returned, the function displays the UI action or not.
function wfContextExists(recordID, tableName){ let table = new SimpleRecord('sys_db_table'); table.get('name', tableName); let wfContext = new SimpleRecord('wf_context'); wfContext.addQuery('related_record_id',ss.getDocIdByIds(table.sys_id, recordID)); wfContext.query(); return Boolean(wfContext.getRowCount()) }
Defining UI action behavior with a script
The Script field defines the UI action behavior in the form field. In there, you can determine UI action behavior logic using Server-Side API. For example, this UI action adds an informational message on every table field with the Description field content.
ss.addInfoMessage(current.description);
When the current object is invoked there, it is not necessary to use the initialize() method; the object context is already initiated.
UI Action form description
Field | Description | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | UI action name. It specifies a text displayed on the button, link, or as a context menu item. | ||||||||||||||||||||||||||
Table | A table to display UI action on. A form or a list or a context menu should be used. | ||||||||||||||||||||||||||
Comments | UI action brief description. | ||||||||||||||||||||||||||
Active | Mark this checkbox to display the UI-action is displayed on form (list, context menu). | ||||||||||||||||||||||||||
Inherits | When set to TRUE, this UI action is propagated to all the tables that are a child for the table specified in the table field. | ||||||||||||||||||||||||||
Overrides by | This field is specifying UI action, which will be overridden by current UI action. Learn more about UI action inheritance and override. | ||||||||||||||||||||||||||
Order | The displaying order. If there are over one UI-actions of the same type, then they will be arranged in ascending order. | ||||||||||||||||||||||||||
Parent | Specify the context menu item to be a parent for the current UI action (applicable for the Form context menu UI action type). | ||||||||||||||||||||||||||
Use in | Choose form where the UI-action is displayed. Available options are:
| ||||||||||||||||||||||||||
Conditions and Actions | |||||||||||||||||||||||||||
Show Insert | When set to TRUE, this UI action is displayed on a new record insert form. | ||||||||||||||||||||||||||
Show Update | When set to TRUE, this UI action is displayed on an existing record form. | ||||||||||||||||||||||||||
Wait Server Response | When set to TRUE, the system will wait for the server response after clicking the button. The button will be disabled until the server responds. | ||||||||||||||||||||||||||
Client | When set to TRUE, client-side API is available in the Script field; otherwise, server-side API is available. | ||||||||||||||||||||||||||
Condition | A condition written using server-side API; if this condition will be met, then the Script will be executed. | ||||||||||||||||||||||||||
Script | The script that will be executed by clicking the UI action. | ||||||||||||||||||||||||||
URL | This URL will be followed after clicking the UI action. You can use variables listed below there:
| ||||||||||||||||||||||||||
Position and Style | |||||||||||||||||||||||||||
Form Style | Button appearing style on the form view:
| ||||||||||||||||||||||||||
Form Bottom Button | Button at the bottom of the form. | ||||||||||||||||||||||||||
Form Button | Button in the form header on the right. | ||||||||||||||||||||||||||
Form Context Menu | Context menu item on the form. | ||||||||||||||||||||||||||
Form Header Button | Button in the form header on the left. | ||||||||||||||||||||||||||
Form Link | Link on the form. | ||||||||||||||||||||||||||
Form Field Label Context Menu | An item of the context menu for the fields on the form. | ||||||||||||||||||||||||||
List Style | Button appearing style on the list view:
| ||||||||||||||||||||||||||
List Banner Button | Button in the list header on the left. | ||||||||||||||||||||||||||
List Bottom Button | Button at the bottom of the list. | ||||||||||||||||||||||||||
List Burger Menu | A burger menu item on the list. | ||||||||||||||||||||||||||
List Choice | Menu item for actions applicable to list entries. | ||||||||||||||||||||||||||
List Header Right Button | Button in the list header on the right. | ||||||||||||||||||||||||||
List Link | Link on the bottom of the list. | ||||||||||||||||||||||||||
List Table Header Context Menu | A context menu item for the elements of the list. | ||||||||||||||||||||||||||
List Context Menu | Context menu item on the list. | ||||||||||||||||||||||||||
Button Context Menu | A context menu item for UI actions of the button type. | ||||||||||||||||||||||||||
Dependency Map Context Menu | Menu item on the service model form. |
- No labels