Multi-approval Workflow
The multiple approval workflow manager allows the definition of additional course enrolment workflows that require one or more approvals.
Functions of Approval Workflow Manager
New
Supervisors and members of groups can act as approvers.
Supervisors as approvers of enrolment request: Supervisors can be entered as approvers for the enrolment request, whereby we differentiate between direct supervisors and indirect supervisors. Direct superiors are defined as users who have been selected in a user's personal profile via the email address of the superior or the user selection field "Superior". The direct superior of an organisational unit is used as a further superior relationship. Indirect superiors are superiors who are defined in the organisational structure. The field "Include the superior in the approval process at the following levels" can be used to set which hierarchical level of the superior in the BU structure is to be taken into account for approval.
Groups as approvers of enrolment requests: If a group is set as an approver, all members of the group are authorised to process an approval request.
Reasons for Approval or Declination
Approval or declination reasons can be added for each approval step and are defined in the "Cancellation, exception, and approval reasons" manager. This allows the approver to justify their decision as to why a learner should or should not complete a course.
In addition to selecting a reason for confirmation or denial, the approver can also enter a reason in an input field. The selection of reasons for denial or confirmation is only available when using the "Booking request" panel.
Priorities
The priorities are also created there, but can only be added to one approval level per workflow. This priority allows the approver to add a weighting to their decision in addition to the approval reason.
Reasons for Cancellation, Exemption and Approval | Reason for approval
Reasons for Cancellation, Exemption and Approval | Reasons for Declination
The priorities are also created there, but can only be added to one approval level per workflow. This priority allows the approver to add a weighting to their decision in addition to the approval reason.
Reasons for Cancellation, Exemption and Approval | Priority for multi approval workflow
Filters
The filter function of an approval level can be used to further restrict the group of people for which this level applies, e.g. a customer-specific person attribute can be selected there. If a certain value is entered there, only then is this authorisation level applied.
Once all the necessary approval steps have been configured, they are displayed on the "Approval steps" tab. The last level is automatically the final approval, which can be recognised by the status "Confirmed" or "Rejected". For all previous levels, the participant remains in the "Requested" status. Using the checkbox in the "Final decision" column, the booking process can be canceled prematurely if, for example, a level is rejected.
The final enrolment must be carried out by the course administrator by transferring the confirmed users from the application list to the participant list.
Once the booking workflow has been set up, it can be assigned to a course. However, the meta tag "Multiple approval workflows" (ID=11842) must be assigned in the course template.