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

More Settings

2026-06-24 08:43:09
liujinyuan
312
Last edited by haoyonghong on 2026-07-30 15:52:36
Share links

1. Cross-Process Settings

Cross-process settings are used to configure the relationships between two or more related processes. Common scenarios include:
  • Vehicle information as a preceding process, vehicle reservation as a following process;
  • Recruitment management as a preceding process, referral management as a following process;
  • Meeting room management as a preceding process, meeting room reservation as a following process.
Cross-process settings need to be configured in the preceding process. Foreign key field controls in the following process should typically be set as dropdown menus or radio buttons, with the preceding process selected as the data source.

Through the relevant configurations in the actions, the relationships between preceding and following processes can be set, and the related data can be displayed on the system page.

2. Report Settings

Report settings are used to statistically display process data. The system supports three display formats: pie charts, line charts, and bar charts.

The "dimension" in the report can be understood as which field is used for classification and statistics. Statistical types include:
  • Count: Counts the number of data entries under each category according to the selected dimension.
  • Sum: Summes the specified numerical field according to the selected dimension. Fields used for summation must be numeric, such as integers or decimal fields.

3. Display Value Settings

When a process is configured with cross-process relationships and has subsequent processes, display value settings need to be enabled. Once enabled, the selected preceding process field values can be displayed in the subsequent processes.

4. Export Settings

After enabling the export action in the action design, the export function also needs to be enabled in the export settings, and the fields allowed to be exported for the process need to be selected.

5. Search Settings

After enabling the search function, the process list page can use selected fields to search for data. Designers can set which fields are allowed to be searched according to actual business needs.

6. Full-Text Search

Full-text search is used to support retrieving data from custom processes in a global search.

Configuration method: Save the fields to be searched in "More Settings - Full-Text Search", then rebuild the index for the changes to take effect. When setting fields, the title field has a higher weight than the content field, and therefore will be displayed first in the search results.

Note: Rebuilding the index usually only needs to be performed once when configuring full-text search for the first time; subsequent modifications generally do not require repeating this operation.

7. CSS and JS

The CSS and JS settings in the "More Settings" section are global configurations for the workflow and will be loaded into all pages of that workflow. They can be used to customize the page styles and interaction logic of the entire workflow.

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