Pushback functionality is available for the following transaction types:
Manage HR
Final Pay
Extended Absence (a second level UCPath approver can push back a transaction for edits)
For Smart HR Transactions, and a TAM Job Opening, while there is no pushback feature, there is a ‘Clone’ feature, copying a denied or cancelled transaction into a new transaction for editing and resubmission.
No. Once an initiator submits the request, it will be automatically routed to all transactors who:
have the approval role for the transaction type, andhave row-level access to the department associated with the employee/position.
Only one person in that approver group needs to approve for the workflow to move forward. However, an approver has the ability to add an ad-hoc approver prior to approving the transaction, if necessary. Please note, adding ad-hoc approvers...
Yes. Prior to approving a transaction, an approver can click the [+] button in the AWE panel and enter the employee ID of one or more valid approvers. Once the first approver approves the transaction, it is routed to the next additional ‘ad hoc’ approver.
Note: the selected approver must have the required approval role, and row level security for the transaction.
It is also possible to add an ad hoc reviewer to a transaction. This reviewer will receive an email giving them...
