Process Settings

To access the process settings page, follow these steps: Select a process, right-click to choose 【Settings】, then enter the process settings page as shown in the figure below:

Layout: Reorganize the workflow layout
Steps: Click 【Layout】to open a dialog box, click 【YES】, and the workflow will be reorganized, as shown in the figure below:
The layout result is shown in the figure below:

Properties: After selecting a process control, click 【Properties】 to view the detailed control configuration page, as shown in the figure below：
Clear: Cleared all nodes and process controls from the page
Delete: Select a process control then click 【Delete】 to delete this control
Process Validation ：Validate whether the current set process can be executed, as shown in the figure below：

Flow Control Terminology Explanation

Terminology Explanation：

Icon	Name	Explanation
	Start Element	The first activity of the approval process, representing the start of the process. A process can only have one start activity. It can set the name, parameter indicator, and other information
	End Element	The final activity of the process, indicating the end of the process. A process can have n end activities. End activities can set document approval or document cancellation
	Manual Element	An approval node in the process. You can set the approver for this node or set the logic to enter or leave this node in process function
	Connection Line Element	The element that connects various approval nodes, with the direction of the arrow on the line representing the direction of the workflow. Logic judgments can be set in connection lines for data flow
	Automatic Element	An element that invokes other functionality, enabling features like CC/XOR, reassignment, logical delete, physical delete, returning to the previous step, or returning to a previous level. It can also have custom events executed during system invocation for logical processing
	Route Element	A route without business rules. It is used to indicate that the workflow engine needs specific processing or logical judgment when business reaches here, then proceed to the subsequent node based on the judgment or processing outcome

Start Control

Represents the beginning of a process, and there can only be one start activity per process. Clicking the control →【Properties】or right-clicking the control →【Detailed Configuration】allows you to set its functionality, as shown in the image below:

Numbering: Automatically generated by the system based on the order of component appearance
Ordering: Controls the sequence of generated functional buttons

Use Case: Controlling the arrangement order of the "Return" and "End" function buttons at the leader's approval node, and the flow is illustrated in the figure below:

Steps are as follows：

Set the sort order of the "Return" line to 0, as shown in the figure below：
Set the "End" connection line's sorting order to 1.
The result appears as shown below （The “Return” option is positioned before the “End” button）：
Name： Describes the name of the current approval node
Parameter Identifier ：Assign a special identifier to the current node, which helps in querying this specific node via the parameter identifier within the database

Line Control

Connect the various approval nodes together, with the direction of the arrow on the line indicating the direction of workflow flow.

Operation as follows: Click the line control →【Properties】or right-click the control to click 【Detailed Configuration】, which will pop up the detailed configuration interface to set its function, as shown in the figure below：

Filter by Department

Application Example : At the "Initial Review" node, specify that the review should be conducted by either the Finance Department or the IT Information Department, and designate the department's review personnel. The system needs to list the approvers for the "Initial Review" node in the order of Department → Personnel as optional choices when submitting for initial review. The system workflow is as shown in the figure below：

The procedure is as follows:

Click 【Workflow Designer】→【Basic Setup】→【Dialog Box】→【New】; the dialog box type is “process personnel filter” as shown in the figure below：
On the connection line control “Send to Initial Review,” set up department-based filtering and decide on execution personnel by choosing the dialog box, as demonstrated in the figure below：
The Initial Review node's “Assign Department” should be set to Finance or IT Information Department, with option for department filtering selected as “Optional”, shown in the figure below：
For choosing approvers, click the [Add] button and select approvers in the pop-up window, as seen below：

The result looks like this: once logged into the application platform, creating a draft document, and clicking [Send], the following dialog box appears on the screen:

Action Properties

The capabilities included in Action Properties as shown in the figure below:

Operation Type

