文档更改5 Sub-process node

摘要

• 页面属性 (1 修改， 0 新增， 0 删除)
• 附件 (0 修改， 3 新增， 0 删除)
  • 1753064871834-492.png
  • 1753064891433-308.png
  • 1753065148807-206.png

细节

页面属性

内容

...	...	@@ -1,166 +1,88 @@
1		-The approval node supports the configuration:Node name, approver, approval mode, no-approver rules, field permissions, buttons, validation, and notifications.
	1	+=== 1、Feature Overview ===
2	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"]]
	3	+Sub-process nodes that can call other processes to run under the current process.
4	4
5		-=== 1、**Approver Settings** ===
	5	+When the business process is more complex, the process can be split into a parent process and one or more sub-processes to execute. When the parent process to a part of the process will begin to enter the sub-process approval flow, sub-process flow is completed and back to the parent process to complete the acceptance of the entire business.
6	6
7		-Choose from address book or form controls; Multiple approvers can be selected.
	7	+ps: child process is also a complete self-executing process.
8	8
9		-Multiple Approvers: Select different approval modes for different outcomes.
	9	+=== 2、**Use Cases** ===
10	10
11		-[[image:1741686498801-276.png]]
	11	+Scenarios such as: employees need to return the relevant equipment when leaving, in the exit process can call the “return of equipment” process, will leave the employee's equipment for the return.
12	12
13		-=== 2、Approval Mode ===
	13	+=== 3、**Design Approach:** ===
14	14
15		-[[image:1751269691489-384.png]]
	15	+[[image:1753064871834-492.png]]
16	16
17		-Approval mode supports single-approval and multi-approval。Multi-approval modes support  Chain signing  and  Parallel signing。
	17	+==== 1 Select Process ====
18	18
19		-Chain signing：A → B → C (in order)；
	19	+Select the process within the authority, only one can be selected.
20	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.
	21	+[[image:1753064891433-308.png]]
22	22
23		-Parallel signing： A, B, C (simultaneously)；
	23	+==== 2 Participant ====
24	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.
	25	+Sub-processes are automatically initiated, you need to select the participant of the sub-process, and the participant  acts as the initiator of the process;
26	26
27		-**Sequential and Parallel Signing Modes**
	27	+The participant can select one or more, and if you select more than one, there will be more than one sub-process running.
28	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.
63	63
64		-=== ===
	30	+==== 3  Run Mode ====
65	65
66		-=== 3、Rules for When No Approver is Found ===
	32	+Set the running relationship between the parent process and the child process;
67	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:
	34	+* Synchronization: enter the next node after the end of the child process; the parent process will continue to flow down only after the end of the child process flow (the end of the child process flow contains the flow status of flow completion and manual end). If there are multiple sub-processes, all sub-processes will end before completion.
	35	+* Asynchronous: the child process is initiated to the next node; the flow state of the parent process is not affected by the child process, i.e., after the process flows to the child process, the parent process continues to flow down the line.
69	69
70		-[[image:1741684876645-964.png]]
	37	+The default is synchronous.
71	71
72		-1. (((
73		-**Designated by the Previous Approver**
74	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**
	40	+==== 4 Automatically submit after the sub-process is initiated ====
79	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.
81		-)))
82		-1. (((
83		-**Auto-Approval**
	42	+If it is turned on and the sub-process is automatically submitted after it is initiated, the sub-process is automatically created for the Participant, and it is submitted directly to the next node of the order making, and goes to the subsequent approval node.
84	84
85		-* 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.
	44	+If it is not enabled, only the sub-process form data is created, and a pending process is created for the Participant to stay in the order node, and the sub-process needs to be submitted manually by the Participant.
86	86
87		-
88		-)))
89	89
90		-=== 4、**Field Permissions** ===
	47	+==== 5 Data transfer ====
91	91
92		-(% class="wikigeneratedid" %)
93		-The default field permissions for approval nodes are set to **visible**. These can be modified to **editable** or **required**.
94		-**Note**:
	49	+Sets the data transfer rules between processes when the parent process and the child process are running.
