Difference between revisions of "Configuring and extending stages, statuses, and work queues"

From PegaWiki
Jump to navigation Jump to search
(added URL for adding\updating statuses and work queues)
Tag: Visual edit
(Added initial context for versioning)
Tag: Visual edit
Line 16: Line 16:
  
 
The Pega Composer for Healthcare application provides a robust capability to manage various entities such as benefits, networks, product templates, products, and plans. Out-of-the-box, PCS provides 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 setup, PCS also provides several work baskets where these entities are held for processing.
 
The Pega Composer for Healthcare application provides a robust capability to manage various entities such as benefits, networks, product templates, products, and plans. Out-of-the-box, PCS provides 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 setup, PCS also provides several work baskets where these entities are held for processing.
[[File:Lifecycle stages.jpg|none|thumb|800x800px|Lifecycle stages, statuses and workbaskets]]
+
 
 +
Pega-provided case management features are extensively used to achieve this feature. Each PCS entity (E.g. Benefit, Product Template etc.) undergoes this life cycle process. A typical health care benefit configuration, for example, undergoes various stages in its life cycle before it is available for consumption in the actual salable/marketable health plans. This progression of a benefit (or any PCS entity) through various stages typically starts with a concept/idea and traverses through various internal and external reviews and approvals for it to be available in production (salable) before being finally retired when it is no longer used. Similarly a product template, product or plan etc. undergo this life cycle.
 +
 
 +
Rather than being a linear, serialized process, a plan/product configuration is made up of many processes, tasks, policies, and supporting content. Depending on the context of the plan/product, elements and the way that work is accomplished change. Furthermore, a plan as a whole continues to change throughout its life cycle due both internal and external events. Adding to the challenge, there are often several configurators, product managers and other internal and external parties collaborating on any given plan/benefit configuration.
 +
 
 +
Therefore, this customizable stage based life cycle management provides better control over the business process and improves the consistency, effectiveness and visibility of process handling which, thereby, decreases cost and improves quality.
 +
 
 +
Life cycle stage configurations like changing the stage names, skipping the stages, jumping across the stages and skipping approvals etc. are highly business friendly. These can be achieved by the business by just tweaking some business friendly rules like ‘When rules’, ‘Decision rules’, and ‘Flow rules’ etc. These are easily configurable and highly extendable. [[File:Lifecycle stages.jpg|none|thumb|800x800px|Lifecycle stages, statuses and workbaskets]]
  
 
== Stages in PCS ==
 
== Stages in PCS ==

Revision as of 21:45, 27 January 2021


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 ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

The Pega Composer for Healthcare application provides a robust capability to manage various entities such as benefits, networks, product templates, products, and plans. Out-of-the-box, PCS provides 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 setup, PCS also provides several work baskets where these entities are held for processing.

Pega-provided case management features are extensively used to achieve this feature. Each PCS entity (E.g. Benefit, Product Template etc.) undergoes this life cycle process. A typical health care benefit configuration, for example, undergoes various stages in its life cycle before it is available for consumption in the actual salable/marketable health plans. This progression of a benefit (or any PCS entity) through various stages typically starts with a concept/idea and traverses through various internal and external reviews and approvals for it to be available in production (salable) before being finally retired when it is no longer used. Similarly a product template, product or plan etc. undergo this life cycle.

Rather than being a linear, serialized process, a plan/product configuration is made up of many processes, tasks, policies, and supporting content. Depending on the context of the plan/product, elements and the way that work is accomplished change. Furthermore, a plan as a whole continues to change throughout its life cycle due both internal and external events. Adding to the challenge, there are often several configurators, product managers and other internal and external parties collaborating on any given plan/benefit configuration.

Therefore, this customizable stage based life cycle management provides better control over the business process and improves the consistency, effectiveness and visibility of process handling which, thereby, decreases cost and improves quality.

Life cycle stage configurations like changing the stage names, skipping the stages, jumping across the stages and skipping approvals etc. are highly business friendly. These can be achieved by the business by just tweaking some business friendly rules like ‘When rules’, ‘Decision rules’, and ‘Flow rules’ etc. These are easily configurable and highly extendable.

Lifecycle stages, statuses and workbaskets

Stages in PCS[edit]

You can customize each of these stages and add more stages by using the extensions provided.

For example, you can move the benefits from Development to Production after approval and eliminate the Implementation stage, thereby reducing the overall time for configuring each entity. More details on the various stages in PCS can be found in Life cycle management.

Users can also skip a specific stage for all entities from the lifecycle using the configuration rules - "SkipDevelopment" or "SkipImplementation". You can access these configuration rules by clicking Configure > Product Composer System > Business Rules in Dev Studio.

Statuses in PCS[edit]

Out-of-the-box, PCS provides detailed statuses for each of the entities. The statuses are based on the stage of an entity. 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, you can control which entities to flatten based on the status and stage of the entity.

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

Workbaskets in PCS[edit]

Several workbaskets are available out-of-the-box in PCS. Having a foundational knowledge about them is very important for the implementation teams. As shown in the above image, the respective entities move to different work baskets based on the stage and status they are in. In the following table, each column describes the workbaskets in the stage.

Workbaskets in PCS based on stage
Development Implementation Production Retirement
Dev_Initiation Impl_Initiation Prod_Initiation
Dev_PendingApproval Impl_PendingApproval Prod_PendingApproval Retire_PendingApproval
Dev_Approved Impl_Approved Prod_Approved

Some other workbaskets available out of the box in PCS are listed below. All these workbaskets can be accessed from the manager portal.

Sr No Workbasket Description
1 Pending Auto Flatten Workbasket to hold all the flattening jobs
2 Document Approved Workbasket where all the approved SBC documents are stored
3 Custom work plan queue Workbasket where incoming requests for custom plans are held (input via API)
4 Entity save failed Workbasket to store the entities that could not complete the save process
5 PCS product admin Workbasket with complete list of products
6 Pending import Workbasket to store the list of entities which are pending the import process
7 Plan update failed Workbasket where the plans that could not complete the update process are stored
8 Update pending approval Workbasket where the entities pending approval are stored

You can add more processing for entities after the entities are moved into one of these workbaskets. For example if the business team wants to run any of the quoting process, they can run it on any one of these workbaskets.

Extension for implementation teams[edit]

Having a clear understanding of the out-of-the-box stages, statuses, and workbaskets is a must for any member of the implementation team. Knowing how to make changes 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 provides the following decision rules to facilitate the customization. You can access these rules by clicking Configure > Product Composer System > Business Rules in Dev Studio.

Customize stage, status, wb.jpg

For example, the business might have an additional workbasket that they want to add to PCS such as 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.

More details about updating workbaskets (also known as work queues) can be found at https://community.pega.com/sites/default/files/help_v85/index.htm#data-/data-admin-/data-admin-workbasket/creating-work-queue-tsk.htm#Creating_a_work_queue

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

For example, if the client team prefers the name "Ideation" instead of "Development" - the team can change that using the "Customize stage names" decision table as shown below.

Change stage names.jpg

More details about changing status can be found at https://community.pega.com/sites/default/files/help_v85/index.htm#case-management/case-processing/cm-standard-rules-related-to-case-status-ref.htm