Approval Request Flow
Records the Process from the request to the final approval. A director with approval authority can make a record of the approval by simply processing the [2x. Request from the Director] Step without going through the Submit and Approve Steps. However, even a proposal from a director requires approval by the officer if it exceeds 1 million yen. All approval requests are recorded and an approved proposal PDF is automatically generated.
BPMN Nodes
- 1 1. Submit plan draft Applicant drafts a proposal.
- 4 1x. Rework The applicant corrects the draft and resubmits, or withdraws
- 3 2. Approve The applicant’s boss confirms the draft and returns any deficiencies.
- 25 2x. Request from the Director Who in a position of Leader submits drafts
- 14 3. Approve If the external payment is 100 thousand or more, the manager will approve
- 5 x1. Recording of Withdrawal The system overwrites the “Status (Select-type)” Data Item to display “Withdrawn”
- 8 x2. Recording of Approval The system overwrites the “Status (Select-type)” Data Item to display “Approved”
- 12 x3. Approval limit set The system sets the time that is 24 hours later when the token reaches the node into the specified Data Item.
- 21 x4. Recording of Disapproval by Officer The system overwrites the “Status (Select-type)” Data Item to display “Withdrawn”
- 24 x5. Recording of Automatic approval time The system sets the time when the token reaches the node into the specified Data Item.
- 17 x6. Recording of Approval The system overwrites the “Status (Select-type)” Data Item to display “Disapproved by Officer”
- 9 x7a. PDF generation The system inserts the values of the specified Data Items into the Base PDF and generates a PDF file.
- 18 x7b. PDF generation The system inserts the values of the specified Data Items into the Base PDF and generates a PDF file.
Workflow Diagram (click to open)
Variables (click to open)
- = Application = 0:
- Affiliation of Drafter q_Drafter_Org 1: processInstanceInitQgroupId
- Drafter q_Drafter 2: ${processInstance.initQuserId}
- Date and Time of Submission q_Submission_Time 3: Automatically input by Auto processing set in “1. Submit plan draft” or “1x. Rework”.
- Contents and Reason of the Plan q_Reason 4:
- Attachment q_Attachment 5:
- External Payment q_Payment 6:
- Internal Man-hours q_Man_Hours 7:
- Budget Classification q_Classification 8:
- Remarks for Budget Classification q_Classification_Remarks 9:
- = Approval = 10:
- Approved by:(Superior) q_Confirmer 11: Automatically input by Auto processing set in “2. Confirmation” or “2x. Request from Leader”.
- Date and Time of Approval (Superior) q_Confirmed_Time 12: Automatically input by Auto processing set in “2. Confirmation” or “2x. Request from Leader”.
- Approval limit q_Limit 13:
- Approved by:(Officer) q_Approver 14: Automatically input by Auto processing set in “3. Approval”.
- Date and Time of Decision (Officer) q_Approved_Time 15: Automatically input by Auto processing set in “3. Approval”.
- = Decision = 16:
- Status q_Status 17: 1
- Name of PDF q_PDF_Name 18: p#{processInstanceId}-r#{processInstanceSequenceNumber}.pdf
- PDF file q_File 19: Stores the file generated at x7.
- = Internal Communication = 20:
- Message / Comment q_Message 21:
Download
approval-request-flow-20160222-220-en.qar
Only available for Professional edition.
Notes
- You need to associate the Swimlane settings according to your organizational structure upon import
- In this App, Superior (Director of the Department) is defined using the Role settings
Arrangement Tips
- It can be used in all editions by removing [Generate PDF File].
See also
Like this:
Like Loading...
Related
Pingback: Understanding How to Use Split Conditions – Questetra Support