This page (revision-69) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JLawler

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
69 26-Nov-2021 10:22 9 KB kparrott to previous
68 26-Nov-2021 10:22 9 KB jmyers to previous | to last APPROVAL_WIP_REC ==> APPROVAL_WIP_REC(System_Preference)
67 26-Nov-2021 10:22 9 KB JEscott to previous | to last
66 26-Nov-2021 10:22 9 KB JEscott to previous | to last
65 26-Nov-2021 10:22 9 KB JEscott to previous | to last
64 26-Nov-2021 10:22 9 KB JEscott to previous | to last
63 26-Nov-2021 10:22 9 KB JEscott to previous | to last
62 26-Nov-2021 10:22 9 KB JMyers to previous | to last
61 26-Nov-2021 10:22 9 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
APPROVAL PROCESS
APPROVAL PROCESS

Version management

Difference between version and

At line 92 changed one line
Ex: a Manager may be away for a vacation and time sheets may need to be reviewed during that time frame so an alternate or replacement may be assigned specifically to “Time Sheets”. If there was a salary review during that time, it would remain the responsibility of the original manager to approve.
Example: A manager will be away on vacation and will need to have time sheets reviewed during that time frame, so an alternate or replacement may be assigned specifically to “Time Sheets”. However, if there was a salary review due during that time, it would remain the responsibility of the original manager to approve those salaries.
At line 94 changed one line
When responsibility is transferred from the approver to the designate for a replacement, all approval records previously created for notification are moved from the approver to the designate when the new designate record is saved. This will cause work flow, all approver screens and self service splash “to do” lists to now be full for the existing approvals previously required for the approver. Any new approvals required will create new approval records for the designate and the original approver will not be notified.
When responsibility is transferred from the approver to the designate for a replacement, all approval records previously created for notification are moved from the approver to the designate when the new designate record is saved. This will cause work flow, all approver screens and Self Service splash “to do” lists to now be full for the existing approvals previously required for the approver. Any new approvals required will create new approval records for the designate and the original approver will not be notified.
At line 106 changed 4 lines
Example:
Personnel Action where clause:
This condition is attempting to restrict to a position code. In order to do that the condition must start from a column on [p2k_sa_personnel_actions]. This example works its way from [p2k_sa_personnel_actions] then to the prime assignment on [p2k_hr_assignments] ,then to the effective details of that assignment ([p2k_hr_assignment_details]), then to the position ([p2k_cm_positions]) on that assignment as noted from the foreign keys in the condition column. The “value” is the restricted position code.
Example: There is a Personnel Action where clause that restricts the approval process to a position code. In order to do that the condition must start from a column on [P2K_SA_PERSONNEL_ACTIONS]. This example works its way from [P2K_SA_PERSONNEL_ACTIONS] then to the prime assignment on [P2K_HR_ASSIGNMENTS] ,then to the effective details of that assignment ([P2K_HR_ASSIGNMENT_DETAILS]), then to the position ([P2K_CM_POSITIONS]) on that assignment as noted from the foreign keys in the condition column. The “value” is the restricted position code.
At line 114 changed one line
__Approval Bar__
__Approval Bar__\\
This page (revision-69) was last changed on 26-Nov-2021 10:22 by kparrottTop