Stephen Gilmore.

Workday CCB launch parameters

posted

It’s open enrollment time, and that means… running all the CCBs and trying to remember what each launch parameter needs to be. This is just a quick cheat sheet.1

Enrollment Parameters:

  • Effective Date: Reference date for when the enrollments or ended coverage become effective. This sets the end of the range to determine who to include on the file.
  • Last Update: Date/timestamp for when an enrollment change was entered (completed) in Workday. Similar to Effective Date, this sets the end of the range.

Include Ended Coverage or Change File Parameters:

  • From Effective Date: Sets the beginning of the effective date range for who to include on the file.
  • From Last Update: Sets the start of the date range for when the enrollment change is entered into Workday.

2023 Edit: lesson learned the hard way

I learned something the hard way this year with the launch parameters for OE on the “Guardian” template named Guardian: Dental, Vision, Insurance. When I ran the integration for OE, it didn’t include coverage end dates. It took a lot of guessing and checking to figure out what was going on and how to get the End Dates for ended coverage as part of OE.

What I originally did:

Original Launch Parameters - DID NOT WORK

Effective Date: 01/01/2023
Last Update: 12/15/2022 11:22:49.000 AM
From Effective Date: 12/15/2022
From Last Update: 12/15/2022 12:00:00.000 AM

With the above launch parameters, the end date for someone who waived a plan as part of OE was not coming across. The vendor expects to recieve a 349 record for ended coverage (348 is the start coverage date line). Ultimately, this is what did work:

Effective Date: 12/31/2022
Last Update: 12/15/2022 12:30:08.000 PM
From Effective Date: 10/01/2022
From Last Update: 10/01/2022 11:30:08.000 AM

These appear to be the “critical” components to getting the End Coverage records to show up:

  • The Effective Date needs to be in the same year to detect the end coverage date. As best as I can tell, this date seems to drive the Plan Year that the integration considers for changes.
  • The From Dates for change detection need to be dated before the Open Enrollment Event start date. If I picked a date that was after the OE start date and before a worker’s OE finalized date, the End Coverage records wouldn’t show up.
  • This template’s WBN - Full File - Include Ended Coverage Once configuration option is COVERAGE meaning: “Ended coverages are included only when all coverage in a plan type ends. The integration includes only the latest ended coverage.”
  • This template’s Ended Coverage History option is blank. This means, “The integration includes all ended coverages in output files.”

Open Questions:

After all this, I still have a few open questions and things to figure out before the next Open Enrollment event:

  • Since the Effective Date is 12/31/2022… Are the elections dated for 1/1/2023 included in the file, or does the vendor need two files from us, (1) End of 2022 file and (2) a beginning of 2023 file?
  • Do we have any other CCB templates that behave this same way?

Footnotes

  1. WD Community Link