Skip to main content


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

Purpose of this guide

Updated on April 15, 2021

A project team that implements a Pega application uses this implementation guide to enable and extend application features to meet client business requirements. Complete the product installation before starting the implementation procedures. For information about installing your application, see the product installation guides on the Pega Foundation for Communications product page.

This implementation guide presents tasks in the sequence in which they are commonly performed; however, the sequence varies based on business priorities. Follow the procedures in this guide to complete the tasks for the first minimum lovable product (MLP) release. Also, use this guide during iterative releases as you configure and extend more features on top of the MLP release.

The application includes a case type backlog that supports the procedures in this implementation guide. The case type backlog is an inventory of the application-provided case types that establishes the project scope by defining the changes and additions that are required for the first MLP release and later releases. For more information, see Capture microjourneys in the case type backlog and Journey Centric Delivery.

  • Previous topic Pega Fulfillment Control Center for Communications implementation guide
  • Next topic Preparing for the implementation

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