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 339 added 6 lines
;[Action|EVENT_CODE]:It is suggested to prefix all Open Enrollment workflow actions with OE. For this example, OE STUDENT 2 OLD 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_ECT since the workflow action is based on the [P2K_HR_CONTACTS] 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]:This field can be set to either Email or Message.
;[Email|MEDIA_NAME]: If Email was specified for Type, the From email address must be specified. If Message was specified this field must be left blank.
At line 346 added one line
At line 348 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_STUD_2_OLD.
;[Description|DESCRIPTION]: This field should state what the user calc is meant for
;[Product |PRODUCT_CODE]:This field should be set to WF_ECT.
;[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 342 removed one line
;[Step 3: Define Where Clause in IMWC|]
At line 344 changed one line
;[Step 4: Run UMPWF to Start the Pro-active Workflow|]
__Lines__
At line 359 added 32 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 STUDENT 2 OLD| LOG|$S|AS-OF-DATE|RT|42032|99999| |<<EID.FIRST_NAME>> <<EID.LAST_NAME>> student child recipient, <<ECT.FIRST_NAME>> <<ECT.LAST_NAME>> , is turning 25 next month. The Student will surpass the maximum student age defined for the benefit
|99999|EXIT| | | | | | | | | |
Line 10: This line calls the workflow action defined in [IMWA] (OE STUDENT 2 OLD) during the first step and will send an email to person code 42032.
;[Step 3: Define Where Clause in IMWC or IMDAO|]
Where Clauses are used in [{$applicationname}] 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|USERCALC] do not have to be created with the conditions defined which helps ease the amount of work required by the back end processes. As a result, by the time the [user calc|USERCALC] is called the data has already been filtered down to the appropriate records.
This example first filters the all of the data in the [P2K_HR_CONTACTS] table for birth dates that are not null.
The system then filters the data to determine if any of the contacts are turning 25 next month. The system is told to do this by using the Operator ‘Formatted Equals’ and the value being <<AS_OF_DATE>> +1M-25y, the [format symbol|DESCRIPTION] should be MMyyyy.
The system then filters the data further by checking to see which records have the [student indicator|STUDENT_INDICATOR] turned on in [IECT].
;[Data Source|DATA_SOURCE_NAME]: The table in which the data in the where clause is retrieved from. For this example, the [P2K_HR_CONTACTS] table must be defined.
;[Where Clause|WHERE_CLAUSE_CODE]:This field holds the name of the user calc. For this example, OE_STUDENT_2_OLD 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| |BIRTH_DATE| Is Not Null| |
|Ad Hoc| |BIRTH_DATE|Formatted Equals| <<AS_OF_DATE>>+1M-25y|MMyyyy
|Ad Hoc| |STUDENT_INDICATOR|Is Not Null| |
;[Step 4: Run UMPWF to Start the Pro-active Workflow|]
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.