Process Pattern Analysis
Sequential Pattern
In the sequential pattern, activities must follow a strict order — the next activity cannot begin until the previous one is completed. The flow is illustrated in the diagram below:
The steps are as follows:
After creating a new process, bind the form to the workflow as shown in the figure below:
Configure the workflow. On the workflow settings page, drag workflow components to form a sequential pattern workflow. Right-click the first manual node and select 【Detailed Configuration】to enter the detailed configuration page. Modify the name and input the URL address. Repeat this process for other manual and connection nodes, configuring their names, as shown in the figures below:
Assign approvers to the manual nodes (process steps). Right-click the "Department Leader Review" node, select 【Detailed Configuration】, and enter the detailed configuration page to choose the approvers. The "General Manager Review" node should also be configured in the same way, as shown in the figure below:
The effect is as follows: After logging into the application platform, click on the form to initiate the review process, then click [Submit] to send it for department head review, as shown in the figure below：
The department head reviewer logs into the system, clicks on the pending tasks, reviews the form, and upon approval, sends it for General Manager review, as shown in the figure below：
The General Manager review node personnel log into the system, click on the pending tasks, review the form, and upon approval, conclude the process, as shown in the figure below：
After the process ends, click [Completed Tasks], open the form, and then click [Process History] to view the entire workflow execution, as shown in the figure below：
Parallel Branching Pattern
In the parallel branching pattern, one approval node activates multiple subsequent nodes simultaneously, allowing these tasks to be executed in parallel. After drafting the form, both the “Procurement Department Review” and “Finance Department Review” nodes are simultaneously activated. The workflow operates as demonstrated in the figure below：
Steps involved：
Create a new workflow, then bind the form to the workflow
Configure the workflow. On the workflow settings page, drag workflow components into a sequential pattern layout. Right-click on the first manual node, select 【Detailed Configuration】, enter the detailed configuration page, modify the node name, and input the URL address (repeat this for other connectors and manual nodes, replacing grID values with appropriate node names). Also, set the start node’s reception process (Approval Action Setting) to correspond to all downstream steps if there are multiple approval nodes ahead, as shown in the image below：
The effect is as follows: Log into the application platform, click on the form to submit it for review, as shown in the figure below：
After clicking [OK], both the Procurement Department Reviewer and the Finance Department Reviewer will receive the task to review. Once the Procurement Department review team logs in to the system to review the form, the process is completed. Open the "Finished" task and click [Flowing Records] to view the results, as depicted in the figure below：
Single Selection Pattern
The single selection pattern means that, during the approval process, the control or manual choice allows you to select only one node out of several options, achieving the following effect within the system process as depicted in the figure below：
Steps:
After creating a new process, bind the form to the workflow. Enter the settings page of the workflow, drag workflow components onto the page to build a flow. Double-click the name of a component to change the name. Right-click a 【Draft】 type node and select 【Detailed Configuration】, then click 【Advanced Settings】 in the detailed configuration page. Set the URL address and select [Approve Action Setting], click [Save], as shown in the figure below：
Set the URL address and approvers for the approval processes of “Procurement Department Review” and “Finance Department Review.” Right-click to enter detailed configuration, and then go to "Approve Settings" to select the approver, as depicted in the below image：
The effect is as follows: Upon logging into the application platform, formDA (form review) begins. When the drafter submits the form to be reviewed, they can only choose one node out of the two—either the Procurement Department Review or the Finance Department Review, as shown below。
Synchronized Mode
In synchronized mode, multiple parallel approval nodes must all be completed for the workflow to proceed to the next node. That next node will be triggered only once approval is achieved in all parallel paths. For example, when both the "Procurement Department Approval" and the "Finance Department Approval" have completed, the flow moves to "Approval by General Manager" as follows:
Operation steps are as follow:
After creating a new workflow, bind the form to the workflow. Enter the workflow settings page and drag workflow components onto the page to build a flow. Double-click the component name to change the name. Right-click a [Draft] type manual node, select [Detailed Configuration], then click [Advanced Settings] in the detailed setting screen. Set the URL address and approve action setting, and click [Save], as shown in the picture:
Set the URL address and approvers for the approval processes of “Procurement Department Approval”, “Finance Department Approval”, and “General Manager Approval.” Right-click to enter detailed configuration, and then go to "Approve Settings" to select the approver, as depicted in the image below:
For the General Manager Approval node, set the [Acceptance Action Settings], where, in case of multiple approval nodes before this step, the overall workflow can proceed after completion of all nodes, as shown in the figure:
Resulting effect is as follows:
Log into the application platform, click to initiate the approval process on the form, and upon submission by the drafter, it appears such as in the figure:
When the Procurement and Finance Department reviewers submit their approvals through the system, the General Manager’s approval node is activated and receives the approval form. When the General Manager finishes the approval through the system, the task is completed. After clicking on "Flowing History" within the form, the result appears as follows:
Single Convergence Mode
In a simple convergence mode, when there are two or more approval nodes in the approval process, they converge into one approval node. This convergence does not require synchronicity; once one approval node is completed, the process can proceed to the next node. Once either the "Procurement Department Approval" or "Finance Department Approval" has ended, the flow may move onto the "General Manager Approval," as shown in the figure below:
The operation is as follows:
After creating a new workflow, bind the form to the workflow. Enter the workflow setting interface, and drag workflow components to the page to build a flow. Double-click the control name to rename it. Right-click a【Trail】type manual control and select 【Detailed Configuration】. Then, in the detailed configuration option, set the URL address and “Approve & Submit Settings,” which allows only one node to be selected when there are multiple approval nodes proceeding, as shown in the figure below:
Set the URL address and approvers for the【Procurement Department Approval】【Finance Department Approval】【General Manager Approval】nodes. Right-click to open detailed configuration; then, click the plus button next to "Appoint Approver" to select the approver, as shown in the figure:
On the【General Manager Approval】node, set “Approval Arrival Settings.” When multiple approval nodes exist in the previous stage, this enables the flow to proceed as long as one node is completed, as depicted in the image:
The resulting effect is as follows:
Upon logging into the application platform, click on the form to start the approval process. When the drafter submits the approval form, it looks like this as seen in the figure below:
When the Procurement Department reviewer logs onto the system and submits their decision, it is sent to the General Manager for approval, shown here below:
Upon logging onto the system, the General Manager will be able to see the approval form, sent by the Procurement Department. Upon opening and submitting, the process is completed, as shown in the figure to the right:
Once the process finishes, click【Process History】on the form to view its operation path, just as in this image:
Multiple Selection Mode
The multi-choice mode refers to the process in which, during the approval process, approval logic or human intervention allows nodes to be selected from several available path options, either one or more. For example, when drafting a document, one can choose the next review steps from【Procurement Department Review】and【General Manager Review】—as seen in the image below—
Actions performed as follows：
After creating a new workflow, set the form to be bound to the workflow. Proceed to the workflow setting page, drag workflow components onto the page to create a flow. Double-click the name of a component to rename it. Right-click a【Draft】type manual control and select 【Detailed Configuration】. On the detailed configuration page, enter the URL address and select [Approval Action Setting] to allow sending to multiple downstream nodes when multiple approval nodes follow, as depicted in the figure below：
Set the URL address and approvers for the【Procurement Department Approval】【Finance Department Approval】【General Manager Approval】nodes. Right-click to enter detailed configuration; then, click the plus button next to "Appoint Approver" to select the approver, as shown in the image below：
Resulting effect is as follows： Upon logging into the application platform, click on the form to start the review process. When the drafter submits the review form, the options of【General Manager Approval】and【Procurement Department Approval】can be selected, as seen in the image below：
Joint Approval Mode
In joint approval mode, multiple individuals participate in the review procedure, following which all or some of those selected staff must complete the task. Once one of those members finishes their respective review action, the task proceeds. Illustrated graphically：
Here are the steps：
Add the "Send to Joint Signature" connector and set the specified participants to join the signature here, as shown in the figure below：
Add the routing control (router 1). Here, router 1 notifies the workflow engine that the process has reached here, sending data through the "separate workers" connector to the next approval node.
Add the "Separate workers" connector, Setting the processing logic for data arriving at this point from router1， Select To split the data by people, as shown in the figure below：
Add the "Joint signature" control, which, here, handles the approval actions of joint signers, setting that this node can accept workers designated by the previous node, as follows：
Add the "Joint Signature End" connector, which passes the data obtained back to the "Department Head's Approval" node with staff dispatching finished， as shown in the figure below：
Add the routing control (router 2) and perform a judgment on the data to be passed to the next node. Only after all approval staff have finished their approvals can it reach the next, so that the operation proceeds to the next node when all approval actions have completed, as shown in the picture：
Add the "Joint Sign Closing" line, setting the operation type to "joint sign closing", as shown below：
The result is as follows：
Log into the application platform, click on the form to initiate the approval process。 Upon delegate submission to the system, the delegate proceeds to the head of the department for review. the Department Leader Reviewer logs into the system and submits the complete case to the General Manager for examination or joint signature, as follows：
The joint signature reviewer logs onto the system, completes his or her review, and concludes the joint signature, forwarding the case to the department head reviewer, as depicted in the picture：
The Department Head reviewer logs into the system, and upon receipt of the end-of-joint-signature case, opens it and sends it to the General Manager as an approver, as illustrated herein：
The General Manager’s reviewer logs onto the system，the case is reviewed and ends the workflow. Click【Flowing Records】to view the result as follows：
Backtracking Mode
In backtracking mode, when the current approval node identifies issues or other reasons prevent the application form from passing review, it can be returned for reprocessing to a prior approval node or another node.
Example 1: When “Department Head Verification” finds problems, it can return the application to the previous node “Submission”, as shown in the image below：
Operation steps：
After creating a new workflow, set the form to be bound to the workflow. Enter the workflow setting page, click process control by dragging to the page to form the flow. Right-clicking the manual control, click 【Detailed Configuration】in the detailed configuration page, set the URL address and name. Set the line between the "Department Head Review" and the "Submission" nodes, the direction of the arrow points from "Department Head Review" to "Submission", and connect it with "Approval Action", as shown in the picture below：
Set the approvers for the "Department Head Review" and "General Manager Review" nodes, as shown in the figure below：
The effect is as follows: Login to the application platform, click on the form to start the approval process. After the author submits the approval, the process runs to the “Department Head Review” node, where submitting the form generates a back-to-the-previous option as shown in picture：
Example 2: When “General Manager Approval” identifies problems, it directly returns the form to the issuer, and this return spans over several stages, as shown in the image below：
Operations are as follows：
After creating a new workflow, set the form to be bound to the workflow. Enter the workflow setting page, click process control by dragging to the page to form the flow. Right-clicking the manual control, click 【Detailed Configuration】in the detailed configuration page, set the URL address and name. Set the line between the "General Manager Review" and the "Submission" nodes, the direction of the arrow points from "General Manager Review" to "Submission", and connect it with "Approval Action", as shown in the picture below：
Set the approvers for the "Department Head Review" and "General Manager Review" nodes, as described in the figure below：
The effect is as follows: After logging into the application platform and clicking on the form to initiate the review process, the initiator submits the form for Department Supervisor review. Once approved by the Department Supervisor, it is forwarded to the General Manager review node. After reviewing, the General Manager can either return the form to the initiator for re-approval or complete the process, as shown in the figure below：
When the process is returned to the initiator, the initiator submits the form again for Department Supervisor review. When the Department Supervisor logs into the application platform, they can click 【Process History】 in the form to view the status and history of the workflow execution, as shown in the figure below：
Reassignment Mode
Reassignment mode refers to the act of real-time dispatching of current approval tasks to other designated staff members for approval.
For example: When the process reaches General Manager for approval and wishes to reassigned approval to other staff members, the system workflow flow is as follows:
Operation steps are as follows:
After creating a new workflow, bind the form to the workflow, then enter the workflow settings, drag and drop controls on to the page to form the process, modify the name of the connector and node, and set the URL address for each node. For nodes such as "Department Head Approval" and "General Manager Approval," assign approvers, as shown in the image below:
Add an automatic control and a dedicated connector, and set the name of the connector to “Reassign,” along with specifying personnel to receive the task, as shown in the image below:
Configure the automatic control to have a common action of “Reassignment,” allowing it to accept users selected by the prior step, as illustrated in the figure below:
The system functionality works like this: After a user logs into the application platform, they can initiate the approval process by clicking on the relevant form. Once the author submits the approval to the system, the system passes it to the department supervisor for review. Upon receiving the task, the department supervisor logs into the system and forwards the case to the General Manager for evaluation or proceeding to reassignment as shown in the figures below.
Copy Mode
The copy mode is to copy the current approval document to other designated individuals or for the author to read over.
Example of copying to specified individuals：
The drafter drafts the document and then sends it to the department supervisor for review. After the departmental leader has finished reviewing, he or she sends it to the General Manager for review. After the General Manager has reviewed, one can choose to complete the process, or, alternatively, choose to copy it onto another designated individual to read through. The system’s workflow chart is as follows:
Actions performed：
After creating a new process, bind the form to the workflow. Enter the workflow settings page. Click on control elements to drag them onto the page, forming a process. Modify the names of links and nodes accordingly. Set the URL address for each node and assign approvers to nodes like “Departmental Approval” and “General Manager Approval” as shown in the picture:
Add an automatic control and a dedicated connector, and set the connector's name to “Email,” specifying the person who will receive the copy, as shown in the picture:
Configure the automatic control's general operation mode as “Copy” with the option to accept the personnel selected by the previous step, as illustrated in the figure below:
Effects of use:
Upon logging into the application platform, the drafter creates the document, sends it to the department supervisor for review. Upon registering in the system, the departmental leader will send it to the General Manager. Upon login, the General Manager can choose to conclude the process or have it copied to another person to review, as shown in the picture below:
Example of copying the drafter：
The drafter initially prepares the document and sends it to a superior for review. Once the individual in authority reviews the document, they can either forward it to the General Manager for review or directly send it back to the drafter to read over. The system flowchart proceeds as follows:
Actions performed:
After creating a new process, bind the form to the workflow. Enter the workflow settings page. Click on control elements to drag them onto the page, forming a flow. Modify the names of links and nodes accordingly. Set the URL address for each node and assign approvers to the “departmental leader” and “General Manager” steps as illustrated:
Add a automatic control and a dedicated connector. Name the connector as “Email,” and then set the type as automatic control and specify the slice properties for this node to accommodate people chosen in the previous step, just as seen in the figure:
Resulting effect:
Upon launching into the application platform, the drafter creates the document and forwards it to be reviewed by a designated superior. Once the individual in authority finishes reviewing, he or she can complete the process or send it back to the drafter to approve and review themselves, just like shown in the picture below。
Logic Delete Mode
Logic Delete Mode is when the current form is canceled and deleted, terminating approval process
Use Case: The General Manager needs significant authority and can directly cancel and terminate the approval process by deleting the form. The system workflow chart is shown below：
How to operate：
After creating a new process, bind the form to the workflow. Enter the workflow settings page. Drag controls to form a workflow. Modify the names of links and nodes. Set URL address for each node and assign approvers to nodes like “Department Head Review” and “General Managers Review,” as shown in the picture：
At the “General Manager’s Review” node, an automatic control and a dedicated connector are added. Rename the connector and set the common action of the automatic control to "logical deletion", allowing it to accept users designated by the previous step, as shown in the figure：
After the process reaches the General Manager's review node, here's the result：
Physical Delete Mode
Physical deletion mode directly removes the current approval document from the database so that no trace of the data remains in the system. This action is irreversible and permanent for this single document.
Use Case: The General Manager has considerable authority and can perform system-level direct data deletion, rendering it impossible to retrieve that specific document from the system. The system workflow chart is as displayed below：
How to operate：
After creating a new process, bind the form to the workflow. Enter the workflow settings page. Drag controls to form a workflow. Modify the names of links and nodes. Set URL address for each node and assign approvers to nodes like “Department Head Review” and “General Managers Review,” as shown in the picture：
At the “General Manager’s Review” area, an auto-control is equipped alongside a specific connecting line. Customize the lines’ name and set the auto-handling method to "physical deletion", as evident in the illustration provided：
Upon the process proceeding to the General Manager’s Review stage, this will be the visual result：
Upon submission, this document will be permanently erased from the system database and lost forever.
Branch Auto-Decision Mode
The branch auto-decision mode is a pattern where the system automatically judges set conditions.
Use Case: The system automatically judges the amount entered in the form for approval. Based on the set conditions, the system automatically sends form with amounts over 10,000 to the General Manager for approval, and amounts less than 10,000 to Vice President for approval, as depicted in the chart below：
Operation Steps：
After creating a new workflow, bind the form to the workflow. Enter the workflow settings page, drag and drop control elements to form a process. Change the names of connections and nodes, and set URL addresses for each node. Assign approvers to nodes such as "Procurement Department Approval", “General Manager Review”, and “Vice President Review”, as shown in the figure below：
Add a routing control element to direct requests from Procurement Department to either General Manager or Vice President approval, based on the specified condition.
Create a new event in the “Event Management” section that handles the amount judgment condition for the form, as shown in the picture below：
Set up the conditional logic on the "Forward to General Manager for approval" link, indicating that it should proceed when the condition is fulfilled (e.g., value > 10000).
For the "Forward to Vice President for approval" link, set up the condition to apply when the first rule is not met (e.g., value < or = 10000), as illustrated in the figure：
Result of the identification function： When the approval amount on the current form is less than 10,000, following the routing, data is routed automatically via the condition, resulting in the selection of “Send to Vice President Review.” Upon clicking [Process View] in the form page, the result will appear as shown in the picture below：
When the current approval form amount is greater than 10,000, I hear that upon the route, controled by the logic defined in the link, the system automatically selects the option "Send to General Manager for Approval." When clicking 【Flow View】on the form, the result appears as shown in the figure.
Single Node Multi-Person Single Approval Mode
Single Node Multi-Person Single Approval is where a single approval node is set up to have multiple approvers, and once one person approves, the node passes.
Use Case: The approval node “Department of Procurement Approval” has approvers Wang Manager and Financial Manager, where approval by either one allows the process to head to the “General Manager Approval” node. Upon approval, the process ends. The flow is demonstrated in the diagram below:
Action completed as follows:
After creating a new workflow, bind the form to the workflow. Enter the workflow settings page and drag the control components onto the page to create the flow. Rename the link and node names accordingly, set the URL address for each node, and assign approvers to the “General Manager Approval” node, as shown in the image below：
Configure the approvers of the “Procurement Approval” node and specify "Any person among several" as the operation type, as shown in the image below:
The result is as follows: Upon logging into the application platform and clicking on the form to initiate the approval process, once one of the specified approvers approves, the process progresses to the “General Manager Approval” node. Upon clicking “Process History” to view the process, it will be similar to the diagram settings as depicted below：
Single Node Multi-Person Multi Approval Mode
Single Node Multi-Person Multi Approval is where a single approval node requires multiple approvers to approve for it to pass.
Use Case: The “Department of Procurement Approval” node is configured with two approvers. For the process to reach the “General Manager Approval” node, both must approve. After approval, the process ends, as shown in the diagram below：
Action completed as follows:
After creating a new workflow, bind the form to the workflow. Enter the workflow settings page and drag the control components onto the page to create the flow. Rename the link and node names accordingly, set the URL address for each node, and assign approvers to the “General Manager Approval” node, as shown in the image below：
Configure the approvers of the “Procurement Department’s Approval” node and set the operation type to “All persons must approve” as shown in the picture below：
Result: Once logged into the application platform and clicking on the form to begin approval, when all designated reviewers have approved, click "flow history" to view the result as shown in the picture below：