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

Version management

Difference between version and

At line 6 changed one line
To outline functionality in the Personality Admin and Self Service application approvals, using Approval Processes, Approval Steps, Approvers, Designated Approvers, and Approval Records.
To outline functionality in the eP2k Professional and Self Service application approvals, using Approval Processes, Approval Steps, Approvers, Designated Approvers, and Approval Records.
At line 22 changed one line
**Approval notification / workflow
**Approval notification / work flow
At line 32 changed one line
Processes are defined in IDAP with a APPROVAL_PROCESS_CODE which is standard to all code fields in Personality, a type of approval being defined using the APPROVAL_TYPE and a description.
Processes are defined in IDAP with a APPROVAL_PROCESS_CODE which is standard to all code fields in eP, a type of approval being defined using the APPROVAL_TYPE and a description.
At line 40 removed 2 lines
[Approvals_and_Authorization_01.jpg]
At line 44 removed one line
[Approvals_and_Authorization_02.jpg]
At line 49 changed one line
[{InsertPage page = 'X_APPROVER_TYPE'}]
||Abbreviation||Stored Value
|Department Manager|01
|Position Manager|02
|Assignment Manager|03
|First Manager|04
|Specified Person|07
|Spec List Of People|08
|Last Approvers Manager|09
|All Managers|10
At line 63 changed 2 lines
%%information People lists that are generated through Personality can only be used in this selection. These people lists use the "WHERE_CLAUSE" functionality as defined in [IMDAO]%%
[Approvals_and_Authorization_03.jpg]
%%information People lists that are generated through ep2k can only be used in this selection. These people lists use the "WHERE_CLAUSE" functionality as defined in [IMDAO]%%
At line 69 changed one line
When an approval Entity becomes eligible for approval. "Notification approval records" are created. These are approval records with the approval status of "Ready To Be Approved". There is one record for each identity defined as an approver for the first step of approval. These record in conjunction with workflow can be used to notify approvers of pending approvals.
When an approval Entity becomes eligible for approval. "Notification approval records" are created. These are approval records with the approval status of "Ready To Be Approved". There is one record for each identity defined as an approver for the first step of approval. These record in conjunction with work flow can be used to notify approvers of pending approvals.
At line 77 removed 2 lines
[Approvals_and_Authorization_04.jpg]
At line 85 changed 7 lines
Designate approvers will have the start and end dates qualified based on the current server date.
[Approvals_and_Authorization_05.jpg]
[Approvals_and_Authorization_06.jpg]
\\
At line 95 removed 4 lines
[Approvals_and_Authorization_07.jpg]
[Approvals_and_Authorization_08.jpg]
At line 100 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 workflow, 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 113 removed 2 lines
[Approvals_and_Authorization_09.jpg]
At line 122 changed 2 lines
[Approvals_and_Authorization_10.jpg]\\
At line 143 changed one line
Approval screens include different types to define, view, maintain and approve. This is possible in both Personality Admin and Self service. Some of the main driving screens are listed below for Personality. Self service has specific notation to the function name as WV???? and are located on several menus but generally in administrator or manager type roles.
Approval screens include different types to define, view, maintain and approve. This is possible in both eP and Self service. Some of the main driving screens are listed below for eP. Self service has specific notation to the function name as WV???? and are located on several menus but generally in administrator or manager type roles.
At line 248 changed one line
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 264 changed one line
This option is available in Personality 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 296 changed one line
;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 Personality people list.
;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.)
At line 361 changed 2 lines
!Approval Workflow Notification
Approval Records are used in several ways to compliment the approval system. One of the usages is Workflow. Workflow is provided on the table p2k_cm_approval_records. This enhances approvals by adding all standard features of workflow such as emails, user calcs and in turn procedures.
!Approval Work Flow Notification
Approval Records are used in several ways to compliment the approval system. One of the usages is Work Flow. Work flow is provided on the table p2k_cm_approval_records. This enhances approvals by adding all standard features of work flow such as emails, user calcs and in turn procedures.
At line 364 changed one line
The term "Notification records" has been used to describe the records created to "notify" an approver, say for example an assignment manager of a pending approval via email using workflow. If on step one an approver is required to make an approval. Once the approval entities stage is set to Stage_waiting_approval, an approval record or notification record is created. This record has a status of "Ready to be Approved" as defined in the lexicon X_APPROVAL_STATUS. Up to Approvers also get a notification record with the status of "Approval In Progress".
The term "Notification records" has been used to describe the records created to "notify" an approver, say for example an assignment manager of a pending approval via email using work flow. If on step one an approver is required to make an approval. Once the approval entities stage is set to Stage_waiting_approval, an approval record or notification record is created. This record has a status of "Ready to be Approved" as defined in the lexicon X_APPROVAL_STATUS. Up to Approvers also get a notification record with the status of "Approval In Progress".
At line 368 changed one line
Since approval records are used in a few ways to notify approver of pending approvals like screens (SS) and workflow, approval records are maintained in cases where the approval entity is deleted or cancelled. The approval record status is updated to cancelled and will have a comment made if deleted.
Since approval records are used in a few ways to notify approver of pending approvals like screens (SS) and work flow, approval records are maintained in cases where the approval entity is deleted or cancelled. The approval record status is updated to cancelled and will have a comment made if deleted.
At line 400 removed one line