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

Work parties are not always properly indexed



Work parties are not always properly indexed. For example, if a case is opened it might show four work parties listed; however, the indexed table only shows three entries. 

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create a parent case and child case.
  2. Run an activity to copy the work parties from the child case to the parent case.

Root Cause

An issue in the custom application code or rules. An activity is used to copy the work parties from the child object to a temporary page, and then call the addWorkObjectParty activity to add these work parties to the parent object. The pzIndexes field is included in the copy and causes an issue when the index is already on the parent object.


The issue is resolved by modifying the custom activity to remove the pzIndexes property after the Page-Copy step.
Suggest Edit

Published September 23, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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