Configuring and extending stages, statuses, and work queues
|Request to Publish|
|Description||Configuring and extending stages, statuses and workbaskets in PCS|
|Version as of||8.5|
|Application||Product Composer for Healthcare|
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 life cycle 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 workbaskets where these entities are held for processing.
Pega-provided case management features are extensively used to achieve life cycle management. Each PCS entity, for example benefit and product template, undergoes this life cycle process. For example, a typical healthcare benefit configuration undergoes various stages in its life cycle before it is available for consumption in the actual marketable and salable health plans. This progression of a benefit or any PCS entity through various stages typically starts with a concept or idea. It traverses through various internal and external reviews and approvals before it is available in production (salable). It is finally retired when it is no longer used. Similarly a product template, product, or plan undergoes this life cycle.
Rather than being a linear, serialized process, a plan or product configuration is made up of many processes, tasks, policies, and supporting content. Furthermore, a plan as a whole, continues to change throughout its life cycle due to both internal and external events. Because of inheritance between product template, product and plans, the values can change for any of these entities, which qualifies as internal change. Also due to regulatory changes, the plan repository might need to be updated, which is an example of external change. Adding to the challenge, there are often several configurators, product managers, and other internal and external parties who collaborate on any given plan or 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, thereby decreasing cost and improving quality.
Life-cycle, stage configurations such as changing the stage names, skipping the stages, jumping across the stages, and skipping approvals are business-friendly. Business users can tweak when rules, decision rules, and flow rules. These are easily configurable and extendable.
Stages in PCS
You can customize each of these stages and add more stages by using the extensions provided.
For example, you can move benefits from Development to Production after approval and eliminate the Implementation stage, thereby reducing the overall time for configuring each entity. For more details on the various stages in PCS, see Life cycle management.
You can also skip a specific stage from the life cycle for all entities by using the SkipDevelopment or SkipImplementation configuration rules. You can access these configuration rules by clicking Configure > Product Composer System > Business Rules in Dev Studio.
Statuses in PCS
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
Several out-of-the-box workbaskets are available in PCS. Having a foundational knowledge about them is very important for the implementation teams. As shown in the Life cycle stages image above, the respective entities move to different workbaskets based on their stage and status. In the following table, each column describes the workbaskets in the stage.
Some other out-of-the-box workbaskets are listed below. All these workbaskets can be accessed from the Manager portal.
|1||Pending Auto Flatten Entities||Workbasket containing all the flattening jobs|
|2||Document Approved||Workbasket storing the approved SBC documents|
|3||Custom plan work queue||Workbasket holding incoming requests for custom plans (input through API)|
|4||Entity Save Failed||Workbasket storing the entities that could not complete the save process|
|5||PCS Product Admin||Workbasket storing the list of all products|
|6||Pending Import||Workbasket stroring the list of entities which are pending the import process|
|7||Plan Update Failed||Workbasket storing the plans that could not complete the update process|
|8||Update Pending Approval||Workbasket storing the entities pending approval|
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
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.
For example, the business might want to add a workbasket, such as Pending-Quote, to PCS 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. For more details about updating workbaskets (also known as work queues), see Creating a work queue .
Similarly, you can rename or remove any of the stages 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 the name by using the Customize stage names decision table as shown below.
For more details about changing status, see Standard rules and extension points.