95	95
	51	+* Parent process →Sub-process: When the parent process flows to the sub-process node, the following parent process field values will be assigned to the corresponding sub-process fields
96	96	* (((
97		-A field must first be set to **visible** before it can be marked as **editable**.
	53	+Sub-process→ parent process: When the sub-process flow is completed, the following sub-process field values will be assigned to the corresponding parent process fields
98	98	)))
99		-* A field must be marked as **editable** before it can be marked as **required**.
100	100
101		-[[image:1741686531103-177.png]]
	56	+[[image:1753065148807-206.png]]
102	102
	58	+Data transfer rules:
103	103
104		-=== 5、**Function Buttons** ===
	60	+* Support [master-master], [child-child] two kinds of assignment relationship;
	61	+* field type filtering the new data of the same data service;
	62	+* and can only be assigned by business fields, system fields to business fields;
	63	+* each field can only be selected once;
	64	+* when assigning values between sub-tables, a sub-table can only be assigned by the same sub-table; e.g., the parent process has sub-tables A and B, and the sub-processes have sub-tables C and D. Sub-tables A can be；
	65	+* assigned to the sub-processes' child table C, child table D, but can not assign both child table A, child table B to child table C;
105	105
106		-The approval node supports the following function buttons: Agree、Save、Reject、Transfer、Recall、Circulate、Terminate、Add Signatory。
107	107
108		-[[image:1741686549674-439.png]]
	68	+==== 6 Sub-process operation rules ====
109	109
110		-Button Functions and Effects：
111	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.
	71	+When a sub-process is executed asynchronously, if the last node of the parent process also passes, the status of the parent process becomes “completed” regardless of whether the status of the sub-process is completed or not.
122	122
123		-The "Recall" button is displayed and operated on the completed details page.
	73	+When there are multiple sub-processes, the values will be passed according to the completion time of the sub-processes, and the sub-processes completed first will pass the values first, and the sub-processes completed later will overwrite the previous data.
124	124
	75	+When the sub-process is executed asynchronously, when the sub-process is completed, if the parent process is completed, it still needs to pass the value, and the order of passing the value is the same as above.
125	125
126		-In the admin console, rejection rules can be configured to support the following options：
	77	+Dismissal rule of approval node in parent process: If “Dismiss to previous approval node” is set, if the previous approval node is on top of the child process node, it will be dismissed to the previous approval node normally and the child process node will be skipped.
127	127
128		-* Reject to Document Creation Node
129		-* Reject to Previous Node
130		-* Reject to Specified Node
131	131
132		-[[image:1741686596683-996.png]]
	80	+Parent process dismissal (child process subsequent nodes dismissed to the node in front of the child process), the impact on the operation of the child process
133	133
134		-=== 6、Assignment ===
	82	+* synchronized: does not affect the operation of the sub-process;
	83	+* asynchronous ：
	84	+** If the dismissal to the node in front of the sub-process, and the node is submitted and runs normally according to the process, the running sub-process is discarded, and when you go to the node of the sub-process again, the sub-process activates a new process;
	85	+** If the dismissal to the node in front of the sub-process and the node is submitted and goes directly to the node that is dismissed, the running sub-process is unaffected and runs normally.
135	135
136		-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	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]]
143		-
144		-=== ===
145		-
146		-=== 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]]
153		-
154		-
155		-=== 8、Event ===
156		-
157		-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.
	88	+When the parent process run is discarded, the child process data is also nullified. When the parent process run is terminated, the child process is discarded.

1753064871834-492.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.liuqing01

大小

...	...	@@ -1,0 +1,1 @@
	1	+146.7 KB

内容

1753064891433-308.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.liuqing01

大小

...	...	@@ -1,0 +1,1 @@
	1	+8.0 KB

内容

1753065148807-206.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.liuqing01

大小

...	...	@@ -1,0 +1,1 @@
	1	+31.3 KB

内容