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 work baskets where these entities are held for processing.
Stages in PCS
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.
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 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.
Some other workbaskets available out of the box in PCS are listed below. All these workbaskets can be accessed from the manager portal.
|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 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.
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.