This page (revision-12) 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
12 26-Nov-2021 10:22 2 KB kparrott to previous
11 26-Nov-2021 10:22 2 KB jmyers to previous | to last DPS_APPRVL_REQ ==> DPS_APPRVL_REQ(System_Preference)
10 26-Nov-2021 10:22 2 KB JEscott to previous | to last
9 26-Nov-2021 10:22 2 KB JEscott to previous | to last WP-APPROVALS_ON_POSITIONS ==> APPROVALS ON POSITIONS
8 26-Nov-2021 10:22 2 KB JEscott to previous | to last
7 26-Nov-2021 10:22 2 KB JEscott to previous | to last
6 26-Nov-2021 10:22 2 KB RForbes to previous | to last
5 26-Nov-2021 10:22 1 KB RForbes to previous | to last
4 26-Nov-2021 10:22 239 bytes RForbes to previous | to last
3 26-Nov-2021 10:22 122 bytes RForbes to previous | to last EP-WP-Approvals on Positions-v01.doc ==> WP-APPROVALS_ON_POSITIONS
2 26-Nov-2021 10:22 122 bytes JLawler to previous | to last
1 26-Nov-2021 10:22 114 bytes JLawler to last

Page References

Incoming links Outgoing links
APPROVALS ON POSITIONS
APPROVALS ON POSITIONS

Version management

Difference between version and

At line 1 changed 30 lines
!!POSITION APPROVALS
A user now has the option of having an approval process triggered on the [position table|P2K_CM_POSITIONS] when certain fields are changed. By cloning the [IDPS], users will have the ability to specify which fields will trigger approvals and which fields will not.
In addition to approvals being generated, [workflow|MODULE-WF] has been added to the [P2K_CM_POSITION_DETAILS] table. This will allow notifications to be sent to [approvers|APPROVERS] once a change has been made informing them that there is an approval record requiring an action.
!!Functionality
In order to implement approvals of positions, [IDPS] must be extended.
*Positions will now be subject to approval if the function preference “[DPS_APPRVL_REQ(System_Preference)]” states it is required.
*The original [IDPS] will not display any positions that are in a status of “Waiting for Approval”. A new find block LOV with a where clause changed to include positions waiting approval will need to be added to the new extended form.
*Approvals on positions are driven from the position “standing” [lexicon|LEXICON] value. The lexicon associated to the column is [X_STANDING_APPROVAL] and its values stored in the order of a standard approval process\\
e.g. A new position is created with the standing of “Pending”. Once ready for review, the standing may be switched to “Waiting Approval”.
*When approvals are in place, a button will be available to change the standing from “Pending” to “Waiting Approval”.
*It is suggested to secure off the “standing” column on the extended [IDPS] form to avoid the value from being manually changed.
*Users will not be able to select “Waiting for Approval” or “Not Approved” on the original [IDPS] screen; the standing can only be changed on the extended [IDPS] screen.
*If an extended function has the [DPS_APPRVL_REQ(System_Preference)] preference set up, the standing will automatically be set to pending when a new position is created. Otherwise the user is responsible for setting the standing as a default on the original [IDPS] screen.
!! Required Set Up
In order for approvals to work on positions there is specific set up required. Please read the [Position Approval Set Up|POSITION APPROVAL SET UP] page for the steps required.
!!Limitations
The [approval process|APPROVAL PROCESS] definitions of [approvers|APPROVERS] will not support manager hierarchy in the case of position approvals.
----
![Notes|Edit:Internal.WP-APPROVALS_ON_POSITIONS]
[{InsertPage page='Internal.WP-APPROVALS_ON_POSITIONS' default='Click to create a new notes page'}]
*[POSITION APPROVALS]
*[POSITION APPROVAL FUNCTIONALITY]
*[POSITION APPROVAL SET UP]
*[POSITION APPROVAL LIMITATIONS]
This page (revision-12) was last changed on 26-Nov-2021 10:22 by kparrottTop