Hi All, Our Production Application (App A) is built on on CPMI Framework which is used by Call Center Team. Additionally, now we have a new requirement where the back-end team also needs to use some features (intents) from App A. But with the below constraints.

Reporting:  cases created by the back end team should not be visible to Call Center Team and Vice Versa. 

Specialization: Some of App A's intents are to be used by the Backend team with specialization

Additionally for the Back end team, Some new Intents are to be created.

Composite Tabs to be re-used.

The backend team solves the cases offline, they will not be going to make use of Phone, Call and Chat channels.

As we have to make use of few intents and composite tabs that are in App A, we have identified below with possible approaches.

1. Intents with Case Specialization, New Access Group for Backend team and Reporting with ABAC handling.

2. New Application Built on App A.  

Considering few important things like Specialization, Reporting, and Offline Cases handling we thought to go with the New Application approach which will give the advantage of Class and Ruleset Specialization, Security, and Reporting. On the other side for this New App, application-specific settings like Declare_CAApplicationsettings are to be maintained.

With approach #1 it will remain in same but maintenance may get overhead because of circumstance/when/decision shape/visibilities.

In the CPM Framework context having multi-layered Production applications like the below app stack acceptable or good to go or do we have to consider some other factors? 

Any points will be helpful considering the approaches listed.