Skip to main content

Mobile

pasted-image-20260517183810-cab287be

Buttons

pasted-image-20260517183831-def8a609

pasted-image-20260517183852-e97062da

There are three states shown above. Clicking the subscript opens the corresponding workflow diagram.

After a workflow is enabled, the related button is automatically bound with the corresponding subscript without needing a refresh. When the workflow is running, clicking the button shows the corresponding prompt.

After rejection, the same workflow can still be initiated again. In history, this is shown as returned.

Status UI Display

No approval history.

No approval in progress.

pasted-image-20260517183921-387538d2

pasted-image-20260517183932-1d5b7de7

Has approval history.

Has approval in progress.

Has approval history.

No approval in progress.

Capsule Action Bar

pasted-image-20260517184003-7f019acb

pasted-image-20260517184010-4442030c

Transfer

pasted-image-20260517184024-e890fe76

If "Also transfer subsequent tasks in the current workflow instance" is selected, subsequent tasks in the current workflow are also automatically transferred to the selected person.

Add Approver

Add someone to approve together.

When a countersignature node already has "Minimum Approvals" configured, adding an approver only adds the new approver to the current node's approver scope. It does not automatically increase the original passing threshold. In other cases, all approvers must approve before the approval is completed.

For example, if a countersignature node originally has three approvers and the minimum approvals value is 2, then even if another approver is added later, the system still determines node completion according to the rule "the node passes once 2 people approve." Here, adding an approver is closer to "expanding the people who can participate in approval at the current node" rather than forcing the newly added approver to approve. Therefore, if the business requires the added approver to participate in the decision, avoid setting the minimum approvals too low during workflow design, or clearly define in actual usage that adding approvers is used to supplement approval opinions, not to change the passing threshold of the current node.

Reject

pasted-image-20260517184103-2be25087

Approve

pasted-image-20260517184119-163496bb

History

pasted-image-20260517184146-d9a633a6

Fuzzy search: historical approver and workflow name.

Workflow Diagram

pasted-image-20260517184226-8690391d

pasted-image-20260517184234-af4d7b55

Supports one-finger drag and two-finger zoom.

Web

pasted-image-20260517184326-0099a4b6

Buttons

pasted-image-20260517183831-def8a609-1

pasted-image-20260517183852-e97062da-1

There are three states shown above. Clicking the subscript opens the corresponding workflow diagram.

After a workflow is enabled, the related button is automatically bound with the corresponding subscript without needing a refresh. When the workflow is running, clicking the button shows the corresponding prompt.

After rejection, the same workflow can still be initiated again. In history, this is shown as returned.

Capsule Action Bar

pasted-image-20260517183545-19fb128d

Transfer

pasted-image-20260517184341-ec2e7f29

If "Also transfer subsequent tasks in the current workflow instance" is selected, subsequent tasks in the current workflow are also automatically transferred to the selected person.

Add Approver

Add someone to approve together.

When a countersignature node already has "Minimum Approvals" configured, adding an approver only adds the new approver to the current node's approver scope. It does not automatically increase the original passing threshold. In other cases, all approvers must approve before the approval is completed.

For example, if a countersignature node originally has three approvers and the minimum approvals value is 2, then even if another approver is added later, the system still determines node completion according to the rule "the node passes once 2 people approve." Here, adding an approver is closer to "expanding the people who can participate in approval at the current node" rather than forcing the newly added approver to approve. Therefore, if the business requires the added approver to participate in the decision, avoid setting the minimum approvals too low during workflow design, or clearly define in actual usage that adding approvers is used to supplement approval opinions, not to change the passing threshold of the current node.

Reject

No special notes.

Approve

No special notes.

History

pasted-image-20260517184401-b7a2ff16

Search Box

Fuzzy search: historical approver and workflow name.

Workflow Diagram

pasted-image-20260517184417-9df594e4