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.
Steps to Reproduce
- Create a parent case and child case.
- Run an activity to copy the work parties from the child case to the parent case.
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.