1. Basic Settings

1.1 Select Template

• First select a business flow template, you can create or use an existing template independently.

1.2 Configure Basic Information

• Business Flow Name: used for subsequent calls.
• Process Initiation Object: preset or custom objects such as customers, contacts, business opportunities, and work orders.
• Sponsor Range: Select a certain scope to initiate business flows through the [Colleague] [Department] [User Group] [Role] module.
• Enable Interconnection Process: When selecting an approver, you can choose external roles, including external managers and external leaders. The Internet application currently supports ordering, work order, agency, equipment assets, service - personal, ordering mall, equipment query, service, equipment query, and ordering mall.
• Process Description: Describe the purpose or meaning of the process and other information, with a maximum of 500 Chinese characters.

1.3 Trigger Condition Configuration

• Description: After the business flow initiation object is selected, it can be re-filtered according to the field. Only the data that meets the filtering conditions will execute the business process and post-action.
• Trigger configuration can be explained through custom prompts (limited within 100).
• Actions can be set after terminating the process, including field change, APL code execution, CRM reminder, data lock/unlock.

2. Condition Configuration

2.1 Business Flow Configuration

• Drag nodes and polylines to draw business flowcharts.
• Polyline: A line segment connecting nodes, configured according to node characteristics.
• Node: Different collaborations can be achieved by configuring different nodes.
• Stage: The business flow can be divided by configuring different stages, and different nodes are placed in each stage to realize more complex business processes.
• There can only be one start node, but there can be multiple end nodes.

Note: All business processes need to configure the start node and end node to take effect

2.2 Business Node Configuration

• Business Node: It is used when the process runs to a certain node and requires employees to perform specific operations.

  • What needs to be done: There are mainly editing objects, operating objects, operating objects (multiple selection), editing related objects, selecting or creating new related objects, creating new related objects in batches, creating new secondary objects, and editing secondary objects.
  • Configurable edit fields or process layout.

• Approval Node: Similar to the approval flow node, the next stage of the process needs to be approved by the processor. If it is rejected, it will return to the designated node.

• Signature Node: Similar to the countersignature of the approval flow, it needs to be approved by everyone before it can be transferred to the next node.

• Application Node: A node that can trigger work order assignment/service evaluation/field planning/external enterprise processing process, generally used for after-sales service.

• Auto Node: When running to this node, some actions are automatically performed, such as automatically changing the information of a certain field, or automatically locking the data.

• Waiting Node: This node can set the waiting time, and the task can be automatically passed after waiting. The waiting mode is divided into conditional waiting and delayed waiting.

  • Conditional Waiting: After waiting for n minutes, judge whether the waiting condition is met.
  • Delay Waiting: After waiting for n minutes, continue to flow down.

• Branch Node: It is necessary to judge a certain field in this link, and flow to different nodes according to the content.

• Parallel Task: In a business process, multiple tasks need to be executed at the same time, and the next node can only be entered after the tasks are executed.

2.3 Completion Condition Settings

• Edit Completion Conditions: It is divided into field-based and APL code-based. Only when the set conditions are completed can the process pass.

2.4 After-action Settings

• After-actions include field change, SMS notification, business process initiation, email sending, external notification, APL code execution, data lock/unlock, new task, new schedule, and new sales record.

3. Publish & Management of Business Process

3.1 Publish of Business Process

• After saving and submitting successfully, the process will take effect. If there is any improper configuration, the system will verify the process configuration when saving.
• Similar to approval process management, operations such as editing, deactivating, enabling, copying, creating, and deleting business processes can be performed.
• You can also view the number of business process usage on the page

3.2 Business Process Advanced Settings

• Business Flow Default Processing Page Settings: Click the business flow to-do by default to enter the task processing page, or choose to enter the data details page by default.

• Mobile To-do Default Return Page Settings: The default is to stay on the task landing page after a certain to-do is processed, and it can also be set to return to the previous page.

• Termination Reason Configuration: When the service flow is terminated, whether the termination reason is mandatory can be set here.