Application Instance Management
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

Approval Process

2026-06-23 15:02:49
liujinyuan
320
Last edited by haoyonghong on 2026-07-30 15:53:19
Share links

1. Adding an Approval Workflow

After entering the approval page, designers can click the "Create Approval Workflow" button to add a new approval workflow, or edit an existing workflow using the operation buttons on the right side of the approval workflow list.

When creating an approval workflow, the following information is required:
  • Approval Workflow Name: Used to identify the current approval workflow; a clear business name is recommended.
  • Bound Module: Used to distinguish the scope of application of the approval workflow.
  • Description Information: Used to describe the purpose, applicable scenarios, or approval rules of this approval workflow.

2. Designing an Approval Workflow

Clicking the "Design Workflow" button on the right side of the approval workflow list will take you to the approval workflow design page.

Newly created approval workflows contain three nodes by default: Initiation, Approval, and End.

Designers can click on each approval node to configure node information, approvers, copy recipients, approval permissions, and workflow rules.


2.1 Copy Node Configuration

Copy nodes are used to synchronize approval information to relevant personnel. Copy recipients can be set as follows:


  • Initiator Selected: When initiating an approval, the initiator manually selects the copy recipients. 
  • Designated Personnel:Designate one or more users as recipients.
  • Role: Select the approval role maintained in the "Approval - Roles" list.
  • Immediate Supervisor: Select the initiator's immediate supervisor, typically from the system's organizational or departmental structure configuration.

2.2 Approval Node Configuration

Approval nodes are used to set who approves the current node, how it is approved, and the operational permissions during the approval process.

1. Setting Basic Information

In the basic information, you need to maintain the title and approval node type of the approval node.
  • Title:The name of the current approval node.
  • Approval Node Type:Used to control the approval method for this node.
Approval node types include:
  • Manual Approval:Requires the approver to manually click "Approve" or "Reject."
  • Automatic Approval:The system automatically approves; commonly used in multi-branch scenarios where no approver is set.
  • Automatic Rejection:The system automatically rejects; commonly used in multi-branch scenarios where no approver is set.

2. Setting Approver

The approver type determines which personnel will approve the current node. Supported approval types:

Initiator Selection:The initiator manually selects the approver when initiating an approval process. There can be no restriction on the scope, or restrictions can be set by role, department, or position.

Initiator (Self-Selected):The initiator approves the approval themselves.
Role:Approval is performed by users under that role. Roles can be configured in the backend.
Position:Approval is performed by users under that position. Positions can be configured in the backend.
Department Head:Approval is performed by the head of the initiator's department.
Immediate Supervisor:Approval is performed by the initiator's immediate supervisor. Immediate supervisors can be configured in the personnel information.
Multiple Levels of Supervisors:Approval is performed consecutively by multiple levels of supervisors. The approval endpoint can be the highest supervisor, the second-highest supervisor, the third-highest supervisor, the fourth-highest supervisor, or the fifth-highest supervisor.
Previous Node Approver Selection:The approver at the previous node selects the approver for the current node. This method is not supported for the first approval node.

3. Set Approval Operation Permissions

Approval operation permissions control the actions an approver can perform at the current node.
  • Transfer: The approver can transfer the current approval to someone else for processing.
  • Rollback: The approver can roll back the process to any node before the current node, or back to the initiator.
The workflow after a rollback includes:
  • Approval in the order of the approval process: After the rolledback node is approved, the process continues according to the original approval flow.
  • Start directly from the current review node: After the rolledback node is approved, the process returns directly to the current approval node to continue review.
If "Initiator withdraws during review" is checked, the initiator can withdraw the approval during the current node's approval process.

4. Set Copy Recipients

Copy recipients can also be set in the approval node. The selection range for copy recipients is similar to that of approvers, and can be configured by specifying personnel, roles, positions, department heads, direct supervisors, etc.

5. Set Approval Process

Approval process settings are used to configure rules such as multi-person approval methods and whether approval comments are mandatory.

Multi-person approval methods include:
  • Joint Sign-off: Approval passes only after all approvers approve.
  • Alternative Sign-off: Approval passes only after one approver approves.
  • Joint Sign-off: Approval passes only after a certain percentage of approvers approve.
  • Request for Opinions: Approval passes only after a set approval percentage is reached.
  • Seeking Opinions: Approval is granted.This method is primarily used to collect opinions; the approval result does not affect the flow of the process.
Note:When "Requires All Approvals to Complete Review" is not checked, the current node can end as long as the approval conditions are met. When checked, regardless of the approval result, the system will wait for all approvers to complete their reviews before moving to the next node.

2.3 Adding Nodes and Branches

On the approval process design page, you can click the plus icon between nodes to add approval nodes or branches.
Branch types include:
  • Conditional Branch:Select one branch to flow downwards based on conditions. Condition priority is judged from left to right. If none of the branches on the left are met, the rightmost default branch is entered.
  • Parallel Branch:Supports multiple branches flowing simultaneously. If the conditions are met, the system will proceed to the corresponding branch; the default branch will always be executed.

3. Using Approval Workflows in Modules

After selecting this approval workflow in the module's "More Settings," when a user submits data, the system will execute the approval process according to the configured approval nodes, approvers, and workflow rules.

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