Wiki源代码4 Approval Node
显示最后作者
| author | version | line-number | content |
|---|---|---|---|
| 1 | The approval node supports the configuration:Node name, approver, approval mode, no-approver rules, field permissions, buttons, validation, and notifications. | ||
| 2 | |||
| 3 | [[image:1741680073490-233.png]](% contenteditable="false" style="background-image:url(http://192.168.102.35:8080/webjars/wiki%3Axwiki/xwiki-platform-ckeditor-webjar/16.8.0/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="拖曳以移動" width="15"]] | ||
| 4 | |||
| 5 | |||
| 6 | === 1、**Approver Settings** === | ||
| 7 | |||
| 8 | Choose from address book or form controls; Multiple approvers can be selected. | ||
| 9 | |||
| 10 | Multiple Approvers: Select different approval modes for different outcomes. | ||
| 11 | |||
| 12 | [[image:1741680091439-552.png]] | ||
| 13 | |||
| 14 | |||
| 15 | === 2、Approval Mode === | ||
| 16 | |||
| 17 | The approval modes support Chain signing and Parallel signing。 | ||
| 18 | |||
| 19 | Chain signing：A → B → C (in order)； | ||
| 20 | |||
| 21 | * Approvers (A, B, C) must approve in sequence. After A completes the approval, the task moves to B's pending list. After B completes the approval, the task moves to C's pending list. | ||
| 22 | |||
| 23 | Parallel signing： A, B, C (simultaneously)； | ||
| 24 | |||
| 25 | * Approvers (A, B, C) receive the task simultaneously in their pending lists.Once A, B, and C complete their approvals, the process continues according to the configured approval rules. | ||
| 26 | |||
| 27 | |||
| 28 | **Sequential and Parallel Signing Modes** | ||
| 29 | |||
| 30 | (% style="width:1480px" %) | ||
| 31 | |(% colspan="2" rowspan="1" style="width:492px" %)((( | ||
| 32 | Approval Mode | ||
| 33 | )))|(% colspan="1" rowspan="1" style="width:987px" %)((( | ||
| 34 | description | ||
| 35 | ))) | ||
| 36 | |(% colspan="1" rowspan="4" style="width:161px" %)Chain signing|(% colspan="1" rowspan="1" style="width:331px" %)((( | ||
| 37 | Default | ||
| 38 | )))|(% colspan="1" rowspan="1" style="width:987px" %)((( | ||
| 39 | A, B, and C must all sign. If any one person rejects, the approval fails. | ||
| 40 | ))) | ||
| 41 | |(% colspan="1" rowspan="1" style="width:331px" %)((( | ||
| 42 | One-Vote Veto | ||
| 43 | )))|(% colspan="1" rowspan="1" style="width:987px" %)((( | ||
| 44 | If any one person (A, B, or C) votes to reject, the process node is rejected, and the remaining approvers do not need to continue | ||
| 45 | ))) | ||
| 46 | |(% colspan="1" rowspan="1" style="width:331px" %)((( | ||
| 47 | One-Vote Pass | ||
| 48 | )))|(% colspan="1" rowspan="1" style="width:987px" %)((( | ||
| 49 | If any one person (A, B, or C) votes to approve, the process node is approved, and the remaining approvers do not need to continue. | ||
| 50 | ))) | ||
| 51 | |(% colspan="1" rowspan="1" style="width:331px" %)((( | ||
| 52 | All Sign, Pass by Ratio (Customizable Ratio) | ||
| 53 | )))|(% colspan="1" rowspan="1" style="width:987px" %)((( | ||
| 54 | A, B, and C must all sign. If the approval ratio reaches the set threshold, the process node is approved. | ||
| 55 | ))) | ||
| 56 | |(% colspan="1" rowspan="6" style="width:161px" %)((( | ||
| 57 | Parallel signing | ||
| 58 | )))|(% style="width:331px" %)Default|(% style="width:987px" %)A, B, and C must all sign. If any one person rejects, the approval fails. | ||
| 59 | |(% style="width:331px" %)One-Vote Veto|(% style="width:987px" %)If any one person (A, B, or C) votes to reject, the process node is rejected, and the remaining approvers do not need to continue. | ||
| 60 | |(% style="width:331px" %)One-Vote Pass|(% style="width:987px" %)If any one person (A, B, or C) votes to approve, the process node is approved, and the remaining approvers do not need to continue. | ||
| 61 | |(% style="width:331px" %)Any Approval|(% style="width:987px" %)If any one person (A, B, or C) votes to approve or reject, the process node is approved or rejected accordingly. | ||
| 62 | |(% style="width:331px" %)Pass by Ratio (Customizable Ratio)|(% style="width:987px" %)If the approval ratio reaches the set threshold, the process node is approved, and the remaining approvers do not need to continue. | ||
| 63 | |(% style="width:331px" %)All Sign, Pass by Ratio (Customizable Ratio)|(% style="width:987px" %)A, B, and C must all sign. If the approval ratio reaches the set threshold, the process node is approved. | ||
| 64 | |||
| 65 | === 3、Rules for When No Approver is Found === | ||
| 66 | |||
| 67 | This rule determines how to handle situations where no approver is found due to reasons such as the assigned approver leaving the company or incorrect settings. Three modes are supported: | ||
| 68 | |||
| 69 | [[image:1741684876645-964.png]] | ||
| 70 | |||
| 71 | 1. ((( | ||
| 72 | **Designated by the Previous Approver** | ||
| 73 | |||
| 74 | * During the approval process, after the current approver submits, a dialog box pops up for the approver to designate a handler for the node with no approver. | ||
| 75 | ))) | ||
| 76 | 1. ((( | ||
| 77 | **Handled by System Administrator** | ||
| 78 | |||
| 79 | * During the approval process, after the current approver submits, the process flows normally to the node with no approver. The system administrator then designates a handler for the node on the process monitoring page in the admin console. | ||
| 80 | ))) | ||
| 81 | 1. ((( | ||
| 82 | **Auto-Approval** | ||
| 83 | |||
| 84 | * During the approval process, after the current approver submits, the process skips the node with no approver and proceeds to the next node, where the next approver continues processing. | ||
| 85 | ))) | ||
| 86 | |||
| 87 | |||
| 88 | === 4、**Field Permissions** === | ||
| 89 | |||
| 90 | (% class="wikigeneratedid" %) | ||
| 91 | The default field permissions for approval nodes are set to **visible**. These can be modified to **editable** or **required**. | ||
| 92 | **Note**: | ||
| 93 | |||
| 94 | * ((( | ||
| 95 | A field must first be set to **visible** before it can be marked as **editable**. | ||
| 96 | ))) | ||
| 97 | * A field must be marked as **editable** before it can be marked as **required**. | ||
| 98 | |||
| 99 | [[image:1741680106933-786.png]] | ||
| 100 | |||
| 101 | |||
| 102 | === 5、**Function Buttons** === | ||
| 103 | |||
| 104 | |||
| 105 | The approval node supports the following function buttons: Agree、Save、Reject、Transfer、Recall、Circulate、Terminate、Add Signatory。 | ||
| 106 | |||
| 107 | [[image:1741680117231-445.png]] | ||
| 108 | |||
| 109 | |||
| 110 | Button Functions and Effects： | ||
| 111 | |||
| 112 | (% style="width:1439px" %) | ||
| 113 | |(% style="width:132px" %)**Button Name**|(% style="width:302px" %)**Button Meaning**|(% style="width:1002px" %)**Effect After Clicking** | ||
| 114 | |(% style="width:132px" %)Agree|(% style="width:302px" %)Submit to Next Node|(% style="width:1002px" %)The process is submitted to the next node. After clicking "Details," further approval is not allowed. | ||
| 115 | |(% style="width:132px" %)Save|(% style="width:302px" %)Save as Draft|(% style="width:1002px" %)Stays on the current page and can be viewed in the pending list. Clicking "Details" allows continued approval. | ||
| 116 | |(% style="width:132px" %)Reject|(% style="width:302px" %)Reject to Previous Node|(% style="width:1002px" %)The process is rejected to a previous node based on rejection rules. It can be viewed in the completed list, but further approval is not allowed after clicking "Details." | ||
| 117 | |(% style="width:132px" %)Transfer|(% style="width:302px" %)Transfer the Process to Another Approver|(% style="width:1002px" %)The process stays at the current node, and the approver is changed from the reassigner to the new assignee. The new assignee can approve the process, while the reassigner can view details in the completed list but cannot approve further. | ||
| 118 | |(% style="width:132px" %)Circulate|(% style="width:302px" %)Circulate the Process for Others to View|(% style="width:1002px" %)Stays on the current page, allowing other operations. Recipients can view the process in the "Circulated List" under the Process Center. | ||
| 119 | |(% style="width:132px" %)Terminate|(% style="width:302px" %)Terminate the Process|(% style="width:1002px" %)The process stops and does not proceed further. It can be viewed in the completed list, but no further actions are allowed. | ||
| 120 | |(% style="width:132px" %)Add Signatory|(% style="width:302px" %)Add an Approver to the Process|(% style="width:1002px" %)After adding a signatory, the process stays at the current node, and the new approver is added. Once the new approver completes their approval, the process returns to the original approver's pending list for continued approval. | ||
| 121 | |(% style="width:132px" %)Recall|(% style="width:302px" %)Recall the Approved Process|(% style="width:1002px" %)Requires operation in the completed details. The recalled process can be approved again. | ||
| 122 | |||
| 123 | The "Recall" button is displayed and operated on the completed details page. | ||
| 124 | |||
| 125 | |||
| 126 | In the admin console, rejection rules can be configured to support the following options： | ||
| 127 | |||
| 128 | * Reject to Document Creation Node | ||
| 129 | * Reject to Previous Node | ||
| 130 | * Reject to Specified Node | ||
| 131 | |||
| 132 | [[image:1741680137160-379.png]] | ||
| 133 | |||
| 134 | === === | ||
| 135 | |||
| 136 | === 6、**Circulation Notification** === | ||
| 137 | |||
| 138 | The circulation notification feature supports configuring recipients and circulation comments. When setting recipients, allowing multiple people to be selected. | ||
| 139 | |||
| 140 | Circulation comments are text-based, and once set, recipients can view these comments in the approval records | ||
| 141 | |||
| 142 | [[image:1741680162647-311.png]] | ||
| 143 | |||
| 144 |