Welcome to PegaWiki

To get started search for a Design Pattern or review content by selecting Design Patterns or Glossary terms.

What is a Design Pattern?
A Design pattern document:

• should share a specific opinion on what a user should do, look for or understand when they are trying to implement something in Pega.
  
• should share the best practices
  
• should provide at least one real-life example
  
• should provide real numbers/metrics (for example: we suggest x number of case stages or if this indicator is higher than x, you should do this)
  
• should be straightforward and easy to read (aka not too long!)
  
• should link/reference other documents (especially those in Community) that have implementation details that are relevant to the usage pattern.
  
• should not go into specific step by step implementation details or definitions (this content should be in other areas and linked to)
  

The first level of organization of the tasks that are required to complete your business process. By providing stages, you organize work into logical phases that users of your application follow to reach an outcome. Stages visualize milestones or significant events in your business process and can also indicate a transition of work from one person to another. For example, if your business process is to review job applications, you can create Submission, Review, and Approval stages, each of which includes a different set of actions and is performed by a different person. Stages that are necessary to resolve a case through the basic, default path are called primary stages.

In a Microjourney™, stages are the milestones that leads towards an outcome.