This page (revision-23) was last changed on 26-Nov-2021 10:22 by Karen Parrott

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

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
23 26-Nov-2021 10:22 31 KB Karen Parrott to previous
22 26-Nov-2021 10:22 31 KB kparrott to previous | to last
21 26-Nov-2021 10:22 31 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
APPROVALS AND AUTHORIZATIONS
APPROVALS AND AUTHORIZATIONS

Version management

Difference between version and

At line 230 changed 4 lines
STANDARD FUNCTIONALITY
Empty Approval Step
When an approval process has been initiated each step is displayed in the approval bar which is visible in certain approval screens. Approvers who qualify for approval by the where clause will be notified of a pending approval to be made. After such approval the next step is assessed for the current approvers. If the next step is lacking approvers from either an empty definition or the defined approver is disqualified via a where clause that empty step is ignored.
When a step is ignored it will not show in the approval bar or have approval notification records created. It will appear as if the approval process did not have that step defined. When the empty step is the last step in the process the last approval made will be considered final approval and the approval entity will be updated to the “approved” stage.
!!STANDARD FUNCTIONALITY
!Empty Approval Step
When an approval process has been initiated each step is displayed in the approval bar which is visible in certain approval screens. Approvers who qualify for approval by the where clause will be notified of a pending approval to be made. After such approval the next step is assessed for the current approvers. If the next step is lacking approvers from either an empty definition or the defined approver is disqualified via a where clause that empty step is ignored.
When a step is ignored it will not show in the approval bar or have approval notification records created. It will appear as if the approval process did not have that step defined. When the empty step is the last step in the process the last approval made will be considered final approval and the approval entity will be updated to the "approved" stage.
At line 235 changed 4 lines
Approval Process – Where clause = PEAS Personnel Actions only.
Step 1, Approver = Department Manager (no where clause)
Step 2 , Approver = HR personnel Specific person ( Where Clause – where wage Scale/Step is the last step sequence 3)
The assignment manager creates a new Personnel Action for a salary increase in PEAS for a salary increase to the next step. (2 of 3)
Approval Process - Where clause = PEAS Personnel Actions only.
Step 1, Approver = Department Manager (no where clause)
Step 2 , Approver = HR personnel Specific person ( Where Clause – where wage Scale/Step is the last step sequence 3)
The assignment manager creates a new Personnel Action for a salary increase in PEAS for a salary increase to the next step. (2 of 3)
At line 247 changed one line
!Approver Options
Approvers may be defined with fours options. These options are "up to approval", "allow send back", "allow decline" and "allow change". Only applies to a second level of approval or higher. Once that level of approval is reached the approver will be notified of the pending approval. At that time the approver now has three possible actions to make.
At line 249 changed 3 lines
Approver Options
Approvers may be defined with fours options. These options are “up to approval”, “allow send back”, “allow decline” and “allow change”. Only applies to a second level of approval or higher. Once that level of approval is reached the approver will be notified of the pending approval. At that time the approver now has three possible actions to make.
;Up to Approval:When Up to Approval is checked that approver is eligible to approve entities which they qualify for via the where clause, including entities that are waiting approval on a step with a lower sequence. When up to approval is granted "notification records (approval records)" will be created with a status of "Approval In Progress" (Notification records are discussed further in Approval Notification /Workflow).
At line 253 changed 2 lines
Up to Approval
When Up to Approval is checked that approver is eligible to approve entities which they qualify for via the where clause, including entities that are waiting approval on a step with a lower sequence. When up to approval is granted “notification records (approval records)” will be created with a status of “Approval In Progress” (Notification records are discussed further in Approval Notification /Workflow).
;Allow Send Back:This setting applies to a second level of approval or higher. If at the time of approval the approver does not like what they see the option to send the entity back to the beginning of the approval process is available. This will set all previous step approvals (approval records) to have a status of "Approval Sent Back" which will cause the first step approvers to be notified (via new approval records) to once again approve the entity. Comments as to why the send back was made may be entered if necessary.
At line 256 changed 6 lines
Allow Send Back
This setting applies to a second level of approval or higher. If at the time of approval the approver does not like what they see the option to send the entity back to the beginning of the approval process is available. This will set all previous step approvals (approval records) to have a status of “Approval Sent Back” which will cause the first step approvers to be notified (via new approval records) to once again approve the entity. Comments as to why the send back was made may be entered if necessary.
This option is available in eP as an option in the right mouse click menu over the appropriate step on the approval bar.
This option is available in eP as an option in the right mouse click menu over the appropriate step on the approval bar.
At line 263 changed 2 lines
Allow Decline
This setting allows the approver to decline the approval entity. The option is applicable to all steps the approver is responsible for. If a decline is made the approval process is complete, no further approval notification is necessary. This option is available in the right mouse click menu. Comments as to why the decline was made may be entered if necessary.
;Allow Decline:This setting allows the approver to decline the approval entity. The option is applicable to all steps the approver is responsible for. If a decline is made the approval process is complete, no further approval notification is necessary. This option is available in the right mouse click menu. Comments as to why the decline was made may be entered if necessary.
At line 266 changed 3 lines
Allow Change
This setting will cause the approval entity to be editable or not during the approval. In cases where the approver is allowed to view only while making the approval.
;Allow Change:This setting will cause the approval entity to be editable or not during the approval. In cases where the approver is allowed to view only while making the approval.
At line 275 changed one line
Once an approval entity has entered the approval stage (explained below) of "Stage_WaitingApproval" CRUD will be controlled to the appropriate approver. This means that only approvers who have rights to approve on the current step with "allow change" rights will be able to edit the information displayed.
Once an approval entity has entered the approval stage (explained below) of "Stage_WaitingApproval" CRUD will be controlled to the appropriate approver. This means that only approvers who have rights to approve on the current step with "allow change" rights will be able to edit the information displayed.
At line 277 changed 2 lines
Approver Derivation
Department Manager - Used for approval entities which are employee based and is the person who manages the department for that employee. Example. If approving a time sheet; the person who manages the department in which the owner of the time sheet works will be the approver. This person is derive by first looking if a specific person has been defined as the manager in IDDP. This is defined by a specifying a person or a supervisory position.
!Approver Derivation
;Department Manager:Used for approval entities which are employee based and is the person who manages the department for that employee. Example. If approving a time sheet; the person who manages the department in which the owner of the time sheet works will be the approver. This person is derive by first looking if a specific person has been defined as the manager in IDDP. This is defined by a specifying a person or a supervisory position.
At line 283 changed one line
Position Manager - Used for approval entities which are employee based and is the person who manages the position for that employee. Example: If approving a time sheet; the person who manages the position in which the owner of the time sheets works will be the approver. This is defined by specifying a person or another position which manages it.
;Position Manager:Used for approval entities which are employee based and is the person who manages the position for that employee. Example: If approving a time sheet; the person who manages the position in which the owner of the time sheets works will be the approver. This is defined by specifying a person or another position which manages it.
At line 285 changed one line
When a specific person is not defined then the first active incumbent found in the Reports to position will be set as the manager.
When a specific person is not defined then the first active incumbent found in the Reports to position will be set as the manager.
At line 287 changed 2 lines
If no active employee is found in that position the manager of that position will be found in the same manner until a position is found where it is not reporting to another position.
Assignment Manager - Used for approval entities which are employee based and is the person who is defined as the manager for that employee on their current assignment details (IEAS).
If no active employee is found in that position the manager of that position will be found in the same manner until a position is found where it is not reporting to another position.
;Assignment Manager:Used for approval entities which are employee based and is the person who is defined as the manager for that employee on their current assignment details (IEAS).
At line 290 changed 6 lines
First Manager - Used for approval entities which are employee based and is the first manager found defined in a pecking order of assignment manager, position manager and finally department manager for that employee. If no assignment manager is found then the manager of the position will be searched, if no active employee is found then the manager of the department is searched. The logic for each is described above. Only the first employee found in this order will be used.
Specified Person - Used for all approval entities, employee based or not. This allows an approval administrator to set a specific employee as an approver.
Specific List of People - Used for all approval entities, employee based or not. This allows an approval administrator to set specific people as an approver. This list of people is defined in IMPL and must be an eP people list (p2k people lists are not supported.)
Last Approvers Manager - Used for all approval entities, employee based or not. This approver type is not intended to initiate an approval process(any approver on step 1). There must be at least 1 approval made on a previous step and only applies if the previous step was approved and not declined or sent back. This type uses the logic in "First Manager" as described above.
All Managers - Used for approval entities which are employee based. This will set each manager found as an approver. The first manager defined on the assignment, position and department will have approval notification record created.
All manager type approvers are searched for based on a date in context to the approval entity. This will be the date used to search date sensitive details.
;First Manager:Used for approval entities which are employee based and is the first manager found defined in a pecking order of assignment manager, position manager and finally department manager for that employee. If no assignment manager is found then the manager of the position will be searched, if no active employee is found then the manager of the department is searched. The logic for each is described above. Only the first employee found in this order will be used.
At line 297 changed 2 lines
Approval Stages
Approval Entities are managed by stages. Simplified for example - “before”, “during” and “after”. Each stage is mapped for each approval entity. This enables each entity to manage them selves to their specific business status descriptions. These are lexicon columns on the entity which describe their status or authorization requirements. The personnel actions mapping is given as an example below. For this example the “before” is stage_WorkInProcess, “during” is Stage_WaitingApproval and “after” is either “Stage_approved”, “Stage_Not_approved” or “Stage_Cancelled”
;Specified Person:Used for all approval entities, employee based or not. This allows an approval administrator to set a specific employee as an approver.
;Specific List of People:Used for all approval entities, employee based or not. This allows an approval administrator to set specific people as an approver. This list of people is defined in IMPL and must be an eP people list (p2k people lists are not supported.)
;Last Approvers Manager:Used for all approval entities, employee based or not. This approver type is not intended to initiate an approval process(any approver on step 1). There must be at least 1 approval made on a previous step and only applies if the previous step was approved and not declined or sent back. This type uses the logic in "First Manager" as described above.
;All Managers:Used for approval entities which are employee based. This will set each manager found as an approver. The first manager defined on the assignment, position and department will have approval notification record created.
All manager type approvers are searched for based on a date in context to the approval entity. This will be the date used to search date sensitive details.
!Approval Stages
Approval Entities are managed by stages. Simplified for example - "before", "during" and "after". Each stage is mapped for each approval entity. This enables each entity to manage them selves to their specific business status descriptions. These are lexicon columns on the entity which describe their status or authorization requirements. The personnel actions mapping is given as an example below. For this example the “before” is stage_WorkInProcess, “during” is Stage_WaitingApproval and “after” is either “Stage_approved”, “Stage_Not_approved” or “Stage_Cancelled”
This page (revision-23) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop