Circulation Management Process 20220819
The process records the results of a circular sent to dozens of target persons.
The number of persons to be circulated to can be varied.
The recipients can be specified in batches by a list of user email addresses or by targeting organisations.
Client
Person in charge of requesting circulation.
Verifier
Person in charge of checking circulars.
1 1-1. Input Content / Designate Circulation Destination
The requester specifies the content and destination of the communication.
19 1-2. Confirm Recipient List
The requester checks the list of recipients to be sent to.
23 2-1. Circular Confirmation
The confirming party reviews the circular and records comments as necessary.
7 x1-1. Set Subject 13 x1-2. Prepare to Acquire Organisation Members
The workflow platform performs the pre-processing to retrieve the users belonging to the specified organisation.
10 x1-3. Acquire Organization Members
The workflow platform retrieves the users belonging to the specified organisation.
9 x1-4. Merge Recipient List
The workflow platform merges the lists that have been previously retrieved with the lists that have now been retrieved.
17 x1-5. Copy Processing List
The workflow platform copies the list of recipients for the execution of the process.
3 x1-6. Recipient List Processing
The workflow platform takes one item from the circulated list. It also updates the list before and after processing.
22 x2-1. Set Subject
(Data Items in the Parent Process) 15 Circular Subject q_title 0*
Stores the subject of the circular.
Circular Explanation q_detail 1*
Stores the description of the circular.
Related Files q_file 2
Stores the relevant files of the circular.
Circulation Deadline q_limit 4
Stores the deadline for the circular.
User List q_userList 3
Stores a list of email addresses to be circulated to.
Organization 1 q_qgroup1 8
Stores the (first) organisation to be circulated to.
Organization 2 q_qgroup2 9
Stores the (second) organisation to be circulated to.
Organization 3 q_qgroup3 10
Stores the (third) organisation to be circulated to.
Organization 4 q_qgroup4 11
Stores the (fourth) organisation to be circulated to.
Organization Counter q_counter 14
To retrieve the list of circulated items, a counter is stored for how many organisational data items are targeted.
1
Target Organization q_targetQgroup 12
Temporarily stores the organisations to be processed in order to retrieve the list of circulated organisations.
Target Organization User List q_targetQgroupUserList 13
Temporarily stores the list of users belonging to the organisation to be processed.
Circulation List, Before Processing q_userListBefore 5
Stores the list of email addresses to be circulated (before the child process is started).
Circulation List, After Processing q_userListAfter 6
Stores the list of email addresses to be circulated to (after the child process has been started).
Target User q_targetUser 7
Temporarily stores the email address to be circulated to start the child process.
(Data Items in the Child Process) 16 Verifier q_sub_user 17*
Stores the person who confirms the circular (for the child process).
Verifier’s Organization q_sub_group 18
Stores the organisation of the person confirming the circular. Automatically set in ‘2-1. Circular Confirmation’ (for the child process).
Date and time of confirmation of circulation q_sub_datetime 19
Stores the date and time of the confirmation of the circular. Automatically set in ‘2-1. Circular Confirmation’ (for the child process).
Circular Subject q_sub_title 20
Stores the subject of the circular (for the child process).
Circular Description q_sub_detail 21
Stores the description of the circular (for the child process).
Related Files q_sub_file 22
Stores the relevant files of the circular (for the child process).
Circulation Deadline q_sub_limit 23
Stores the deadline for the circular (for the child process).
Comments q_sub_comment 24
Stores comments for the circular (for the child process).
Field Name , num, Initial Value
Please refer to manual page M411 for more information on how parent-child cooperation works in workflow applications.
If the number of destinations exceeds 100, it may be caught by the limit of 500 execution steps. Please refer to manual page M407 for information on the limit on the number of execution steps. To avoid the limit on the number of execution steps, the system needs to be modified to allow recursive calls.
Like this: Like Loading...
Related
