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 ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓
Configuring and extending Stages, Statuses and workbaskets in PCS
??? Is this a repetition of the title? I changed the title, but this is still here. I think that this should be deleted or changed to Introduction???
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.
Can you add a comma after statuses? Every time I make the change, it gets crazy and I don't seem to get back to the document
Stages in PCS
You can customize each of these stages and add more stages by using the configuration touch points provided. ??? what are the touchpoints? We never discuss them. Extensions?
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. ??? I wonder if this referenced section in the implementation guide needs to be expanded --not really a lot there on how to change the stages. I'm not sure how/where this happens. Is this in versioning? More info here?
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. ?? Should we tell them how or reference platform or something? I don't know how to add a status
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. ??? how do they find out about this functional knowledge? Can we reference something? In the following table, each column describes the workbaskets in the stage.
|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|
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. Do we need more details here? I'm not sure how it would work. How would they do it?
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. ??? hmm....we never tell the user about this location in the Implementation guide. Should we? The wording also should be edited. For example, there is no more PRPC. And we shouldn't use via. I can try and edit this page. who would I send the edits to?
For example, the business migth 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.