Modular-based reuse in action​: Advanced topics on enterprise reuse for BA's

We are excited to announce an upcoming online webinar that's set to captivate the global business architecture community! Join us for an insightful session on advanced topics on modular-based reuse in action. Dive deep into the world of business architecture as we explore strategies to enhance enterprise reuse. Let's unravel the power of modular-based approaches and witness real-world examples in action. Mark your calendars and stay tuned for an engaging exchange of knowledge and ideas on low-code application development best practices.

Q. Will the library provide reusable assets from All layers? Can I see everything that is reusable across my organisation? 

A. The library shows you reusable assets that are available to your specific application. In the example covered today, we showed “Marc’s café app” that was built on reusable “modular layers” of Bread and Cake. This app could see in the library all reusable assets from those layers.  

We further showed “Paulo’s coffee cart”, who was only built on a reusable module of Coffee Beans. So both apps had different views of what was reusable in the library based on their layers.  

This ensures, I only reuse what was intended to be reused by my application, without overwhelming me with things I would never reuse. However, System Architects can easily include modules in your App, so when “Marc’s café” is ready to sell Coffee, they can include the Coffee Beans module, so I can start reusing assets from there. 

Q. I have an app that has been built for 3 years, how can I leverage reuse for that? 

The question was asked in the context of the reuse library. When you update to Infinity ’23, you’ll immediately see a few things: 

1. What layers are available to your app 

2. What reusable assets in those layers are built 

3. Which assets have been “marked relevant” for App Studio / Reuse 

What you will see really depends on what has been built over those 3 years, what layers were built, how much the app has adopted App Studio delivery and any Constellation UI adoption.  

I would expect some might see too much, and others too little. What is important is that the reuse library is a great visual starting point for reuse conversations and to move the desired strategic direction for your organisation/project.  

Check out more on https://docs.pega.com/bundle/platform/page/platform/app-dev/managing-reusable-assets-in-reuse-library.html 

Q. If you want to integrate them to an external webpage - can you explain what you mean there? Mash up's too? Aren’t' they usually very specific to case types? 

A. These methods of consuming a Pega were presented in the context of reuse. A Pega Centre-out™ business architecture,  is focused around reuse. When we build a journey, they can be consumed in different ways by different channels. The important things are you are building a journey once and then interacting with it via different channels to reuse it: 

• A Pega portal 

• Mashup or Web embed 

• DX API 

You’re not needing to build that journey 3 times, or maintaining 3 different sets of logic, you can build it once and reuse it across different channels.  

If you are interested in designing a reusable module which is channel-independent, check all the details in our Modular Business Architecture template