Question
NASCO
US
Last activity: 26 Nov 2020 17:19 EST
BIX extract on Rule-Declare-DecisionTables class
We have a requirement to generate a BIX extract on Rule-Declare-Decision tables. These decision tables are delegated to users and there will be frequent changes to the values in decision table. Does PEGA recommends the use of BIX extract rules to run on rules schema to extract values of decision table data like conditions and results data set? Will there be any disadvantages or issues for us to extract data for decision tables?
Pegasystems Inc.
AU
It is not something I've seen done before, but I expect it would work as you intend.
An instance of a Decision Table rule is stored as a record in a BLOB table no different to a case. I doubt BIX would care whether that table was in the RULES schema or the DATA schema.
Consider using a filter on your Extract rule to only extract the Decision Tables that reside in the Production ruleset, if your intent is to extract the changes made by business users.
Remember that BIX will only extract the current state of the rule when it runs. If the users have made multiple changes between running the BIX jobs, BIX will only extract the latest snapshot.
From a performance point of view, run explain plan / query analysis on the SQL that BIX generates for extracting the Decision Table instances and ensure these are hitting database indexes. Decision Table rule instances live in the main rule table (I think) which have hundreds of thousands of records, so consider:
It is not something I've seen done before, but I expect it would work as you intend.
An instance of a Decision Table rule is stored as a record in a BLOB table no different to a case. I doubt BIX would care whether that table was in the RULES schema or the DATA schema.
Consider using a filter on your Extract rule to only extract the Decision Tables that reside in the Production ruleset, if your intent is to extract the changes made by business users.
Remember that BIX will only extract the current state of the rule when it runs. If the users have made multiple changes between running the BIX jobs, BIX will only extract the latest snapshot.
From a performance point of view, run explain plan / query analysis on the SQL that BIX generates for extracting the Decision Table instances and ensure these are hitting database indexes. Decision Table rule instances live in the main rule table (I think) which have hundreds of thousands of records, so consider:
- Adding more filtering conditions (Applies To class, Rule Name) to your Extract rule that align with existing out-of-the-box database indexes, resulting in a more performant extraction that doesn't cause BIX to time out due to it having to scan the whole rule table to find the few Decision Table instances to extract.
- If it is only one Decision Table you care about, and (as per best practice) the Production ruleset does not have checkin enabled, then the pzInsKey of that Decision Table doesn't change even as the business makes edits. Your Extract rule could filter by pzInsKey which is the most performant lookup you can do.