Approval Process Management

1. List

• Edit: Modify the approval workflow configuration. Note that the API name and associated object cannot be changed during editing.
• Enable/Disable: Activate or deactivate the approval workflow. Only enabled workflows can initiate approval processes.
• Reuse and Create New: Duplicate all configurations of this workflow to create a new approval flow. The associated object can be modified after reuse.
• Delete: Delete deactivated approval workflows. Deleted workflows retain historical approval instances for querying and viewing details.

picture coming soon:

2. Advanced Settings

Configure global settings for approval workflows, including:
- Priority
- Default landing page for Terminal tasks
- Web task processing behavior
- Approval comment configurations
- Rejection handling
- Approval detail display settings
- Timeout reminders
- Approver reassignment
- Field-level permission controls for approval content
- Custom plugin configurations

picture coming soon:

2.1 Priority

2.1.1 Function
Prioritize multiple approval workflows under the same object. For example, in Supplier Management and procurement approvals involving multiple stages, setting higher priority ensures urgent processes are handled promptly.

2.1.2 Configuration
- Drag and drop workflows to reorder priorities. Saved arrangements determine display order.
- Object-triggered workflows will execute the top-priority flow first.

picture coming soon:

2.2 Default Landing Page for Terminal Tasks

2.2.1 Function
Set whether Terminal tasks default to the approval feed detail page (showing only approval content) or the data detail page (enabling direct approval actions).

2.2.2 Configuration
Enable [Default to Data Detail Page] if needed.

Note: Users must have data view permissions to access the data detail page.

picture coming soon:

2.3 Web Task Processing Behavior

2.3.1 Function
Configure whether the detail page closes or remains open after task completion. Keeping it open aids review; closing it improves efficiency.

2.3.2 Configuration
Default: [Close detail page after processing]. Enable [Stay on current page after processing] if needed.

picture coming soon:

2.4 Approval Comment Configuration

2.4.1 Function
Customize the layout and interaction of approval comment fields.

2.4.2 Configuration
- Require comments for Agree/Reject actions.
- Auto-fill default comments (e.g., “Agree”/”Disagree”) during manual processing.
- Expand all processed comments by default.

picture coming soon:

2.5 Rejection Handling

2.5.1 Function
Set rejection destinations: terminate workflow or return to a specified node.

2.5.2 Use Cases
- Terminate: Reject flawed Sales Orders to halt processing.
- Return to Node: Route customer complaints back to a dedicated team for further action.

picture coming soon:

2.6 Approval Detail Display

2.6.1 Function
Toggle whether the latest approval details display on data detail pages.

2.6.2 Configuration
Enable [Show latest approval details] as needed.

picture coming soon:

2.7 Timeout Reminders

2.7.1 Function
Set task duration thresholds and reminder triggers (e.g., Contract Management renewal alerts).

2.7.2 Configuration
- Configure rules by day/week/month.
- Select active objects.
- Set task duration (hours/days).
- Define triggers (object fields).
- Choose actions (CRM alerts/SMS/email).

picture coming soon:

2.8 Approver Reassignment

2.8.1 Function
Enforce [Business Permissions] > [Roles] > [Reassign Approvers] controls when reassigning approvers.

2.8.2 Use Case
Reassign tasks when original approvers leave or become unavailable.

picture coming soon:

2.9 Field-Level Permissions

2.9.1 Function
Apply [Field Permissions] to objects under [Edit-Triggered Approvals].

2.9.2 Use Case
Restrict sensitive data (e.g., IDs, contact info) to authorized personnel.

Note: Applies only to view/edit-type approval content.

picture coming soon:

2.10 Role Matching Rules

2.10.1 Match by Submitter’s Primary/Secondary Departments
When enabled, approvers are auto-matched based on the submitter’s department affiliations.

Example:
- Sales Manager Role:
- Zhang San (Dept. A)
- Li Si (Dept. B)
- Submitter Wang Wu (Primary: Dept. A; Secondary: Dept. B) triggers approvals for both Zhang and Li.

2.10.2 Match by Data Ownership Department
Approvers are matched only if the data’s owning department matches their primary department. Empty data departments return no approvers.

picture coming soon:

2.11 Custom Plugins

2.11.1 Function
Extend CRM functionality via custom plugins (e.g., optimize workflows or UI).

2.11.2 Configuration
Use PWC-JS plugins to:
- Toggle bulk action buttons in task lists.
- Force approval content pop-ups during processing.

picture coming soon: