From the Carrier standpoint:
Looking for Limra/Carrier recommendations for processing multi/array of employee LDEx BEM transmissions as well as responding appropriately with LDEx RSP
All scenarios assume a single transmission (Represented as one transmissionGUID) containing >1 employee objects
processing with LDEx BEM
- Partial processing for small/medium 10 Employees - If issue is identified upfront (synchronously) for one or more employees are Carriers failing and refraining from accepting the entire transmission?
- Partial processing for large >100 Employees - same question above
responding asynchronously w/ LDEx RSP
- For accepted - single transmission small/medium 10 Employees - If downstream processing failures occur for one or more employees
- Is it sufficient to respond with LDEx RSP asynchronously one transaction for each employee failure related back to the source transmissionGUID
- OR - aggregate all employee failure into one transaction relating back to source transmissionGUID
- For accepted - single transmission large >100 Employees - If downstream processing failures occur for one or more employees
- same questions (1,2) above
1 transmission 10 Employees - to relate to API requests
1 transmission >100 Employees - to relate to potentially file based transmissions
#LDEx-API#LDEx-BEM#LDEx-Implementation------------------------------
Stephen Cocuzza
Tech Lead, Software Developer
Prudential
Newark NJ
------------------------------