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

Benefit variation is not displayed on plan data instance

SA-34431

Summary



A plan was created through the Product Development portal with a benefit that has a copay variation. The plan has been advanced to the prod-approved status. The variation is visible on the plan work object in both the review and perform harnesses but not visible on the data instance that is displayed when searching for plans via the portal search feature.

Error Messages



Not Applicable


Steps to Reproduce

  1. Create 1 benefit work object and advance it to prod-approved.
  2. Create 1 benefit set and add benefit to benefit set and advance it to prod-approved.
  3. Create 1 network and advance it to prod-approved.
  4. Create 1 Product Template and select the network and benefit set created in previous steps and advance it to prod-approved.
  5. Create 1 Product and select the template created in previous step and advance it to prod-approved.
  6. Create 1 Plan and advance to the "configure benefits" screen.
  7. When at the configure benefit screen, click the hyperlink for the benefit to open up modal.
  8. Within modal, select the 'Policies" tab and expand the network row.
  9. Click "on Edit" button and then click the "add variation".
  10. Add values for the variation and click the save button.
  11. Click the submit button on the modal.
  12. Click "Mark All" as Complete button and click "Finish".
  13. Advance the plan to prod-approved.
  14. Click on "Plan" tab on the left panel of the portal.
  15. Enter plan name in the search criteria and click search button.
  16. Click on the plan in the search results to open the plan data instance.
  17. Click the "configured benefits" tab.
  18. Click on the benefit hyperlink to open the modal.
  19. Select "policies" tab and expand the network.
  20. Variation information is not displayed.


Root Cause



A defect in Pegasystems’ code or rules.

Resolution



Apply HFix-32727.

Published March 7, 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