Hello,

I have a business requirement involving two applications, Application A and Application B,(both on the same server) each with its own distinct user base. These users primarily work within their respective applications. The two applications communicate with each other via APIs.

There is also a third user group, such as managers, who need to work across both applications. The business requires a unified worklist for these users, allowing them to avoid logging into each application separately.

To address this, we considered two options:

1. Implementing Process Fabric, which is not feasible at this time.

2. Developing a third wrapper application (Application C) which has built on application as  Applications A and B to provide a unified worklist and report access.

Have the following questions:

1. Is it a best practice to build a wrapper application (Application C) for this use case?

2. If we proceed with this approach, should the unique users of Applications A and B continue logging into their respective applications, or should the process be changed so that all users, including those specific to Applications A and B, log into Application C instead?

What would be the best practice in this scenario?

Thank you!