AWE: Initiator & Approval Workflow
For employees transferring between departments, does the receiving department initiate the transfer?
Yes, the receiving department should initiate the transfer.
Can approvers be defined at the department level? When would you use an ad hoc approver?
Transactions are routed to all transactors who:
- have the approval role for the transaction type, and
- have row-level access to the department associated with the employee/position.
Most transactions, including Additional Pay, require one level of approval. That said, an approver has the ability to add an ad-hoc approver prior to approving the transaction, if necessary. Please note, adding ad-hoc approvers can slow down the completion of the transaction.
If UCPath denies the transaction, what is the process if that initiator is no longer an employee? Who is notified to problem solve the reason for denial?
The Approval Administrator will also be notified that a transaction was denied.
Can the initiator assign specific approvers?
No. Initiators cannot assign a specific approver. Once an initiator submits the request, it will be automatically routed to all transactors who:
- have the approval role for the transaction type, and
- have 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 can slow down the completion of the transaction.
If a transaction is denied, what is the retention time of transaction in UCPath?
All transactions are kept indefinitely in UCPath.
When would the approver deny the request instead of pushback?
If one approval level is defined, then approve or deny are the only two options. If more than one level of approvals is defined, then pushback is an additional option.