Forward Approval: The arrow direction on the line control points forward, indicating approval is passed from the current node to the next node in the workflow sequence
Application Case: A document created by the author goes through department head approval and then general manager approval, like shown in the diagram below：
Backward Approval: This refers to current node approval that detects issues or for other reasons deems the document ineligible to pass through to the next node, thus returning the document to a prior node or different node for further handling
Case Example 1 (Return to the Previous Node): When the document reaches “Department Head Approval,” if issues are found or if the input information is incorrect, document can be returned to prior node to be re-edited, as shown in the diagram below ：
Operations as follows:
1. Set a link between “Department Head Approval” and “Submit” nodes, directing arrows from “Department Head Approval” to “Submit”()
2. Set this link's operation type to backward approval, generating a “Return” option on the “Department Head Approval” node shown below：
Case Example 2 (Return to Different Node)： Suppose when the document reaches General Manager Approval, the document is questioned for serious flaws that necessitate the creator to remake it. In such a situation, the document can be sent back through multiple stages to the creator as shown in the figure below：
On the “General Management Approval” node, generate a “Return to Creator” option as follows：
Normal Action: This action does not affect or control the direction of data flow in the approval process like forward or backward actions. Instead, it works in conjunction with external action functions to generate new buttons, such as function buttons designed for functions like reassignment, inclusion, physical deletion, logical deletion, return to a previous step, or to go back several steps up the hierarchy. Following are examples of additional functionalities enabled by these action types: Reassign, CC, Physical Delete, Logical Delete, Return to Last Step, Return to Previous Level, etc.
Application Example : Execute a dedicated function on the "Department Management Head Approval" node to generate its own button which can reassign the task directly to someone else for processing as shown below：
Operation Steps ：
1. Add a functional control, and then a link control with name “Reassign”, set the operation type between the link and the automatic control as “normal action,” and specifically assign executors to this reassign node. Additionally, set the executives to be selected as "Required to be specified" or "Must be specified", exactly as shown below：
2. Configure the functional control under the common actions label to reassign it, allowing the type to shift by accepting the processor set by the link control, exactly as shown below：
Effect as seen ： When the [Submit] button is pressed from the "Dept Head Approval" node, the [Reassign] button becomes activated, enabling the configurable selection of a new person to handle the matter as seen in the figure below：
Concurrent Sign Aggregation: When coupled with the concurrent splitting function, the data that has been split is collected to ensure the condition of all these concurrent paths is satisfied for the process to advance to the next stage
Application Example ：After being reviewed by Department Head, File must be submitted to though two concurrent signers from Finance management and IT Information department and then allowed to proceed to General Management Approval stage. As shown in the diagram below：
Operation as follows ：
1. Add a "Send to Sign" line and specify here the personnel who need to participate in the concurrent signature as shown in the image below：
2. Add the route control (router 1), which tells the workflow engine that the process has reached here and takes down the data via "Personnel Split" lines to the next node of approval.
3. Add "Personnel Split" lines. At this point, the logic for handling the data that came through in router 1 must to be set. It is also necessary to set the data to split according to persons as seen in the figure below.
1. Add a "Concurrent Sign" control, where here the concurrent signers' approval actions are processed, and set that this node accepts personnel designated by the previous node, as seen in the figure below：
1. Add “Concurrent Sign End” line, to feed the data after concurrent signing back to the “Department Head Approval” node, and select "End Personnel Split" at this point, as seen in the figure below：
1. Add a routing control (router 2) and implement logic to evaluate the data being passed to the next node. The process should only proceed to the next node after all designated approvers have completed their approval tasks. Set the approval arrival condition as follows, as shown in the figure below：
1. Add a "Concurrent Sign Aggregate" line, set the operation type to concurrent sign aggregation, as shown in the figure below：
Effect as follows ：At the “Department Manager Approval” node, after clicking 【Submit】, selecting 【Send to Concurrent Sign】, choose the concurrent signers as shown in the figure below：
Upon completion of the concurrent signing process, the department manager logs into the application platform, clicks the corresponding form to carry out the review. At the point of clicking 【Flow Record】 on the “General Manager Approval” node’s form, the result displayed shall be as follows：

Action Type

Unconditional Execution ： No special judgment condition. Upon entering this node, it is executed directly
Need to Judge Conditions Before Execution ： This action requires calling an event handler and judging if the current condition matches the processing condition before proceeding

Use Case ： The document has a value field in its form. During the approval process, need to make a judgment on the amount. If the amount exceeds 100,000, the CEO shall be assigned to approve； otherwise, management should be assigned. Refer to the following flow diagram：

Procedure as follows ：

Create an event to determine the amount. Click 【Basic Settings】→【Event Management】→【New】, the dialog box type is “process personnel filter” as shown in the figure below：

After completing the creation of the amount event, click to save. Complete the saving of the event.

Set General Manager Approval Conditions (amount > 10000), as shown in the figure below：

Set Vice General Manager Approval Conditions (amount <10000 )，as shown in the figure below：

Effect as follows ： Login to the application platform, click on the form to begin process review, when the form contains the value entered into the "amount" field > 10000, according to the conditional assessment, the system will only generate the option to send to general manager approval button, with the effect shown in the figure below：

