Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Changing Plan end-date creates new Plan instance



When editing a previously draft-approved PlanProduct Composer for Healthcare ( PCS ) allows user to change the 'end-date' (on metadata screen).

When user changes the end date and the plan is again draft-approved, PCS creates an additional Plan 'data' instance.

PCS would ordinarily not let you create a duplicate named Plan with overlapping date ranges. Both Plan data instances (with different end-dates) are associated with same Plan work-object.

Error Messages

Not applicable

Steps to Reproduce

  1. Create a PCS Plan and proceed all the way through draft-approval. Note that user can now find the plan when clicking 'Plans' on left-hand navigation bar and filter it (for example, by name).
  2. Reopen the Plan work object and click 'update' button.
  3. Make a change to the end-date.
  4. Proceed all the way through draft-approval.
  5. Click on 'Plans' on left-hand navigation bar and note that when you filter for your Plan, observe two instances, one with the old end-date and one with the new end-date.

Root Cause

This is working as designed in PCS version 7.12. The system is setup to retain all data instances.


This issue may be avoided in PCS version 7.21 through the use of application versioning features.

Published August 23, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us