Wiki source code of 4.8.3 Approval Escalation
Last modified by Admin User on 2023/06/30 10:26
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Escalation steps can be included in your approval plans to automatically forward requisitions/orders to another approver if the first has not dealt with them within a certain definable timeframe. | ||
| 2 | [[image:PECOS Admin.WebHome@Fig 4.22 - Notification messages approval escalation.png]] | ||
| 3 | If escalation steps are used in your approval plans and any step is invoked, this eMail is **sent to the original approver** (the escalated task’s owner) to notify them that their approval has been escalated. An entry will also be made in the audit trail and is configurable here. | ||
| 4 | |||
| 5 | Note that the eMail and audit trail for the //**new**// approver (the owner of the escalation task itself) is part of the standard configuration of the approval plan. | ||
| 6 | |||
| 7 | To configure this message: | ||
| 8 | |||
| 9 | 1. In the Organisation Maintenance page click the **Notification **button. | ||
| 10 | 1. Select the **Approval escalation **tab. | ||
| 11 | 1. Enter the subject text and message text that you would like to appear in eMails sent to the owner of the original approval task. | ||
| 12 | 1. In the **Audit trail Message** box, enter the message that you would like to appear in the requisition or purchase order audit trail when the escalation task is invoked. | ||
| 13 | 1. Click **Save**. | ||
| 14 | |||
| 15 | **Suggested Approval Escalation Text** | ||
| 16 | |||
| 17 | //Subject Text~:// Approval Escalation | ||
| 18 | |||
| 19 | //Body Text~:// Document reference <%DOCID%> has not been approved within the required timeframe and has been escalated. It has therefore been removed from your PECOS inbox because your approval is no longer required. | ||
| 20 | |||
| 21 | //Audit Trail~:// Escalation timeframe expired and approval escalated from <%USRID%> |