When the value entered into the “amount” field on the form is <10000, according to the conditional evaluation, the system will only generate a choice button to send to vice-president approval, and the effect is shown as in the picture below：

Executable Personnel

No need to specify

No need to specify: Do not specify the executor of the next node at this approval node, but set approvers for the next approval node. The effect shown is as follows:

Need to specify

Need to specify : The approver at the current node can specify the person who will process the next approval node. If not specified, the next node will proceed with the original approvers you set for review

Application Example: In production material procurement applications, the personnel in the procurement department separately handle different types of materials. Therefore, applicants must designate which person within the procurement department will perform the review when submitting the application. The system's workflow is shown in the figure below：

Steps as follows ：

Set up the selected executor scheme：Create a new personnel selection scheme under "Dialog Box Management," as shown in the image below：
After creating the new scheme, click Save to complete saving the new dialog box.
On the "Submit to Procurement Department for Review" line, set that the execution personnel of this line must be specified, and specify the above personnel choice scheme, as illustrated in the figure below：
Set up the procuration department's review node to accept the processor designated by the previous node, as shown in the figure below：

Effect as follows ：Login to the application platform, open the form, and submit the procurement department for review, select the approver, as shown in the image below：

Must specify

Must specify : The approver at the current node must specify who will process the next approval node. If not specified, the system will prompt to select the executor. Then, the next approval node can allow the receiver to receive the executor designated by the previous node without setting the approver, as shown below：

Split, Split End

Used generally to complete sign-off approval, when sign-off involves many approvers or many departments, task to be assigned to each approver in the sign-off process. The split end node can be set on the connection control or manual control based on demand.

No Split： By default, no split occurs
Split by Approver： Subsequently, membership of the sign-off operation will be split by each of its approvers, which must all complete their operations before there's movement forward to the starting node of sign-off again

Use Case： Following the example of splitting by approver to complete sign-off type tasks. System's workflow schema as as follows：

Procedure as follows ：

Add a "Send to Sign" line, and at this point specify which personnel need to participate in the concurrent signature, set the sign-off personnel as follows：

Add the routing control (router 1), which tells the workflow engine that the process has reached this point and then claw back data via “personnel diversion” lines to the next node of approval
Add "Personnel Split" lines. At this point, the logic for handling the data flowing to router 1 needs to be assigned, and data is split according to individuals, as seen below：

Add the "Signoff" control to process the approval actions of the sign-off personnel, and configure it to accept personnel designated by the previous node, as follows：

Add a "Concurrent Sign End" line, to carry data after Signing back to the "First Review" node, and at this point select the end of "Personnel Split", as follows：

Add a route control (router 2) and implement judgment logic on data proceeding to the next node point. Only after all approvers' approval tasks are completed will the process proceed to the next node. Set the approval arrival condition as follows, shown in the figure below ：

Add a “Concurrent Sign Aggregate” line, set the operation type as Concurrent Sign Aggregation, shown in the figure below,

The effect is shown in the figure below: At the "Department Supervisor Review" node, click the 【Submit】 button, as illustrated in the figure below：

Departmental Split

Departmental Split： During the sign-off process, there are multiple approval departments involved. The split function divides the sign-off tasks to all persons within the sign-off departments. After an approval action by one department within a signature approval, the flow will proceed to the node that initiated the sign-off.

Application Example： The application involves splitting by department for sign-off tasks in order to complete the sign-off process. The system workflow is illustrated as follows：

Operation as follows ：

Add a "Send to Convene for Signature" line, and specify the personnel who must participate in the concurrent signature；

Add the routing control (Router 1) to notify the workflow engine that it reaches here and then collects the data via "Departmental Split" lines to the subsequent node of approval；
Add "Departmental Split" lines, and set the logic for processing the data arriving at the routing control, that is to split the data by department as follows：

Add a "Concurrent Signature Aggregation " control； set the operation type to Concurrent Aggregation； adding to accept the person specified by the previous node, and the task can be considered completed for any single approver to pass or refuse. As shown in the figure below：

Add the "Concurrent Signature Completion " line to return the data processed to the first initial review, and at this point select the "End Departmental Split"；
Add a Router control(Router 2)； implement judgment logic on data proceeding to the next node. The process should only proceed to the next node after all designated approvers have completed their approval tasks.。ervation arrival setting as； look as follows， shown in the figure below ：

