4 Approval Node - EgretSoft

1

The approval node supports the configuration:Node name, approver, approval mode, no-approver rules, field permissions, buttons, validation, and notifications.

2

3

[[image:1751269132744-902.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

=== 1、**Approver Settings** ===

6

7

Choose from address book or form controls; Multiple approvers can be selected.

8

9

Multiple Approvers: Select different approval modes for different outcomes.

10

11

[[image:1741686498801-276.png]]

12

13

=== 2、Approval Mode ===

14

15

[[image:1751269691489-384.png]]

16

17

Approval mode supports single-approval and multi-approval。Multi-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

**Sequential and Parallel Signing Modes**

28

29

(% style="width:1480px" %)

30

|(% colspan="2" rowspan="1" style="width:492px" %)(((

31

Approval Mode

32

)))|(% colspan="1" rowspan="1" style="width:987px" %)(((

33

description

34

)))

35

|(% colspan="1" rowspan="4" style="width:161px" %)Chain signing|(% colspan="1" rowspan="1" style="width:331px" %)(((

36

Default

37

)))|(% colspan="1" rowspan="1" style="width:987px" %)(((

38

A, B, and C must all sign. If any one person rejects, the approval fails.

39

)))

40

|(% colspan="1" rowspan="1" style="width:331px" %)(((

41

One-Vote Veto

42

)))|(% colspan="1" rowspan="1" style="width:987px" %)(((

43

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

44

)))

45

|(% colspan="1" rowspan="1" style="width:331px" %)(((

46

One-Vote Pass

47

)))|(% colspan="1" rowspan="1" style="width:987px" %)(((

48

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.

49

)))

50

|(% colspan="1" rowspan="1" style="width:331px" %)(((

51

All Sign, Pass by Ratio (Customizable Ratio)

52

)))|(% colspan="1" rowspan="1" style="width:987px" %)(((

53

A, B, and C must all sign. If the approval ratio reaches the set threshold, the process node is approved.

54

)))

55

|(% colspan="1" rowspan="6" style="width:161px" %)(((

56

Parallel signing

57

)))|(% style="width:331px" %)Default|(% style="width:987px" %)A, B, and C must all sign. If any one person rejects, the approval fails.

58

|(% 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.

59

|(% 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.

60

|(% 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.

61

|(% 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.

62

|(% 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.

=== ===

=== 3、Rules for When No Approver is Found ===

67

68

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:

69

70

[[image:1741684876645-964.png]]

71

72

1. (((

73

**Designated by the Previous Approver**

74

75

* 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.

76

)))

77

1. (((

78

**Handled by System Administrator**

79

80

* 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.

)))

1. (((

**Auto-Approval**

* 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.

)))

=== 4、**Field Permissions** ===

91

92

(% class="wikigeneratedid" %)

93

The default field permissions for approval nodes are set to **visible**. These can be modified to **editable** or **required**.

**Note**:

* (((

A field must first be set to **visible** before it can be marked as **editable**.

98

)))

99

* A field must be marked as **editable** before it can be marked as **required**.

100

101

[[image:1741686531103-177.png]]

102

103

104

=== 5、**Function Buttons** ===

105

106

The approval node supports the following function buttons: Agree、Save、Reject、Transfer、Recall、Circulate、Terminate、Add Signatory。

107

108

[[image:1741686549674-439.png]]

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:1741686596683-996.png]]

=== 6、Assignment ===

The process runs to the current node, you can assign values to the fields, and you need to set the fields and contents to be assigned in advance.

137

138

Assignment is performed only when the approval mode is “Single person approval”.

139

140

Enter or select the content of the assignment according to the field type. For personnel assignment, you can only select “current node approver”, and for department assignment, you can select “node approver's department” and “node approver's part-time department”. ".

141

142

[[image:1751269940050-146.png]]

=== ===

=== 7、Circulation Notification ===

147

148

The circulation notification feature supports configuring recipients and circulation comments. When setting recipients, allowing multiple people to be selected.

149

150

Circulation comments are text-based, and once set, recipients can view these comments in the approval records。

151

152

[[image:1741686607634-332.png]]

=== 8、Event ===

Process events include approval events and reject events, which are used to carry out some actions such as data service calls, intelligent assistant calls, message notifications, etc. after a process node passes or rejects.

158

159

[[image:1751270009451-352.png]]

160

161

162

Multiple actions can be added to an event, and the actions can be dragged to adjust the sorting;

163

164

At runtime, multiple actions are executed according to one transaction; if an action fails, all events will be rolled back.

165

166

If an action fails, all events will be rolled back. If the event fails, the process can continue to flow: If this item is not checked, the process will become “abnormal state” after the event fails; if it is checked, the event failure will not affect the process state, and the process can continue to flow.

Wiki源代码4 Approval Node