Configuring and extending stages, statuses, and work queues
|Request to Publish||Yes|
|Description||Configuring and extending stages, statuses and workbaskets in PCS|
|Version as of|
|Application||Pega Product Composer for 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 workbaskets where these entities are held for processing.
Pega-provided case management features are extensively used to achieve this feature.?? which feature? 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. Depending on the context of the plan or product, elements and the way that work is accomplished change. ?? what does this mean???? Furthermore, a plan as a whole, continues to change throughout its life cycle to due both internal and external events. what does to due mean?? 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. Is the flow link the correct reference for the users? Is this OK to reference these links? 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. ??? Is this the correct link for them to create new statuses???
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.??? I did not see these. Where are they? Also i tried searching for some of these to find the exact way they are written (underscores etc) and they didn't show up. Where should i be looking?
|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
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. I can't change the size of the image. This is too big...goes beyone the right text border. Can you change it? Maybe only show the table part?
For more details about changing status, see Standard rules and extension points.