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
APPROVAL PROCESS
APPROVAL PROCESS

Version management

Difference between version and

At line 79 removed 8 lines
!Approval Process And Approver Where Clauses
A where clause may be defined in [IMWC] or [IMDAO].
Once a where clause is defined it may be used to control what gets approved and by whom when using it at two levels. The first is by the approval process itself and the second is by each approver. In both cases the where clause must be relative to the approval entity as the base table.
Example: There is a Personnel Action where clause that restricts the approval process to a position code. In order to do that the condition must start from a column on [P2K_SA_PERSONNEL_ACTIONS]. This example works its way from [P2K_SA_PERSONNEL_ACTIONS] then to the prime assignment on [P2K_HR_ASSIGNMENTS] ,then to the effective details of that assignment ([P2K_HR_ASSIGNMENT_DETAILS]), then to the position ([P2K_CM_POSITIONS]) on that assignment as noted from the foreign keys in the condition column. The “value” is the restricted position code.
This page (revision-69) was last changed on 26-Nov-2021 10:22 by kparrottTop