AnsweredAssumed Answered

Single App with Multiple EDCs/Business Sources

Question asked by William May on Nov 12, 2018
Latest reply on Nov 13, 2018 by Mostafa Helmy

I'm looking for some validation on an approach to collecting an application. The app in question has a single account repository, an app level entitlement repository and multiple LOB entitlement repositories (different schema owner on backend), each owned separately from a business owner point of view.

 

Account Repository

Overarching Entitlement Repository

LOB Entitlement Repository 1

LOB Entitlement Repository 2

LOB Entitlement Repository 3

etc...

 

Our thoughts on collecting these would be to have the following Business Sources created in Aveksa:

Application - Enterprise Level: ADC, EDC for overarching entitlement repository

Application - LOB 1: only EDC for entitlement repository 1, resolved against ADC from first app

Application - LOB 2: only EDC for entitlement repository 2, resolved against ADC from first app

Application - LOB 3: only EDC for entitlement repository 3, resolved against ADC from first app

etc...

 

This approach would allow us to separate ownership of reviews/approvals, and draw clear lines between the entitlements which belong to each respective repository.

 

I'm trying to think through if this will cause me any unexpected issues. Has anyone ever implemented an application using this approach, and if so, any pointers or pitfalls to avoid?

 

Thanks,

Bill

7.0.2 P07

Outcomes