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

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
37 26-Nov-2021 10:22 20 KB rforbes to previous BSS_EVIDENCE_REQ(System_Preference) ==> BSS EVIDENCE REQ(System_Preference)
36 26-Nov-2021 10:22 20 KB jmyers to previous | to last BSS D REASON REQ ==> BSS D REASON REQ(System_Preference)
35 26-Nov-2021 10:22 20 KB jmyers to previous | to last BSS_EVIDENCE_REQ ==> BSS_EVIDENCE_REQ(System_Preference)
34 26-Nov-2021 10:22 20 KB jmyers to previous | to last
33 26-Nov-2021 10:22 20 KB jmyers to previous | to last
32 26-Nov-2021 10:22 20 KB jmyers to previous | to last
31 26-Nov-2021 10:22 29 KB jmyers to previous | to last
30 26-Nov-2021 10:22 32 KB jmyers to previous | to last
29 26-Nov-2021 10:22 35 KB jmyers to previous | to last
28 26-Nov-2021 10:22 37 KB jmyers to previous | to last
27 26-Nov-2021 10:22 37 KB jmyers to previous | to last
26 26-Nov-2021 10:22 38 KB jmyers to previous | to last
25 26-Nov-2021 10:22 39 KB jmyers to previous | to last
24 26-Nov-2021 10:22 43 KB jmyers to previous | to last
23 26-Nov-2021 10:22 43 KB jmyers to previous | to last
22 26-Nov-2021 10:22 43 KB jmyers to previous | to last
21 26-Nov-2021 10:22 43 KB jmyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 2 changed 3 lines
!!!STEPS TO SETTING UP OPEN ENROLLMENT
!!Open Enrollment Setup
!!!OPEN ENROLLMENT SET UP
At line 7 changed one line
!Step 1: IBPT – Define Benefit Plan Types
!!Step 1: IBPT – Define Benefit Plan Types
At line 16 changed one line
!Step 2: IMLN- Maintain Lexicons
!!Step 2: IMLN- Maintain Lexicons
At line 21 changed 2 lines
!Step 3: IMST – Define Client Site Information
By default decline reasons are required; however, if it is a client’s policy not to require reasons for declines, the site preference [BSS D REASON REQ] must be defined in [IMST] with a value of N.
!!Step 3: IMST – Define Client Site Information
By default decline reasons are required; however, if it is a client’s policy not to require reasons for declines, the site preference [BSS D REASON REQ|BSS D REASON REQ(System_Preference)] must be defined in [IMST] with a value of N.
At line 24 changed one line
The site preference [BSS_EVIDENCE_REQ] may be defined with a value of Y to force an employee to provide Evidence/Documentation during the Open Enrollment before they can submit their elections. If this is defined with a Y a validation message will be displayed to the employee. If a value of N is provided, the employee will still be prompted to submit evidence however they will still able to submit their elections if no evidence is uploaded.
The site preference [BSS EVIDENCE REQ(System_Preference)] may be defined with a value of Y to force an employee to provide Evidence/Documentation during the Open Enrollment before they can submit their elections. If this is defined with a Y a validation message will be displayed to the employee. If a value of N is provided, the employee will still be prompted to submit evidence however they will still able to submit their elections if no evidence is uploaded.
At line 26 changed one line
!Step 4: IPPGU / IPPGC – Define US/CDN Pay Categories
!!Step 4: IPPGU / IPPGC – Define US/CDN Pay Categories
At line 29 changed one line
!Step 5: IPPF – Define Processing Frequencies
!!Step 5: IPPF – Define Processing Frequencies
At line 32 changed one line
!Step 6: IBPN – Define Benefit Plans/Coverages
!!Step 6: IBPN – Define Benefit Plans/Coverages
At line 65 changed one line
!Step 7: IBSC – Define Benefit Schedule
!!Step 7: IBSC – Define Benefit Schedule
At line 69 changed one line
!Step 8: IDGR – Define Groups
!!Step 8: IDGR – Define Groups
At line 72 changed one line
!Step 9: IBET – Define Benefit Event Types
!!Step 9: IBET – Define Benefit Event Types
At line 81 removed 2 lines
At line 86 removed 3 lines
Proof Required
If employees are required to submit proof that the event took place, this toggle should be turned ON. For example, some carriers require a birth certificate or a marriage license.
At line 93 removed 5 lines
Event Type Text
This field allows for more information to be posted on the actual event type. This will also respect basic HTML tags. Again, this will be carried over to IBOE.
At line 93 added 2 lines
!!Step 10: IMFD – Maintain Form Definitions
In order for the employees’ election choices to be automatically saved when entered in [WEBOEE] the Auto Commit preference must be added to [WEBOEE] in [IMFD]. The value for the preference must be Y.
At line 106 removed 29 lines
Plans Affected
Plan Election Set
If there are Plan Election Sets that are to be included in the event, users can specify the Plan Election Set instead of listing each plan individually. This will group the plans within the plan set together.
Plan
Plans that are not part of a Plan Election Set but should be included in the enrollment should be listed individually.
Description
This is the benefit plan description which will default in once the plan has been selected.
Election Required
This is used to force the employee to elect a coverage from a plan. This toggle will default as checked ON if the plan’s participation rule is ‘Required’. For Plan Election Sets, if one plan in the set has ‘Required’ defined as the participation rule, then the toggle will be checked ON. This can be used to override the Participation rule for Open Enrollments by selecting or unselecting the toggle.
!Step 10: IMFD – Maintain Form Definitions
In order for the employees’ election choices to be automatically saved when entered in [WEBOEE] the Auto Commit preference must be added to the [WEBOEE] screen in [IMFD]. The value for the preference must be Y.
At line 141 changed 4 lines
!Step 11: IMRO – Define Roles
!!Step 11: IMRO – Define Roles
At line 151 removed one line
At line 163 removed 9 lines
Step 10: IMFD – Maintain Form Definitions
In order for the employees’ election choices to be automatically saved when entered in WEBOEE the Auto Commit preference must be added to the WEBOEE screen. The value for the preference must be Y.
Headers and Footers can be used to tailor the WEBOEE screen. If headers and/or footers are to be used, the preferences Header and/or Footer should be added to the screens in IMFD.
If birth certificate, marriage license or health questionnaire do not meet your business needs, the form item name prompts for these documents may be translated to something else. These media are used in WEBOEE, IBPOE and in VBOEE.
Additional media may be added to the WEBOEE form if documents other than birth certificate, marriage license, or health questionnaire are required. Media codes must first be defined in IMEC for P2K_HR_IDENTITIES. These new media codes would need to be added to the form definition for WEBOEE, IBPOE and VBOEE. The three existing media codes in WEBOEE can be used as an example.
Step 11: IMRO – Define Roles
In order for employees to make use of Open Enrollment execution rights for the Open Enrollment, forms and reports must be given to the appropriate execution type roles.
Since there are two My Benefit Elections forms, WEBEL and WEBOEE, ensure that execution rights are granted to only one of the forms. To make use of Open Enrollment, employees must have access to WEBOEE.
Access to the following new forms and reports should be granted to the appropriate users: IBET, IBOE, IBPOE, VBOEE, IBEV, RBET, RBOE, UBOE, UBPOE.
At line 173 removed 14 lines
Approvals in Open Enrollment
• Approvals in the Benefit Open Enrollment facility are done at the Open Enrollment level, not at a plan level. Therefore, the Benefit Administrator will be approving an employee’s Open Enrollment in IBPOE; he/she will not be approving each individual plan election.
• The approval processes for Benefit Open Enrollment must be defined with a type of Open Enrollment EEs. The function the processes are tied to is IBPOE.
• The process can consist of a single or multi-stepped sequence.
• Approval processes for different events can be handled via where clauses. The where clause would filter the open enrollments based on event type.
• All Open Enrollments must be approved before they can be processed.
• If no approval process is defined or the employee’s Open Enrollment is not filtered to a specific Open Enrollment approval process a system generated generic approval process will be used.
• The Sample Approval section provides sample approval processes that may be defined.
• For further information on setting up Approvals please review the EP-WP-Approvals white paper.
Open Enrollment Messages
• There are many messages in the Benefit Open Enrollment facility that are portrayed to the users in both the Professional and Self Service side of Personality. These messages can be translated to a different language or edited to suit your business needs.
• Messages are only created once they have been issued to the users in Personality, therefore they will only display in IMMS once they have been created (issued to a user). Once the message code and text display in IMMS they can be translated.
• Please review the WSA manual for more information on how to use the translations functionality.
• The following are the message codes, their descriptions and where they are used in the Open Enrollment facility.
At line 188 removed 6 lines
Message Code Message Text Displayed In
BBR_00002 Your elected student <<CONTACT_NAME>> is older than the coverage's Maximum Student Age restriction of <<MAXIMUM_STUDENT_AGE>>. WEBOEE & IBPOE
BBR_00003 Your elected child <<CONTACT_NAME>> is older than the coverage's Maximum Child Age restriction of <<MAXIMUM_CHILD_AGE>>. WEBOEE & IBPOE
BBR_00004 Coverage requires that <<CONTACT_NAME>> be a child recipient. WEBOEE & IBPOE
BBR_00005 This coverage requires benefit recipients be elected. WEBOEE & IBPOE
BBR_00006 <<CONTACT_NAME>> for plan <<PLAN_CODE>> has a future dated recipient record. The recipient record will not be updated with this Open Enrollment. Please review <<EMPLOYEE_NAME>>'s election changes and update the recipient record accordingly IBPOE & UBPOE
At line 195 removed 43 lines
BBR_00007 <<CONTACT_NAME>> for plan <<PLAN_CODE>> cannot be changed. Please review <<EMPLOYEE_NAME>>'s election changes and update the recipient record accordingly IBPOE & UBPOE
BBR_00008 Your elected recipient <<CONTACT_NAME>> is older than the coverage's Maximum Disabled Age restriction of <<MAXIMUM_DISABLED_AGE>>. WEBOEE & IBPOE
BEPS_00001 This Coverage allows a maximum of <<BCG_ID.NUMBER_RECIPIENTS>> benefit recipient(s) to participate. WEBOEE & IBPOE
BEPS_00002 A required plan cannot be declined. IBPOE
BEPS_00003 This coverage requires an answer to all of the mandatory questions in the <<ASSESSMENT_DESCRIPTION>> in order to pass the validation process WEBOEE & IBPOE
BEPS_00004 This coverage requires you to answer the questions in the <<ASSESSMENT_DESCRIPTION>> in order to pass the validation process and submit your elections WEBOEE & IBPOE
BEPS_00005 This coverage requires an amount to be specified WEBOEE & IBPOE
BEPS_00006 Evidence Required for this coverage. Please upload the required documents WEBOEE & IBPOE
BEPS_00007 Grand Total WEBOEE
BET_00001 Enter life event information. WEBEV
BEV_00001 The Event Date is too far into the past. Please contact your Benefit Administrator to discuss an Open Enrollment Period WEBEV & IBEV
BEV_00002 Your event has been recorded. This type of event requires proof, please navigate to the Pending Proof tab to upload the required documentation. Your Benefit Administrator will be in contact to discuss an Open Enrollment Period. WEBEV & IBEV
BEV_00003 Event <<BET_ID.BE_EVENT_TYPE_CODE>> has been submitted. WEBEV & IBEV
BEV_00004 A record has already been created for Event Type: <<BE_EVENT_TYPE_CODE>> Employee: <<PERSON_CODE>> and Event Date: <<BE_EVENT_DATE>> IBEV & WEBEV
BEV_00005 The Election Opened and Closed Dates for the corresponding Open Enrollment will also be updated with the new Event Date. IBEV
BOEE_00002 A decision must be made for the plan set <<DRV_PLAN_ELECTION_SET_CODE>>. WEBOEE & IBPOE
BOEE_00003 A decision must be made for the plan <<DRV_PLAN_ELECTION_SET_CODE>>. WEBOEE & IBPOE
BOEE_00005 By submitting your benefit elections you will no longer be able to make changes to your elections. Please ensure that all of the information is correct before pressing submit. WEBOEE & IBPOE
BOEE_00006 You cannot submit the open enrollment until all of the election options are valid. WEBOEE & IBPOE
BOEE_00007 All of the elections have passed the validation process. You may now submit the open enrollment. WEBOEE & IBPOE
BOEE_00008 One or more elections have failed the validation process. Please review each plan for any indicated corrections you need to make. WEBOEE & IBPOE
BOEE_00009
Press OK to re-open all of the plans for the current Open Enrollment. IBPOE
BOEE_00010 You cannot submit the open enrollment until you provide a reason for decline WEBOEE & IBPOE
BOEE_00011 Open Enrollment for <<FIRST_NAME>> <<LAST_NAME>>, ( <<PERSON_CODE>> ) Event Type: <<BE_EVENT_TYPE_CODE>> Coverage Effective: <<COVERAGE_EFFECTIVE>> has a stage of <<ELECTION_STAGE>> IDVAR
BOEE_00012 Benefit elections have been successfully submitted WEBOEE & IBPOE
BOEE_CONTEXT <<EEM_ID.EID_ID.FIRST_NAME>> <<EEM_ID.EID_ID.LAST_NAME>> has an Open Enrollment for the Event Type <<BOEE.BOE_ID.BET_ID.BE_EVENT_TYPE_CODE>>
IBPOE
Open Enrollment Questions
Open Enrollments may now be configured to ask questions within the WEBOEE screen. Questions may be asked using the Assessment logic.
Questions are defined in IBAS, a new assessment screen strictly for benefit open enrollments. Questions may be single answer or text.
The open enrollment assessment must have a type of ‘Benefit Open Enrollment’. Only assessments of this type are visible in the IBAS, and only these types of assessments are picked up for benefit processing. If the employees are allowed to change their answers, the toggle ‘Allow Question Review’ must be checked ON in IBAS. If this is not turned on then the employee will not be able to re-open the OE Questions/Assessment Event to change their responses.
Once an assessment is created in IBAS the Assessment Code may be selected in IBPN in the Coverage Details tab. Only one Assessment Code may be tied to a Coverage, however each Coverage within a plan may have a different Assessment Code.
In WEBOEE when an employee elects a coverage with an associated Assessment, a link/button called OE Questions will appear (below the list of recipients) allowing the employee to click on the button to open the assessment screen. The employee will be navigated through the questions, once the questions are answered the Complete button will appear in the assessment screen, once pressed the screen will close and the employee may carry on with their benefit elections. If the assessment has mandatory questions, the employee will not be able to submit the Open Enrollment until the questions have been answered. A validation message has been added to notify the employees of any mandatory unanswered questions.
When an employee elects a Coverage with an associated Assessment, an Assessment Event is created. The status of the event will be set to ‘Planned, Conf’. The status will change to ‘Completed’ once the employee has finished answering the questions and pressing the ‘complete’ button within the assessment window. If the employee needs to change their answers to the questions they may press the ‘ReOpen Questions’ button beneath the ‘OE Questions’ button. The reopen button will change the status of the assessment back to ‘Planned, Conf’, the previous responses will remain visible and any changes the employee make will update the original assessment.
The questions and responses may be seen in IBPOE and in VBOEE in the OE Questions tab. The Administrator cannot change the employee’s answers here. If the Administrator needs to take the assessment on behalf of the employee, the Administrator must use the WABPOE screen as Assessments cannot be taken within the Professional side of ePersonality.
Once an Open Enrollment is processed, the assessment and its responses will be tied to the employee’s enrollment detail record in IBEN. This is so the Administrator can report off of the responses.
The VBOEE screen has also been enhanced with the OE Questions tab to show the questions and responses affiliated to an elected coverage.