Decision-Making Flow, Majority Approval 20220819
Three approvers are requested to authorise the draft in parallel. When two or more approvals are received, the draft is considered approved. The applicant is notified of the result by email.
Worker (#of Swimlane: 4)
  • Planner
    • Person in charge of drafting the decision.
  • Approver 1
    • The approver of the relevant project, who authorizes the request for approval 1.
  • Approver 2
    • The approver of the relevant project, who authorizes the request for approval 2.
  • Approver 3
    • The approver of the relevant project, who authorizes the request for approval 3.
Business Flow (Complexity of Workflow: 22)
  • 11. Submit a request for approval
    • The planner drafts the request to be approved.
  • 41x. Respond to returns
    • The drafter can either revise the draft and resubmit it or withdraw it.
  • 292-1. Approval 1
    • Approver 1 approves the draft.
  • 32-2. Approval 2
    • Approver 2 approves the draft.
  • 142-3. Approval 3
    • Approver 3 approves the draft.
  • 8x1. Record of approval
    • The workflow platform overwrites the “Status” (select type) data item to show “Approved”.
  • 5x2. Record of withdrawal
    • The workflow platform overwrites the “Status” (select type) data item to show “Withdrawn”.
  • 33x3-1. Number of approvers +1
    • The workflow platform has +1 approver.
  • 42x3-2. Number of approvers +1
    • The workflow platform has +1 approver.
  • 41x3-3. Number of approvers +1
    • The workflow platform has +1 approver.
  • 35x4. Clear the number of approvers
    • The workflow platform sets the number of approvers back to zero.
Business Process Variables (#of Data Item: 26)
  • ▼ Application ▼ 0
  • Affiliation of Planner q_Affiliation 1*
    • The department to which the planner belongs is stored. (“Organisation” in the workflow platform).
    • processInstanceInitQgroupId
  • Planner q_Drafter 2*
    • The planner is stored. (“user” in the workflow platform).
    • ${processInstance.initQuserId}
  • Time of Submission q_Submission 3
    • The date and time of the submission is stored.
  • Select Relevant Project q_Project 29*
    • It contains information on which project the draft relates to.
  • Description of and reasons for drafting q_Contents 4*
    • The contents of the draft and the reasons for it are stored.
    • (Example.) <Purpose/Reason>. Additional licences are required due to an increase in the number of members. <Order placed to> Questetra Corporation <What to purchase and services to be used> Questetra BPM Suite Professional edition $XXX / user / month (excluding tax, annual payment) <Quantity and contract period> 10 licences From 2022-01-01 to 2022-12-31 (12 months)
  • Attachment q_Attachment 5
    • It contains attachments relating to the content of the draft.
  • Payment q_Payment 6*
    • The amount of the external payment is stored.
  • Man Hours q_Hours 7
    • The amount of internal man-hours is stored.
  • Budgetary Classification q_Budget 8
    • The budget category of the draft is stored.
  • Budget Category Remarks q_Remarks 9
    • The remarks of the budget category of the draft content are stored.
  • ▼ Approval ▼ 10
  • Approver 1 q_Approver1 11*
    • Approver 1, who approves the draft, is stored.
  • Approval Result 1 q_Judge1 13*
    • The authorisation results of approver 1 are stored.
  • Approval date and time 1 q_DateTime1 12
    • The approval date and time of approver 1 is stored. (Automatically set in “2-1. Approval 1”)
  • Approver 2 q_Approver2 19*
    • Approver 2, who approves the draft, is stored.
  • Approval Result 2 q_Judge2 22*
    • The authorisation results of approver 2 are stored.
  • Approval date and time 2 q_DateTime2 23
    • The approval date and time of approver 2 is stored. (Automatically set in “2-2. Approval 2”)
  • Approver 3 q_Approver3 14*
    • Approver 3, who approves the draft, is stored.
  • Approval Result 3 q_Judge3 18*
    • The authorisation results of approver 3 are stored.
  • Approval date and time 3 q_DateTime3 15
    • The approval date and time of approver 3 is stored. (Automatically set in “2-3. Approval 3”)
  • Number of Approvers q_ApproverCount 24
    • The total number of approvers is stored.
    • 0
  • ▼ Results of the Approval Process ▼ 16
  • Status q_Status 17
    • The status of the request for approval is stored. x1, automatically overwritten at x2.
    • 1
  • ▼ Internal Communication ▼ 20
  • Comments q_Message 21
    • Internal comments and messages are stored.

Field Name, num, Initial Value

Download

This archive contains the BPMN icons that are not available in the Basic edition.

Capture

See also

%d