Configuring and extending stages, statuses, and work queues

Curator Assigned	shahp@pegasystems.com
Request to Publish	Yes
Description	Configuring and extending stages, statuses and workbaskets in PCS
Version as of
Application	Pega Product Composer for Healthcare
Capability/Industry Area	Healthcare

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please Read Below ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Enter your content below. Use the basic wiki template that is provided to organize your content. After making your edits, add a summary comment that briefly describes your work, and then click "SAVE". To edit your content later, select the page from your "Watchlist" summary. If you can not find your article, search the design pattern title.

When your content is ready for publishing, next to the "Request to Publish" field above, type "Yes". A Curator then reviews and publishes the content, which might take up to 48 hours.

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ The above text will be removed prior to being published ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Configuring and extending Stages, Statuses and workbaskets in PCS

PCS application provides a robust capability to manage various entities such as benefits, networks, product templates, products and plans. Out of the box, PCS does provide various lifecycle stages for each of these entities. Within each stage, the application also assigns predetermined statuses to these entities as they progress through each stage. And to complete the infrastructure set up, PCS also provides several work baskets where these entities are held for processing.

Lifecycle stages, statuses and workbaskets

Stages in PCS

More details on the various stages in PCS can be found at https://community.pega.com/knowledgebase/articles/pega-product-composer-healthcare-implementation-guide/85/life-cycle-management

Each of these stages can be customized and additional stages can also be added via the configuration touch points provided.

For example if for a customer, the benefits created move from development to production after approval - the 'implementation' stage can be eliminated, thereby reducing the overall time for configuring each entity.

Statuses in PCS

Out of the box PCS does provide detailed statuses for each of the entities. The statuses are based on the stage that a particular entity is in. For example in the 'development' stage, each entity will have the statuses of 'Dev-Initiation', 'Dev-PendingApproval' and 'Dev-Approved'.

The statuses of the PCS entities also drive many of the validation and processing rules. For example for the flattening process, the users can control which entities to flatten based on the status and\or stage of the entity.

Any additional statuses can also be added by the implementation team.

Workbaskets in PCS

There are several workbaskets available out of the box in PCS, and having a foundational knowledge about them is very important for the implementation teams. The most important work baskets are

Workbaskets in PCS

Development	Implementation	Production	Retirement	Other	Other
Dev_Initiation	Impl_Initiation	Prod_Initiation		Pending Auto Flatten	PCS product admin
Dev_PendingApproval	Impl_PendingApproval	Prod_PendingApproval	Retire_PendingApproval	Document Approved	Pending import
Dev_Approved	Impl_Approved	Prod_Approved		Custom work plan queue	Plan update failed
				Entity save failed	Update pending approval

Additional processing for the entities can be added once the entities are in one of these work baskets. For example if the business team would like to run any of the quoting process, they can select to run that on any one of these work baskets.

Extension for implementation teams

Having a clear understanding of the stages, statuses and workbaskets available out of the box, is a must for any member of the implementation team. Knowing how to change any of these by leveraging the extension rules, allows the implementation team to rapidly customize PCS to meet the needs of the business. Out of the box, PCS does provides the following decision rules to facilitate the customization. One can access these from Configure ---> Product Composer System --> Business Rules

For example, the business may have an additional workbasket that they might to add to PCS like - Pending-Quote before moving the plans to production. By using the above decision rules, the implementation team can quickly re-use one of the workbaskets, or add a new one.

Similarly any of the stages can be renamed or removed from the flow using the customize stage names decision rule.

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.

A business solution that automates workflows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard.

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.

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.

(Deprecated) A configuration of panels (areas) in a harness that support a composite portal. Existing panel sets continue to function. As a best practice, upgrade panel sets to screen layouts.

A work party that typically initiates a case. In many applications, only one customer can be associated with a case.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.

1) In user portals, a "team" is equivalent to a "work group". 2) One or more associates who work semi-autonomously on recurring tasks or towards a common goal. In a Pega Workforce Intelligence hierarchy, departments are comprised of teams. (Defined by the WFI team)

A piece of data that can be extracted from text, including names, locations, amounts, IDs, and so on.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.

This is a deprecated term for what is now known as the work queue.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.