Please endorse Enhancement request - 112238

We have a need from our Life Insurance provider to offer two EOI rules. We opened up an incident and support shared with us that this isn't possible.

New hires are guaranteed issue up to a certain amount and then of course would need EOI for anything more than said amount. This pulls correctly in the system.

Associates who have been here since before a certain date are subject to eoi for any amount or any increase in amount currently enrolled in.

We would love for the system to be able to handle each eoi scenario. Please vote for this enhancement request.

Find more posts tagged with

Accepted answers

All comments

hhernan2

We have several different EOI rules attached to our life plan by creating different coverage rules and linking a different benefit group to each coverage rule. I believe you can accomplish this using different custom groups for the two groups of employees you described. For example, for our plan, those in an active marriage event would have 0 EOI days as compared to a new hire that would have 75 days. Within each rule, you should be able to adjust the EOI days/Guarantee limits according to your plan requirements.

ecloyd

Based on the information we received from Infor, this isn't possible for how we need it to work. I am going to try to test your suggestion though! I appreciate any help or guidance you may have.

reaganr

Hi Crissy, your approach to setting up EOI rules is very interesting! We created a custom action that runs a calculation on EOI and sets the proper amount according to our benefit plans. There is still one scenario we have left to calculate for in our custom action. I'll try your suggestion. Are you referencing a specific life event in the benefit group for the marriage coverage rule?

hhernan2

Yes, for one rule, I used a life event (Marriage event). Here is the syntax I used:

Active and (any Employee.AllEmployeeEnrollmentsRel.EmployeeEnrollment.BenefitEnrollmentEvent = "MARRIAGE") and (any Employee.AllEmployeeEnrollmentsRel.EmployeeEnrollment.ONDIsMarriageEventPeriodCurrentOND >= "Current")

I had to create a custom derived field (ONDIsMarriageEventPeriodCurrent) to return the enrollment period end date.

syntax:

type is Date

if (BenefitEnrollmentEvent = "MARRIAGE")

return EnrollmentPeriod.End

My group then includes any employee that has an active Marriage event. I was told by someone from Infor that the coverage rules are applied in alphabetical order by the benefit group attached, so I just named my groups according to which rule should be processed first since an employee could fall into both groups.

Hope this helps. Please keep me posted on the result of your tests and let me know if you have any questions.

Copyright © 2025 Infor. All rights reserved.