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 461 added 7 lines
;[Action|EVENT_CODE]:It is suggested to prefix all Open Enrollment workflow actions with OE. For this example, OE REMINDER will be used as the Action.
;[Status|EVENT_STATUS]:This field must set to In Production in order for the action to be picked up in [IMUC].
;[Triggered in Product |WORKFLOW PRODUCTS]:This field should be set to WF_BOEE since the email will fire when a new Open Enrollment Period is created.
;[Action Directed To|EVENT_RECIPIENT_TYPE]:Since this action is going to the employees, ‘Employee’ should be chosen.
;[Type|EVENT_MEDIA]:Email should be specified in this field.
;[Email|MEDIA_NAME]: Since Email was specified for Type, the From email address must be specified.
\\
At line 462 removed one line
At line 470 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. For example, WF_OE_REMINDER.
;[Description|DESCRIPTION]: This field should state what the user calc is meant for
;[Product |PRODUCT_CODE]:This field should be set to WF_BOEE.
;[Status |USER_CALC_STATUS]: In order for the action to be processed the user calc must be published in [IMUCA]
;[User Calc Type|USER_CALC_TYPE]: All workflow user calcs must have a type of Calculation
;[Usage|USER_CALC_USAGE]: Pro active workflow must have a usage of Pro-Active WF
At line 478 added 10 lines
__Lines__
||Line||CMD||Type 1||Operand 1||OPER||Type 2||Operand 2||Type 3||Operand 3||If GOTO||Else GOTO||Description
|10|ACT|AC|OE REMINDER|LOG |$S|CURRENT-DATE|RT|Employee| 99999| | This is a reminder that the benefit open enrollment period will be closing on <<BOE.ELECTION_CLOSE_DATE>>. Please ensure that you make your election decisions and submit your choices on or before this date.
|99999|EXIT| | | | | | | | | |
Line 10: This field calls the workflow action defined in [IMWA].
\\
At line 489 added one line
Where Clauses are used in ePersonality to conditionally select data from a table. In the case of Pro Active Work Flow, they are created to help the system filter data based on the specified criteria. This is done so that the user calcs do not have to be created with the conditions defined which helps ease the amount of work required by the backend processes. As a result, by the time the user calc is called the data has already been filtered down to the appropriate records.
At line 491 added one line
Where clauses can be created in either [IMWC] or [IMDAO].
At line 493 added 14 lines
The where clause would filter through the open enrollment periods to locate those that are Open and whose close date is 1 week away from the as of date. The system will then filter through the open enrollment to locate employee open enrollments which are 'open' meaning they have not been submitted yet.
;[Data Source|DATA_SOURCE_NAME]: The table in which the data in the where clause is retrieved from. For this example, the [P2K_BE_OPEN_ENROLLMENT_EES] table must be defined.
;[Where Clause|WHERE_CLAUSE_CODE]:This field holds the name of the user calc. For this example, OE REMINDER will be used.
;[Usage|WHERE_CLAUSE_USAGE]:The usage of the where clause is stated here. For this example, User Defined must be selected.
;[Description|DESCRIPTION]:This field holds a brief description of the intent of the where clause.
||Type||Predefined||Column Name||Operator||Value||Format Symbol
|Ad Hoc| |BOE_ID.ELECTION_CLOSE_DATE|Formatted Equals|<<AS_OF_DATE>> +7d|ddMMyyyy
|Ad Hoc| |ELECTION_STAGE|Equals|01|
|Ad Hoc| |BOE_ID.OPEN_ENROLLMENT_STATUS|Equals|01|
\\
At line 508 added 6 lines
The [UMPWF] function must be run to start the pro-active work flow. The idea behind the [UMPWF] is that the pro active work flow user calculations can be scheduled to run on a regular basis.
The [UMPWF] would be run with the following parameters:
|Product| WF_BOEE
|User Calc Code|WF_OE_REMINDER
|Where Clause|OE REMINDER