Add "Concurrent Sign Aggregate " line, set the operation type to Concurrent Sign Aggregate,

The effect is as follows： When clicking on the "General Manager Approval" node [Flow Record], you will find that only one task has been executed along with the two sub-tasks assigned to the Finance Department and IT Information Department, as follows：

Approval Opinion

During workflow approval submission in the application platform form, whether to display or not display the approval opinion display or not.

Do not display ：Approval Opinion column not displayed. Set as shown in the figure below：

The result is as follows ：Once logged into the application platform to draft a form and submit for initial review, the “Submit” button appears as follows：

Display but do not require to fill in ：Approval Opinion column appears, yet may be bypassed. Result is as follows：

Display and require：Approval Opinion column is mandatory. Appears as：

Entry Node Event

The functions included in the entry node event are as follows：

Execute Event

Upon reaching this node, call the SQL statement or stored procedure that has been set in "Event Management" to execute a piece of code to process the form

Application Example： The "Payment Application Sheet" in the Financial Department, after being approved, will automatically update the financial department’s approval opinion to the "Approval Opinion" field. The flow is as follows：

Procedure as follows ：

Create an execute event, set its type as “Execute code,” and write appropriate code based upon business logic to update the financial department’s decision upon approval. Set it as shown in the image below：

After creating the event, click【Save】to save the event successfully.

Set the “Entry Action” when reaching the "Special Approval by General Manager" node to execute the "Update Opinion" action defined above. The settings can be seen as follows：

The effect is as follows ： Once logged into the application platform to draft a form and submit for financial review, upon entering the approval opinion as "The finance department approved it！", the【Approve Opinion】 pop-up dialog will appear automatically once the General Manager's node is reached and the [Submit] button is clicked, as follows：

Notification Content

When executing the current node, the system issues a notification based on the established setting, as shown below：

Originator

When reaching the current node, select the person to draft the notification, as the originator will receive the message. If the option is not chosen, the originator will not be notified.

For example ：When the flow enters the "Department Head Review" node, it notifies the drafter "The document has been sent for approval!" The workflow is as shown in the following figure below：

The following steps are performed ： Right-click the "Send to Department Head for Review" connection line and click 【Detailed Configuration】, on the detailed configuration page, select 【Notify the drafter】, enter 【Notification content】, and then click 【Save】, like this：

Implementation effect ： After logging into the application platform, he/she submits a form to begin reviewing, the drafter receives a pending notice, see picture：

After completing the workflow, click 【Flow Record】 to view results like below：

Designated Person Notification

You can select one or more people to be notified. When the document is submitted for review, designated individuals will receive a notification about the review process.

For example: When sending a document to be reviewed by the department manager, notifying users Djx. The flow is as follows：

The steps are as follows ： Right-click【Submit to Department Manager for Review】line control, click 【Detailed Configuration】, on the detailed configuration page, click the add button after “Designated Person Notice”, pop up a page to input the condition, click 【Search】，then select djx, click 【OK】is as follows：

The results are as follows : The form creator (administrator) logs into the application platform and creates a new document under the draft mode，then click [Send] to send the document to the department manager, once done, dwj logs in to the application platform following by expecting to see a piece of to-dos, shown below：

Designated Condition Notification

Set personnel filter conditions in advance, the system will send notification to all people who match the conditions

Operation as follows ：

Create an event in the Event Management，click【Basic Setup】→【Event Management】→【New】, pop up the【Create New Event】page and enter relevant information, as shown in the figure below：

After creating the new event, click 【Save】to save the event successfully.

Right-click the link control, choose 【Detailed Settings】, and then click on the designated condition notification button. In this part, pop up a dialog box to input condition number, press 【Search】to select condition, then press 【OK】, as shown below:

The effect is shown in the figure below ：The person who drafts sends the document to the department head for review. Once all department heads log into the application platform, they will see a single to-do. When the department head of ZH BO reviews, the system will directly send a task, as shown in the image below。

After completing the workflow, click 【Flow Record】 to view results like this as follows：

Manual Data Entry Elements

Click the control →【Properties】or right-click the control →【Detailed Configuration】, set its function, the approval node within the workflow can be set with the approver of this node or set the logic of entering/leaving this node, etc., for processing function。

URL Address

When binding a form to a workflow node, the first node binds to the initialization form (the form configures initialization event and startup workflow event), the second node binds to the review form (the form configures workflow open event and workflow running event) and the other nodes can bind a form based on the demand. The URL address{Domain representing}： facilitates quick binding of form to the current node。

