Case Management Studio

We are currently using Appian Case Management Studio (CMGT) as a base application in our organization. On top of this, several separate applications have been built for different business sectors.

The issue is that each of these applications appears to be using a copied version of the “My Cases” module rather than extending or reusing the core CMGT “My Cases” functionality. This has resulted in multiple duplicated implementations of essentially the same case listing and interaction layer, each diverging slightly per application.

We are trying to understand the best practice for handling this pattern in Appian:

• How can we properly extend or customize “My Cases” functionality per application while still relying on the same base CMGT module?
• Is there a recommended approach for reusing the CMGT case views (e.g., configuration, overrides, or parameterized interfaces) instead of duplicating the module?
• What is the cleanest architecture pattern to avoid multiple forked versions of “My Cases” across applications while still allowing sector-specific requirements?

Any guidance on how to structure this properly within CMGT best practices would be appreciated.