Question
Incessant Technologies PVT Ltd
IN
Last activity: 5 Sep 2019 3:04 EDT
Extract rule not supporting polymorphic behavior
In BIX Extarct rule, unable to add "pyPosition" property of "Data-Party-Operator" class in "pyWorkParty" Page group.
The polymorphic behavior to add pages of classes that are inherited from Data-Party(ex:Data-Party-Operator) to pyWorkParty Page group was not supporting in BIX. Extract rule only accepting the properties that are belongs to Data-Party class.
Is there possibility to extract properties in "pyWorkParty" Page group that were part of child classes of "Data-Party" in the BIX extract rules.
***Edited by Moderator Marissa to update platform capability tags; add SR Details***
Pegasystems Inc.
US
BIX extract rules can only select properties that are in the class hierarchy at design time. You can extract all properties and then it will get all of the properties at runtime that are set. But getting all properties of a work object is probably way more than you actually want to extract. If you are just looking to get a couple of these property values you could add a property reference property which is available at design time for the extract rule to include. During run time when the actual pyPostition under pyWorkParty is set then the reference property can be set to the same value.
incessant
GB
Could not able to link a reference property having higher class (Data-Party-Operator) to reference value".pyWorkParty(ClaimHandler)" defined with lower class(Data-Party) .
Created a reference property of class Data-Party-Operator and created OTA to link this property with ".pyWorkParty(ClaimHandler)". Added ".pyWorkParty(ClaimHandler)" as Data-Party-Operator class in pages and classes of activity. but at run time it validated against the definition of pyWorkParty property.while executing Property-Ref method failed with the error as follows
The reference WorkPage.RefClaimHandler is not valid. Reason: class 'Data-Party-Operator' not compatible with source property class 'Data-Party'