Support Article

Child cases are missing from BIX extraction



After upgrading from PRPC 5.5 to Pega 7.2, child work objects are missing from the Business Intelligence Exchange (BIX) extraction.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

A defect or configuration issue in the operating environment.

Issue is that in earlierr version of BIX was taking advantage of the bug that would use a "like" in the where clause instead of an "=" even when the class was not a classgroup.

Extracts are specified at the class level, not at the application level. For example, if there is three case types in the application and user would like to extract data for each,then one must define an extract rule for each of the three case types.

Note: If extracting from a class group, the extract will include all classes in the class group. If the class is not a class group, the extract will only include instances of that class.

Similar to other areas of the product (like List Views, Report Definitions etc.), when a rule is defined at the classgroup level, BIX will include its subclasses by using a LIKE query.

But for classes which themselves are not a classgroup but belong to one, then BIX does not generate a LIKE query.

There was a bug in Extract rule executions which have been fixed to keep the behavior consistent with other rules.


In BIX 7.2.2 there is a new feature which will allow the standard filters to be removed from the extraction query.

There is a secondary option to also remove the order by clause from the query. The feature has been backported to Pega 7.2.

With this feature one can mimic the same behavior you were seeing in previous release of BIX.

This feature involves both code and rule changes. These are the installation instructions.

1. Using Hot Fix Manager install DL item containing HFix-32153 and its dependent hot fixes

2. Import HFix-32183.jar using Import Utility

3. Restart all nodes

After this open the Extract rule on the "Filter Criteria" tab you will see a checkbox to "Skip Standard Filters".

With this checked the standard "pzInsKey like" for a classgroup or the "pxObjClass =" for a class will not be included in the generated extraction query.

There is a second checkbox "Skip standard order by clause".

​With this checked the standard order by pzInskey clause to the generated extraction query.

Published February 9, 2017 - Updated February 19, 2017

Have a question? Get answers now.

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