Operation as follows ：Click on the URL address{Domain representing} behind, pop-up page, select the form, as shown in the image below：

Approval Settings

The Approval Settings include the following functions as shown below：

Note ：For ordinary process handling time, fast processing time, ultra fast handling timeout reminders, timeout rollback, timeout rollback Number locked by document by current system version, when there is a need, special customization can be done.

Signature Method

There are two ways to set signature process when form reaches approval node, auto signature, manual signature. The difference between manual and automatic signatureis that in manual signature only after the approver of the current node clicks "Sign" manually, can he/she modify or approve the current form. With auto signature, no signature button needs to be clicked directly signed by the program.;

Example: To apply manual signature method when the form arrives at “Financial Review”，as shown in the following figure：

operation：Set the signature method of the current node as manual in the "Financial Review" node, as shown below：

Results as shown：

Recall Action

After the form has been issued and a problem arises, the form can be recalled and reprocessed if the approval by the next node has not been signed off yet

Example ：After the draft is submitted to the Financial Dept. for review, assuming that the application amount was wrong. It’s possible to recall and reprocess the drafting cycle. The system flow is as follows：

Operation as follows：Set the recall action to “Allow Recall” on the financial review node, as shown in the picture below：

Effect：In the application platform, after drafting the form and submitting it for financial review, the person validating will open the form, then click 【Recall】to recall the form as shown in the image below：

Approval Arrival Settings

Set Condition One

Set Condition One：When the previous step has multiple approval nodes, as long as one of them is completed, the flow can reach

Application Example ：To realize simple convergence mode of workflow, system flow is as shown in the following figure：

Procedure as follows ：

On the "Submit" node, set the approval dispatch action to, as shown in the image below：
Beneath the “General Manager Approval Stage”, configure the 'approval arrival conditions' to be, as depicted in the image below:

Effect ：Once procurement department or financial department-approved，the flow will proceed to General Manager Approval stage, flow effect shows as below figure：

Set Condition Two

Set Condition Two ：When previous step has multiple approval nodes, all nodes completed, the flow can reach

Application Example ：To implement synchronous workflow mode, System flow as shown in figure below。

Procedure as follows ：

On the "Submit" node, set the approval dispatch action to, as shown in the image below：
On the “General Manager Approval” stage, set the approval arrival action to as follows, as shown in the picture below：

Effect ：Only upon approval by both the procurement department and the financial department can the flow proceed to the General Manager examination stage, as in the picture below，Once you click【View Flow】to review the workflow management document, this is how the system works：

Set Condition Three

Set Condition Three ：When the previous step has multiple approval nodes, when all the activated nodes are completed, the process can proceed forward

Example for Application ：To implement a workflow choice mode, as shown in the diagram below：

Operate as follows：

Set the "Send Approval" action on the "Submit" node to this value, as seen below：
Set "Approval Arrival" to the following value on the “General Manager Approval” node, as seen in the figure below：

Effect ：When starting the approval stage, such as for Finance and Administration, as shown below：

Once the two nodes are completed, the General Manager Approval node will be initiated, and after completion, upon clicking to view the process, the result will look like this figure below：

Set the Condition Four

Set the Condition Four： When all the activated previous nodes are completed, the flow can reach the start node, though the drop-down menu will show all previous nodes ahead of this node

Application Example ：To implement a workflow multi-choice mode, the system workflow can be illustrated as the following figure：

Procedure as follows ：

On the "Submit" node, set the approval dispatch action to, as shown in the figure below：
On the "General Manager Approval" node, set the approval arrival action to, as shown in the figure below：

Effect ：All nodes that have started from the Submit node, as shown in the figure below：

Once all these nodes finish their approval, the General Manager Approval node can start its work, after doing so, upon clicking to view the workflow, the result is shown as the figure below：

Set Condition Five

Set Condition Five ：When the number of activated nodes assigned forward equals the number of established conditions for this current node, the process can proceed to the next node. This condition involves validating the data passed to the next node, and only when all assigned approvers complete their processes does the flow proceed forward to the next node

Application Example ：For example, a consultation process where multiple people could be assigned to review simultaneously, and once all those individuals finish reviewing, the process proceeds to the next node. System workflow as follows：

Operation ：Set the approval arrival settings for the router control (Router 2) to the mode described above, as seen below：

Effect ：In the application platform, click the form to begin workflow review. At the "General Manager Approval” node, click【Flow History】to view the workflow as in the figure below：