The BIX extractor does not show a property that is optimized and mapped in the Database to be used as a filter.

General
, , , , , ,
1

We are creating an extractor in BIX that considers the generation of an XML based on the information of a certain class

BIX1.png
BIX1.png1309×697 51.1 KB

We can get a specific property that is inherited from the class we are mapping, so we can use it in extraction, for example.

bix2.png
bix2.png1911×835 172 KB

BIX3.png
BIX3.png1918×826 111 KB

The property is optimized and mapped within the database as shown below:

bix4.png
bix4.png1918×828 85.6 KB

When we try to use this field as an extractor filter, it is unable to map the information.

​

bix5.png
bix5.png1920×837 89.3 KB

Is there any action we can take?
We have verified that other properties of the same class, which are displayed in the same table, work correctly.

Can you give us any idea of ​​how to resolve this issue?

2

@GuiValino1984

Can you please provide more context on your below comment? Is there an error message? or unable to save with status filter?

When we try to use this field as an extractor filter, it is unable to map the information.

3

@RameshSangili

As I mentioned in the text, I can map a field so that it can be used in the extraction - in this case the status field. We use this field in several reports in our application, and it is already exposed and optimized for use in reports.

When we try to use it as a filter field, BIX cannot map it. If I use another field that has the same conditions, it is already possible to map it, such as the Line of Business field, shown in the image.

These fields originally belong to the Insurance Framework that we use in our application. In this case, the Status field, by business rule, was specialized for the application’s ruleset instead of using the original ruleset. Could this be a reason why it is not being recognized as a field to be used as a filter, for the class level and its inheritances?

4

@GuiValino1984

I opened a ticket with Pega and it was reported that this is a bug in version 8.6.6

“Hi Guilherme, My apologies this is a known Bug in Pega 8.6.6. The workaround is to recreate the extract to resolve the issue, due to this being the workaround there is not currently a HFIX for this. Is there anything else that I can assist with?
Regards,
Erik Tabaka”

We recreated the extract and had no further problems.