Module Design
1. KodeFlex Introduction
1.1 About KodeFlex
2. Installing KodeFlex
2.1 Windows One-Click Installer
2.2 Linux One-Click Installer
2.3 Installing ZAI Service
2.4 Installing from the Source Package (All Operating Systems)
3. Upgrading KodeFlex
4. Platform
4.1. Application Management
4.1.1 Create an Application
4.1.2 Maintenance Application
4.2. Module Design
4.2.1 About the Module
4.2.2 Main Table Design
4.2.3 Sub-table Design
4.2.4 Action Design
4.2.5 Label Design
4.2.6 More Settings
4.2.7 Release Deactivated Modules
4.3. AI Features
4.3.1 Intelligent Conversation
4.3.2 Agent
4.3.3 Skill
4.3.4 Model List
4.4. Application Instance Management
4.4.1 Maintenance Instance
4.4.2 Navigation Menu
4.4.3 Data Source
4.4.4 Validation Rules
4.4.5 Approval Process
4.5. User
4.5.1 Maintain Users
4.5.2 Maintenance Department
4.6. Permissions
4.6.1 Maintenance Permissions
4.7. System
4.7.1 Company
4.7.2 Backup
4.7.3 Authorization Information
4.7.4 Safety
4.7.5 Timing
4.7.6 Time zone
4.7.7 LDAP
5. Business Applications
5.1 Access Applications
5.2. Backend
5.2.1 Personnel Management
5.2.2 Access Management

Action Design

2026-06-23 15:02:18
liujinyuan
325
Last edited by haoyonghong on 2026-09-01 17:27:09
Share links

Actions define the operations users can perform within a workflow. The system includes common actions such as adding, editing, deleting, viewing, importing, exporting, generating reports, linking data, and removing data. Enabling a corresponding action will display the relevant functionality on the front-end page.


For example, enabling the "Link Data" action will display a "Link Data" button on the details page, allowing users to link the current data with data from other modules. After successful linking, a corresponding label will be generated on the details page. Enabling the "Remove Data" action allows users to remove linked data.

1. Adding and Editing Actions

After adding an action, the system automatically generates two fields in the main table: "Who Performed the Action" and "Action Time." Therefore, designers do not need to manually add these fields to the main table.

Common action configuration instructions are as follows:
1)Data Operation Method: Users can choose to operate on a single data item or perform batch operations.
2)Opening Method: No page, pop-up page, or normal page. No page is suitable for actions that do not require information input; pop-up pages and normal pages are suitable for actions that require form information input.
3)Display Location: You can choose to display it on the list page, details page, or both.
4)Display Method: You can choose to display it directly on the page or in a dropdown menu. When there are many actions, it is recommended to put less frequently used actions in the dropdown menu to avoid making the list operation columns too wide.
5)Action Icons: 

  • The system provides fixed icons for built-in actions. Neither built-in actions nor newly added batch operations support icon editing.
  • For newly added actions, you can set icons for each action on the list and detail pages of the business system based on the business context, making the action items more intuitive and easier to identify.

6)Configure the display of actions on list and detail pages:
Designers can configure how action items are displayed on list and detail pages based on the page layout and actual usage scenarios. This not only keeps the action area clean and organized, but also better aligns the application interface with specific business scenarios.

  • Edit the display mode of the "Browse" action to show each action entry as text, an icon, or both.
  • Edit the display mode of the "Details" action to show each action entry as text, an icon, or text with an icon.



2. Configure the Interface of an Action

The interface is used to configure the content displayed on each action page. Click the "Design" button to maintain the interface content.
The following operations can be performed in the interface design:
  • Click on a field or the show/hide button on the right to control whether the field is displayed in the action interface;
  • Drag fields to adjust their display order;
  • Set the field width. The default width is automatic, but you can also enter a number to customize the width;
  • Set validation rules to validate field content when the form is submitted;
  • Set default values to reduce repetitive user input;
  • Set to read-only, so that the field is only for display and cannot be modified by users.

If there are sub-tables in the process, when maintaining the action interface, a field with the same name as the sub-table will appear in the main table fields. If you need to display the sub-table field on the page, in addition to displaying the specific sub-table field, you also need to display this field with the same name as the sub-table. If a preceding process exists within the workflow, after the foreign key field is displayed, you can continue to select preceding process fields, and their values will be displayed in read-only mode on the current page.
The details interface is slightly different, requiring you to set the field display position. The system provides two default sections: "Basic Information" and "Detailed Information." You can also replace the default sections with custom section labels to achieve multi-section, multi-label display.

3. Configure Interface Linkage for Action Forms

Interface linkage is used to control the display or hiding of other fields based on the value of a specific field.
The operation method is: Enter the "Interface" design page of the action, click the "Interface Linkage" button at the bottom, and maintain the linkage rules.
For example, when "Usage Type" is "Stamp," the "Stamp Time" field is displayed and the "Borrowing Time" field is hidden; when "Usage Type" is "Borrowing," the "Stamp Time" is hidden and the "Borrowing Time" is displayed. Both the source and target fields come from the fields already displayed in the current action interface.

4. Configure Trigger Conditions for an Action

Trigger conditions are used to control whether an action is displayed or available.
For example, the "Review" action is only allowed to be displayed or used when the data status is "Pending Review" and the current user is the reviewer. Triggering conditions can also be determined by manually writing SQL queries.

5. Configure Extended Actions after Executing Actions

Extended actions refer to other operations automatically executed by the system after the current action is executed. Extended actions can also have triggering conditions set; if no triggering condition is set, they are executed unconditionally by default.
Note: The triggering condition in an extended action is determined before the main action is executed, not after the main action is completed.
Extended actions support adding, editing, and deleting data tables. When adding data, the target table's field restrictions must be met; for example, required fields must be inserted, and fields with restricted values must be inserted with values that meet the requirements. When editing and deleting data, conditions usually need to be set; otherwise, it may affect all data in the table.

6. Configure Data Validation for Action Forms

Data validation is used to check whether data conforms to business rules before form submission. For example, in a vehicle reservation scenario, it can verify whether the intended vehicle has already been rented.
Note: The form will not be submitted if the data meets the interception conditions set in the validation.

7. Configure Reminders After Action Executio

Setting reminders is used to send notifications to relevant personnel after the action is executed. Reminders can be sent via system pop-ups or emails. This function is similar to copying the action result to specified personnel or those listed in the field.

8. Customize Actions Using CSS and JS

CSS and JS in the action are used to customize the style and interaction logic of the current action page. This configuration is local and only applies to the current action page.


Write a Comment
Comment will be posted after it is reviewed.