POSITION APPROVAL FUNCTIONALITY#
In order to implement approvals of positions, IDPS must be extended.
- Positions will now be subject to approval if a function (IMFN) preference “DPS_APPRVL_REQ” 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 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 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.
POSITION APPROVAL LIMITATIONS#
Approval Process Definitions of Approvers will not support manager hierarchy in the case of position approvals.
