Workday CCB field override example
This post is a quick note to my future self on one useful way of configuring a CCB field override. For the most part, integration maps on the CCB will handle this. But, there are times where the provider needs something “special” that breaks a 1:1 map to the plan(s).
.. Worker Business Object ..
... Field override to map a code to the worker/election on the integration file.
└── CF: Lookup Related Value Field on Worker
├── CF: Extract Single Instance on Worker from Benefit Elections Source Field
│ ├── Condition: CF: T/F Plan is One of the Relevant Plans
│ │ └── Conditions:
│ │ ├─ Waved is Blank
│ │ ├─ Benefit plan is in the list ____
│ │ └─ Coverage Begin Date for Benefit Plan <= Current Effective Date
│ ├── Sort Field: Coverage Begin Date for Benefit Plan & Coverage Level
│ └── Sort Direction: Descending, First occurence
└── CF: Eval Expression to map plan to codes on Benefit Election object
└── Map as many plans/rules <> codes as needed
A few things I learned the hard way about Current Effective Date
- It returns the effective date field form the CCB. This helps filter and sort benefit elections relative to the integration launch parameter(s).
- This is the date field to use to establish different rules for different plan years.