... | @@ -2,11 +2,9 @@ |
... | @@ -2,11 +2,9 @@ |
|
|
|
|
|
## Prerequisites
|
|
## Prerequisites
|
|
|
|
|
|
1. User has the role case worker (technical role name if you need to
|
|
1. User has the role case worker (technical role name if you need to contact support: x_steas_uh_core.case_worker)
|
|
contact support: x_steas_uh_core.case_worker)
|
|
|
|
|
|
|
|
2. The user wants to establish rules for automatically approving
|
|
2. The user wants to establish rules for automatically approving certain courses that students apply to be approved.
|
|
certain courses that students apply to be approved.
|
|
|
|
|
|
|
|
3. Logged in user has access to the process being worked on
|
|
3. Logged in user has access to the process being worked on
|
|
|
|
|
... | @@ -16,31 +14,18 @@ |
... | @@ -16,31 +14,18 @@ |
|
|
|
|
|
1. Log on to UH Sak as a case worker.
|
|
1. Log on to UH Sak as a case worker.
|
|
|
|
|
|
2. Navigate to an application for approving of education where there is
|
|
2. Navigate to an application for approving of education where there is at least one course with the status "Approved".
|
|
at least one course with the status \"Approved\".
|
|
|
|
|
|
|
|
3. Click \"Propose automation\". (If the button isn\'t there, it\'s
|
|
3. Click "Propose automation". (If the button isn't there, it's because automation has already been suggested based on the approval made.)
|
|
because automation has already been suggested based on the approval
|
|
|
|
made.)
|
|
|
|
|
|
|
|
4. You\'ll see the message \" Proposal for automation has been
|
|
4. You'll see the message " Proposal for automation has been submitted ".
|
|
submitted \".
|
|
|
|
|
|
|
|
5. The manager of the case worker who proposed the automation is now
|
|
5. The manager of the case worker who proposed the automation is now given the task of approving the automation proposal. The manager finds the task under "My cases \> UH Tasks" and on the case in question.
|
|
given the task of approving the automation proposal. The manager
|
|
|
|
finds the task under \"My cases \> UH Tasks\" and on the case in
|
|
|
|
question.
|
|
|
|
|
|
|
|
6. The manager opens the approval task.
|
|
6. The manager opens the approval task.
|
|
|
|
|
|
7. The manager now has the option to edit the conditions for the
|
|
7. The manager now has the option to edit the conditions for the automation by clicking "Edit conditions" or approving them as they are by clicking "Approve".
|
|
automation by clicking \"Edit conditions\" or approving them as they
|
|
|
|
are by clicking \"Approve\".
|
|
|
|
|
|
|
|
8. When the manager is ready to approve, an expiration date must be set
|
|
8. When the manager is ready to approve, an expiration date must be set for the automation under "Expiry date".
|
|
for the automation under \"Expiry date\".
|
|
|
|
|
|
|
|
9. In order to manage the automation rules, a role must be manually
|
|
9. In order to manage the automation rules, a role must be manually added for this. The technical name of the role is "x_steas_uhp_c_d_0.approver_education" (technical name of the Manage Automation Rules table is "x_steas_uhp_c_d_0_automation"). |
|
added for this. The technical name of the role is
|
|
|
|
\"x_steas_uhp_c_d_0.approver_education\" (technical name of the
|
|
|
|
Manage Automation Rules table is \"x_steas_uhp_c_d_0_automation\"). |
|
|