Skip to main content

Pega Express best practice Reuse Strategy

Updated on July 1, 2024

Take advantage of the unique qualities of the Pega Situational Layer Cake™ and Pega Platform™ low code capabilities to empower your organization to reuse business processes, decisions, data, integrations, and other application components across business domains. In doing so, you can quickly respond to changing business and technology drivers while laying the foundation to accelerate enterprise transformation.

What is Reuse? 

Reuse refers to using the same software resources across multiple applications or systems within an organization.

The best and easiest way to configure, scale and govern reusable components is to take a modular approach.  A module is a collection of rules that perform a specific purpose, for example, retrieving an employee record, or updating a customer contact method. A module contains processes, flows, decisions, views or other reusable rules that address a business, integration, or utility use case, as shown below:

Types of reuse module
There are three types of reuse module

Using Pega’s patented Situational Layer Cake, organizations can easily manage reusable modules in layers across geographies, lines of business, and other business facets. Changes to a module that are made in one place are reflected everywhere, at once, across the enterprise.

The diagram below illustrates a modular Situational Layer Cake design pattern. This is the optimal way to organize reusable low code assets across the enterprise:

Reuse Strategy; Situational Layer Cake
Optimal Situational Layer Cake setup for reuse

Why does Reuse add value? 

Reuse is the strategic best practice of designing and configuring applications with the longer-term roadmap, scale, and needs of the enterprise in mind.

By providing the ability for both your professional and citizen developers to draw upon reusable components, reuse enables rapid implementation of applications that can be quickly extended to address specific business needs and simultaneously encourage consistency of user experience.

To deliver immediate value, reuse focuses on establishing a business, technical and information architecture that forms a foundation layer of business, data, and technical assets. You make use of these assets to accelerate your release velocity and enterprise transformation.

When does a Reuse take place?

Reuse is a mindset and practice that is prevalent throughout the life cycle of an evolving enterprise landscape.

For any Pega application, from the very early stages during business problem identification and qualification, the lens of reuse is applied for business and IT to collaboratively identify reuse module candidates. Reuse modules are then built using a combination of our low code authoring experiences: App Studio, Dev Studio, or NBA Designer. The business can then assemble workflows quickly by using reusable modules in App Studio or NBA Designer.

When an application with reusable assets is released to production, the ecosystem is enriched by adding those reusable assets to the reuse library for future business or technical needs throughout the organization. This cycle of identify, build, assemble and reuse is most effective when governed by a Centre of Excellence, which orchestrates the lifecycle of reusable assets.

As a mindset, the Reuse best practice is equally applicable to the business domain as well as that of the data and technical domains within an enterprise. When adopted in collaboration between business and IT, this delivery approach creates a culture of reuse throughout the organization.

  • Previous topic Pega Express best practice User Experience
  • Next topic Pega Express best practice Microjourney Accelerators

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us