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

Version management

Difference between version and

At line 5 changed one line
Approvals may be done in Personality or Self Service, by managers and/or administrators. Supervisors who log into the Manager Self-Service module can view and approve transactions initiated by their employees. Administrators who log into Personality or HR Self Service can view and approve transactions initiated by the employees they are authorized for.
Approvals may be done in [{$applicationname}] or Self Service, by managers and/or administrators. Supervisors who log into the Manager Self-Service module can view and approve transactions initiated by their employees. Administrators who log into [{$applicationname}] or HR Self Service can view and approve transactions initiated by the employees they are authorized for.
At line 10 changed one line
||Benefit Elections| Approval of benefits selected on the Personality or Self Service election forms is done on [IBEL] or WxDAR.
||Benefit Elections| Approval of benefits selected on the [{$applicationname}] or Self Service election forms is done on [IBEL] or WxDAR.
At line 13 added one line
||Classes| Approval of training classes is done on [ICRSC].
At line 17 removed one line
||Education| Approval of Candidates Education can be done in [IRCA] within the Education tab.
At line 26 removed one line
||References| Approval of Candidates References is done in [IRCA] within the References tab.
At line 28 removed one line
||Time Sheet Entries (Authorize)|Approval/Authorization of time sheet entries may be done in [WVPATC].
At line 30 changed one line
||Work History| Approval of Candidates Work History is done in [IRCA] within the Work History tab.
At line 81 changed 2 lines
!Approval Workflow Notification
Approval Records are used in several ways to compliment the approval system. One of the usages is Workflow, which is provided on the table [P2K_CM_APPROVAL_RECORDS].
!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.
At line 84 changed one line
This enhances approvals by adding all standard features of workfflow such as emails, user calcs and in turn procedures.
This enhances approvals by adding all standard features of work flow such as emails, user calcs and in turn procedures.
At line 86 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 89 changed one line
Since approval records are used in a few ways to notify approver of pending approvals like screens 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 93 added 47 lines
!!Approval Screens
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.
!Define Approval Process - ([IDAP])
Used to create approval processes, steps, approvers and to view approval records.
!View Pending Approval Records - ([IDVAP])
Used to View approval records which are “ready to be approved” indicating an approval process waiting approval. This will show all the identities for each step which could actually make the approval.
!View All Approval Records - ([IDVAR])
Used to view approval details and approve if the user has approval rights. This function is dynamic and displays different details specific to the approval entity. The example below is for a personnel action.
!View Approval Records - ([DDAPR])
Details of approvals and notifications may be viewed by day.
The [Approval Bar and Approval Action Button Functions|APPROVAL BAR AND BUTTON FUNCTIONS] page provides a list of the functions with either an approval bar or approval action button.
!!DEFAULT FUNCTIONALITY
!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”
Personnel Actions – PA Status mappings translating from pa_status to approval stage.
|Pending |Stage_WorkInProcess
|In Progress| Stage_WaitingApproval
|Submitted |Stage_WaitingApproval
|Failed Update| Stage_Approved
|Approved |Stage_Approved
|Completed |Stage_Approved
|Not Approved| Stage_Not_Approved
|Tracked Copy| Stage_Cancelled
|Cancelled| Stage_Cancelled
Personnel Actions – PA Status mappings translating from approval stage to pa_status
|Stage_WorkInProcess| Pending
|Stage_Not_Approved| Not Approved
|Stage_Cancelled| Cancelled
|Stage_WaitingApproval| In Progress
|Stage_Approved| Approved
!Generic Approvals
It is not necessary to always define an approval processes. When simply a sanity check of the data is required and anyone or everyone is required to review the data on the approval entity before it moves to the next status value, generic approvals may be used.
If an approval entity is moved to the approval stage “Stage_WaitingApproval” and there has not been an approval process defined a generic 1 step approval bar will be displayed. Any user with access to the function and data may approve this type of approval. No approval records are ever created. The status of the approval entity is simply updated to the next stage upon approval.
A generic approval would be displayed as below with the right mouse click menu:
At line 97 changed one line
This section has been replaced with the site preference described below.
This section has been replaced with the site preference described below available in 4.09
At line 99 changed one line
Two Self Service screens listed below have a toggle available for use located in the find block of each function. This toggle enables the data listed in the find block to change dynamically to show “potential” approvals verses “actual” approvals.
Two self service screens listed below have a toggle available for use located in the find block of each function. This toggle enables the data listed in the find block to change dynamically to show “potential” approvals verses “actual” approvals.
At line 101 changed 2 lines
|[WVDATS]|Approve Time
|[WVTSH]|Approve Employee Time and Exceptions
|WVDATS|Approve Time
|WVTSH|Approve Employee Time and Exceptions
At line 108 changed one line
The site preference [APPROVAL_WIP_REC(System_Preference)] now replaces the old simulation logic applied when trying to find the possible approvals an approver may need to make. This logic gives more of an accurate view of the up and coming approvals by monitoring specific tables defined by this preference.
The site preference APPROVAL_WIP_REC now replaces the old simulation logic applied when trying to find the possible approvals an approver may need to make. This logic gives more of an accurate view of the up and coming approvals by monitoring specific tables defined by this preference.
At line 110 changed one line
In [IMST], preference records may be added for table aliases, such as PTS.
In IMST, preference records may be added as in the above example for table TIME
At line 157 added 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 113 changed 2 lines
![Notes|Edit:Internal.APPROVAL+PROCESS]
[{InsertPage page='Internal.APPROVAL+PROCESS' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.APPROVAL+PROCESS]
[{InsertPage page='Internal.APPROVAL+PROCESS' default='Click to create a new discussion page'}]
At line 163 added one line
}]