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

This page was created on 26-Nov-2021 10:22 by KHanson

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
53 26-Nov-2021 10:22 11 KB jaiken to previous
52 26-Nov-2021 10:22 11 KB kparrott to previous | to last
51 26-Nov-2021 10:22 11 KB jmyers to previous | to last
50 26-Nov-2021 10:22 11 KB jmyers to previous | to last
49 26-Nov-2021 10:22 11 KB jmyers to previous | to last
48 26-Nov-2021 10:22 11 KB jmyers to previous | to last
47 26-Nov-2021 10:22 10 KB jmyers to previous | to last
46 26-Nov-2021 10:22 10 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
45 26-Nov-2021 10:22 10 KB jmyers to previous | to last WORK_RULE_CODE ==> WORK_RULE (Field)
44 26-Nov-2021 10:22 10 KB JMyers to previous | to last
43 26-Nov-2021 10:22 10 KB JMyers to previous | to last
42 26-Nov-2021 10:22 10 KB JMyers to previous | to last
41 26-Nov-2021 10:22 10 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
IDDP
IDDP

Version management

Difference between version and

At line 120 added one line
This tab allows you to define a Department Coordinator for different types of roles. The Department Coordinator functionality is open ended to allow you to specify any kind of departmental role. The department coordinator can then be the recipient of emails generated by workflows.
At line 121 changed 3 lines
A new tab has been added to the Department Definition (IDDP) screen to define a “department coordinator” for different types of roles. The Department Coordinator functionality is open ended to allow you to specify any kind of departmental role. This department coordinator can then be the recipient of emails generated by workflows.
There are 10 different coordinator types that can be used and there is no specific logic behind the types. These can be used as required.
The workflow engine will use the coordinator that starts before / end after the date of the action.
There are ten different coordinator types that can be used with no specific logic behind the types. These can be used as required.
The workflow engine will use the Department Coordinator that starts before/end after the date of the action.
At line 126 changed 4 lines
Example: There is a business role of Manager of Compensation. There are 3 managers assigned to specific departments and should receive the workflow correspondence (email only).
Set Up
1. Update the managers’ positions onto the departments. SQL can be used to do so (P2K_CM_COORDINATORS).
If the positions are used when a person leaves the position and another person fills the position there is less maintenance required versus using the
%%information __Example__\\There is a business role of Manager of Compensation. There are three managers assigned to specific departments and should receive the workflow correspondence (email only).\\__Set Up__\\
#Update the managers’ positions onto the departments. SQL can be used to do so ([P2K_CM_COORDINATORS]).\\If the positions are used when a person leaves the position and another person fills the position there is less maintenance required versus using the
#On the [IMWA], use the “Action Directed To” the value of Department Coordinator.
#Add the workflow UserCalc logic ([IMUC]); use the Recipient Type equal to the Coordinator Type.%%
At line 131 removed 9 lines
2. On the IMWA, use the “Action Directed To” the value of Department Coordinator.
3. Add the workflow UserCalc logic (IMUC). Use the Recipient Type equal to the Coordinator Type.
This page (revision-53) was last changed on 26-Nov-2021 10:22 by jaikenTop