This page (revision-14) was last changed on 26-Nov-2021 10:22 by lurtan

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
14 26-Nov-2021 10:22 2 KB lurtan to previous
13 26-Nov-2021 10:22 2 KB lurtan to previous | to last
12 26-Nov-2021 10:22 2 KB lurtan to previous | to last
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 RForbes to previous | to last
9 26-Nov-2021 10:22 3 KB JEscott to previous | to last
8 26-Nov-2021 10:22 3 KB JEscott to previous | to last
7 26-Nov-2021 10:22 3 KB JEscott to previous | to last
6 26-Nov-2021 10:22 3 KB JEscott to previous | to last
5 26-Nov-2021 10:22 2 KB RForbes to previous | to last
4 26-Nov-2021 10:22 2 KB JLawler to previous | to last
3 26-Nov-2021 10:22 2 KB JLawler to previous | to last
2 26-Nov-2021 10:22 1 KB JLawler to previous | to last
1 26-Nov-2021 10:22 1 KB JLawler to last

Page References

Incoming links Outgoing links
POSITION APPROVAL SET UP
POSITION APPROVAL SET UP

Version management

Difference between version and

At line 1 changed 3 lines
*In order to set up approvals, the [IDPS] screen __MUST__ be copied. Use the [IMFN] screen to copy [IDPS] and make the following changes.
**Use the “copy function and form” to make a copy of [IDPS]. The system will default IDPS_EXT as the name of the [function|FUNCTION], however this can be over written to suit the users preference (For example: IDPSA, IDPS_APPROVAL, etc.). The description can also be edited.
**Once the new function has been created, add as a minimum, the [P2K_MASTER] [role|ROLE] on the execution rights tab.
!Step 1 - IMFN, Copy IDPS
In order to set up approvals, the [IDPS] screen __MUST__ be copied. Use the [IMFN] screen to copy [IDPS] and make the following changes.
*Use the “Copy Function and Form” to make a copy of [IDPS]. The system will default IDPS_EXT as the name of the [function|FUNCTIONS], however this can be over written to suit the users preference (For example: IDPSA, IDPS_APPROVAL, etc.). The description can also be edited.
* The Usage of the new function must remain as User Defined so that it is not overwritten with the next release of the application.
!Step 2 - IMFN, Add Security
Once the new function has been created add, as a minimum, the [P2K_MASTER] role on the execution rights tab.
At line 5 changed one line
**On the [Preferences|PREFERENCE] Tab the [function|FUNCTION] preference “[DPS_APPRVL_REQ]” will need to be set to “True”. This will result in approvals being tied to the new extended function. Log out and back in again.
!Step 3 - IMFN, Add Approval Preference
On the [Preferences|PREFERENCE] Tab the [function|FUNCTIONS] preference “[DPS_APPRVL_REQ]” will need to be set to “True”. This will result in approvals being tied to the new extended function. In order for the preference to be respected, you must log out and back in again.
At line 7 changed 2 lines
**Once the newly created function is in place, object security should be used to restrict all fields that will not require approvals. It is suggested to secure off the “standing” column on the extended [IDPS] form to avoid the value from being manually changed. You will not be able to select “Waiting for Approval” or “Not Approved” on the original IDPS screen this can only be changed on the extended [IDPS] screen.
*On [IDAP], the approvers and approval steps must be defined. By selecting ‘Positions’ in the Type field, the new approval process will be tied to the newly created [function].
!Step 4 - IMFOS, Add Object Security
Once the newly created function is in place, object security should be used to restrict all fields that will not require approvals. Object security for a form can be done in the [IMFOS] screen.
It is suggested to secure off the “standing” column on the extended [IDPS] form to avoid the value from being manually changed. You will not be able to select “Waiting for Approval” or “Not Approved” on the original IDPS screen this can only be changed on the extended [IDPS] screen.
!Step 5 - IDAP, Define Approval Process
*On [IDAP], the [approvers|APPROVERS] and approval steps must be defined. By selecting ‘Positions’ in the [Type|APPROVAL_TYPE] field, the new approval process will be tied to the newly created [function|FUNCTIONS].
At line 10 changed one line
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. (In this example, the where clause has been removed and all the status types are included on the extended form).
!Step 6 - IMLOVL, Define New Find Block
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. (In this example, the where clause has been removed and all the status types are included on the extended form).
At line 12 changed one line
*Once the new find has been created it will need to be attached to the newly created function on the IMFN screen.
!Step 7 - Add Find Block to New IDPS Function
Once the new find has been created it will need to be attached to the newly created function on the [IMFN] screen.
At line 32 added 2 lines
!Step 8 - Exit and Re-enter Application
This page (revision-14) was last changed on 26-Nov-2021 10:22 by lurtanTop