UTM PV6.6.0 SV102 Release Notes - Notification Routing Rules

Sep 3, 2026

Upload by Patrick

Release notes describing notification behavior for task workflow actions and timing within UTM PV6.6.0 SV102. The rules specify who receives notifications when roles such as Preparer and Approver are assigned or left unassigned, including fallback delivery to the corresponding Preparer or Approver group. It also details approval routing across multiple approver levels, how unapproval returns to the previous approver, and how upcoming versus past-due timings change recipient scope.

LanguageEnglish

CategoryGeneral

FormatPDF

Pages13

Reading Time5 min

AccessFree to download

Notification routing rules

Action-based recipients

Timing-based recipients

| Action | Recipient | Additional Comments | | --- | --- | --- | | Recalled | Preparer | If Preparer is Unassigned, the notification is sent to all users in the Preparer Group. If there is no Preparer Group assigned, no one receives a
notification. | | Rejected | Preparer | If Preparer is Unassigned, the notification is sent to all users in the Preparer Group. If there is no Preparer Group assigned, no one receives a
notification. | | Prepared | Approver 1 | If Approver 1 is Unassigned, the notification is sent to all users in the Approver Group. If there is no Approver Group assigned, no one receives a
notification. | | Approved | Send to the next Approver | For example, if Approver 1 approves the task, then Approver 2 receives a notification. If any Approver role is Unassigned, the notification is sent to all | | Action | Recipient | Additional Comments | | --- | --- | --- | | | | users in the Approver Group. If there is no Approver Group assigned, no one receives a
notification. | | Unapproved | Send to the previous Approver | For example, if Approver 2 unapproved the task, then Approver 1 receives a notification. If any Approver role is Unassigned, the notification is sent to all users in the Approver Group. If there is no Approver Group assigned, no one receives a
notification. | | Timing | Recipient | Additional Comments | | --- | --- | --- | | Upcoming Due | Preparer | If Preparer is Unassigned, the notification is sent to all users in the Preparer Group. If there is no Preparer Group assigned, no one receives a
notification. | | Timing | Recipient | Additional Comments | | --- | --- | --- | | Past Due | Preparer and Approvers 1–4 | If Preparer is Unassigned, the notification is sent to all users in the Preparer Group. If there is no Preparer Group assigned, no one receives a
notification.
If any of the Approver 1–4 roles is Unassigned, the Approver Group is notified in addition to any other primary approvers assigned to the task. For example, if a task has three approval levels and Approver 1 and Approver 2 are Unassigned, but Approver 3 has an assigned user, the Approver Group and Approver 3 receive a notification. If there is no Approver Group assigned, no one receives a
notification. |

FAQs

What happens when the Preparer role is unassigned for a recalled or rejected action?

The notification is sent to all users in the Preparer Group. If no Preparer Group is assigned, no one receives the notification.

How are notifications routed when Approver 1 approves a task?

If Approver 1 approves, the next approver receives a notification (e.g., Approver 2). If any approver role is unassigned, notifications are sent to all users in the Approver Group.

Who receives notifications when a task becomes past due?

Notifications go to the Preparer and Approvers 1–4. If the Preparer is unassigned, the Preparer Group is notified; if no Preparer Group exists, no one receives the notification, and approver-group notifications may also be sent when approver roles are unassigned.

Sep 3, 2026

Upload by Patrick