Support Article

BIX not functioning correctly after 7.1.8 upgrade

SA-28761

Summary



After upgrading from Pega 7.1.5 to 7.1.8, ​Business Intelligence Exchange (BIX) does not extract work objects with multiple child cases.

Work objects without child objects are being picked up with no issues, and the child objects themselves are being extracted without issue as well.


Error Messages



Not applicable


Steps to Reproduce



1) Create a case with child cases.
2) Resolve parent case and all child cases.
3) Run a BIX extract.


Root Cause



An issue in the custom application code or rules.  

There was a bug in a previous version where BIX should have been doing a LIKE query only for classgroups and not for individual classes which belong to a classgroup.  

BIX has now fixed the behaviour and the application which was leveraging this bug as a feature is now only getting the instances of the class the extract was written against since the class is not a class group.

Resolution



Here’s the explanation for the reported behavior: 

Similar to other areas of the product (like List Views, Report Definitions and so on), 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.

Example,
Sample is class group
Sample-SimpleClassA belongs to class group Sample
Sample-SimpleClassB belongs to class group Sample
Sample-SimpleClassB-AA belongs to class group Sample
Sample-SimpleClassC belongs to class group Sample

Previously with the BIX bug, extraction written on Sample-SimpleClassB and extracted instances of both Sample-SimpleClassB and Sample-SimpleClassB-AA.

Options to get the same instances extracted:
  1.  Make Sample-SimpleClassB a class group and then get pzInskey like 'Sample-SimpleClassB%'.
  2. Keep the current extract rule for 'Sample-SimpleClassB' and create a second one for 'Sample-SimpleClassB-AA' so user ends up with queries pxObjClass = 'Sample-SimpleClassB' for first one and  pxObjClass = 'Sample-SimpleClassB-AA' for second one.
  3. Move the extract rule to the classgroup level and then add filters so only the two classes are included:
pzInskey like 'Sample%' AND ( pxObjClass = 'Sample-SimpleClassB' OR pxObjClass = 'Sample-SimpleClassB-AA') 

 

Published October 3, 2016 - Updated October 14, 2016

Have a question? Get answers now.

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