Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Out-of-the-box microjourneys™ and implementing them with Pega Express™

Updated on December 20, 2020

Business outcomes can be achieved even faster with Pega Express through taking advantage of the out-of-the-box (ootb) microjourneys that are available with Pega. Out-of-the-box microjourneys are high frequency pre-configured microjourneys that can be used on their own or as part of a bespoke configured application.

Information on available microjourneys can be found on community, along with detailed implementation instructions:

Pega Customer Service for Communications Microjourneys

Customer Service for Healthcare Microjourneys

Customer Service for Financial Services Microjourneys

Customer Service for Insurance Microjourneys

Pega Express is a perfect delivery approach for these microjourneys; this topic covers some tips for implementing them quickly using Pega Express.

OOTB microjourneys and the Discover phase:

It’s during Discover, that the microjourneys are identified and prioritized based on their business outcomes and technical feasibility. This is the point when ootb microjourneys should be assessed for suitability and functional coverage.

The review should be a simple gap analysis, where the ootb microjourney UI, extension points and overall functionality is compared against the proposed solution to confirm that the microjourney is a good fit.

Once confirmed, the microjourney should be defined in a case type backlog or directly in App Studio (8.5+). The contents should be tailored and adjusted to reflect the specific client scenario (gap analysis), ensuring tweaks or additions to the microjourney are added.

OOTB microjourneys and the Prepare phase:

With an ootb microjourney forming the core of the application to be delivered, you can accelerate through Prepare and Build. In Prepare, the proposed app design and data model needs to be reviewed to ensure it meets the required design for the client’s organization.

Then similarly to a platform build, the microjourney can be broken down into epics and user stories (supported by Directly Capture Objectives), with the emphasis on user stories being tweaks to the microjourney or additions, to facilitate a rapid application configuration.  Implementing interfaces or any other dependencies first is recommended. Selected microjourneys have implementation guidelines available on community, for example here is the ‘Change Policy Address’ microjourney.

OOTB microjourneys and the Build phase:

Helping with the accelerated delivery, the key benefit of an out-of-the-box microjourney is that testing overhead is reduced, as pre-built functionality has already been tested. Therefore, this should be reflected in test approach to ensure it is as streamlined as possible.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us