An approver can update an action themselves, or return an action for correction to any recipient on the approval chain. However, the ability to update depends on two configurations:
The system profile option HR: Allow Approver Updates to Self Service Actions must be set to Yes.
The recipient must have a workflow role that allows edits.
To update pending transactions, approvers must have a workflow role with the appropriate role type attached to allow them to edit actions. They can then update actions regardless of their position in the approval chain.
There are two supplied role types that control approvers' ability to update pending transactions: SSHR Update Allowed and SSHR Update Not Allowed. These role types should not be used in conjunction with each other; use whichever is simplest.
SSHR Update Allowed
If you associate a role with this role type, any approver with that role can update a pending transaction. No one else can perform updates on pending transactions.
SSHR Update Not Allowed
If you associate a role with this role type, all approvers with that role are prevented from updating pending transactions; all other approvers can update pending transactions.
Use the Maintain Roles window to associate a role with a role type.
You can route actions to an HR representative. The application sends the action to all persons having a role associated with the seeded HR Representative role type. Use the Maintain Roles window to associate a role with this role type.
The first HR representative to process the action does so on behalf of all HR. This is especially useful in situations where the application encounters a future-dated change to a person's record. See Future-Dated Actions in Managing Dates in SSHR.
By default, the save of the SSHR transaction to the database is deferred after the final approval. This is to prevent any delay between the final approver clicking the approve button and moving on to the next notification.
The transaction is saved automatically when the Workflow Background Process runs. The system administrator needs to schedule this process to run periodically as needed.
When you run the Workflow Background Process you need to set the following parameters:
Item Type = HR
Process Deferred = Yes
Process Timeout = No
Process Stuck = No
If you need to modify the default behavior so that transactions are saved immediately after final approval, set the system profile HR:Defer Update After Approval to No at User/Responsibility/Application/Site level.
See User Profiles