Actions for Manual Progression and Synchronization Processes

You've actions available only if the confirmation type for the progression grade ladder or rate synchronization is Manual.

You can accept the updates for people individually or as a group. Accepting a proposed progression and salary update immediately makes these changes for the selected people:

• Adds a new grade or step to the person's assignment
• Adds a new salary amount to the person's salary record

You can reject proposed progressions and salary updates for people individually or as a group. You can also reject proposed progressions and salary updates for selected people in a group, and then accept updates for the remaining people. If you reject a proposal and then change your mind, you can undo the rejection and set the proposal status back to Not Processed.

If some time passes before you review the proposed updates, the underlying data might have changed. To catch any new problems, some validations run again when you manually accept the progressions and salary updates. If you change the person's assignment or salary record after the process ran, you might see an error message in situations like these:

• You add a future-dated salary record, and your configuration setting doesn't allow updates when future-dated salary records exist.
• You add a salary record for the same date as the proposed salary. But your configuration doesn't allow updates when a salary record exists on the same date.
• You add a future-dated assignment.
• You add a grade step record for the same date as the proposed progression. But your configuration doesn't allow updates when a grade step record exists on the same date.
• You change the person's salary basis.

For example, you ran the process with Confirmation Type set to Manual and there were no errors for this person. A proposed progression and salary update exists for June 25. After the process completed, you added a salary record dated July 1. You come to the Review Proposed Progressions and Salary Updates task and use the Accept action to update the person's assignment and salary record. Now, because the underlying data changed, you see the error showing that the proposal can't happen because there's a future-dated salary record.