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

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

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
82 26-Nov-2021 10:22 33 KB jaiken to previous
81 26-Nov-2021 10:22 33 KB jaiken to previous | to last WORK FLOW IN OPEN ENROLLMENT ==> WORKFLOW IN OPEN ENROLLMENT

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 16 changed 7 lines
;Step 1: Define Workflow Action in IMWA
;[Action |??]:Suggest prefixing all Open Enrollment workflow actions with OE.
;[Status|??]:The status must be set to “In Production” in order for IMUC to recognize the action.
;[Triggered in Product |??]:This field should be set to WF_BEV since the email will fire when a new life event record is inserted in the P2K_BE_EVENTS table.
;[Action Directed To |??]:Since this is going to a specific person, typically the person in charge of the benefit elections, Specific Employment should be chosen. The specific person code will be later defined in IMUC.
;[Type |??]:The type can be email or message.
;[Email|??]:If Email was specified for Type, the From email address must be specified. If Message was specified the Type, this field must be left blank.
;[Step 1 - Define Workflow Action in IMWA|]
The first step is to define the workflow action in [IMWA] that will be triggered when an employee records a life or work event.
At line 24 changed 6 lines
;Step 2: – Define User Calc in IMUC
;[User Calc|??]:It is suggested to prefix the user calc code with WF_OE to easily identify the workflow user calcs for Open Enrollment.
;[Description|??]:Should state what the user calc is meant for.
;[Product|??]: This field should be set to WF_BEV since the workflow action will fire when a new life event record is inserted in the P2K_BE_EVENTS table.
;[Status|??]: In order for the action to be processed, the user calc must have a status of “In Production”. User calcs are published in IMUCA.
;[User Calc Type |??]:All workflow user calcs must have the type set to ‘Calculation’.
;[Action |EVENT_CODE]:Suggest prefixing all Open Enrollment workflow actions with OE.
;[Status|EVENT_STATUS]:The status must be set to “In Production” in order for [IMUC] to recognize the action.
;[Triggered in Product |PRODUCT_CODE]:This field should be set to WF_BEV since the email will fire when a new life event record is inserted in the [P2K_BE_EVENTS] table.
;[Action Directed To |EVENT_RECIPIENT_TYPE]:Since this is going to a specific person, typically the person in charge of the benefit elections, Specific Employment should be chosen. The specific person code will be later defined in [IMUC].
;[Type |EVENT_MEDIA]:The type can be email or message.
;[Email|MEDIA_NAME_LK]:If Email was specified for Type, the From email address must be specified. If Message was specified the Type, this field must be left blank.
\\
;[Step 2 – Define User Calc in IMUC|]
The second step requires a user calc to be created to send the email to the Administrator.
At line 29 added 6 lines
;[User Calc|USER_CALC_CODE]:It is suggested to prefix the user calc code with WF_OE to easily identify the workflow user calcs for Open Enrollment.
;[Description|DESCRIPTION]:Should state what the user calc is meant for.
;[Product|PRODUCT_CODE]: This field should be set to WF_BEV since the workflow action will fire when a new life event record is inserted in the [P2K_BE_EVENTS] table.
;[Status|USER_CALC_STATUS]: In order for the action to be processed, the user calc must have a status of “In Production”. User calcs are published in [IMUCA].
;[User Calc Type |USER_CALC_TYPE]:All workflow user calcs must have the type set to ‘Calculation’.