You can add parameters to the prconfig.xml file that filter the data by any property, including date ranges, enable or disable chaining, and specify whether records added to the database while the extract is running are included in the extract.

Add the following settings to the end of the prconfig.xml file:

• Optimize XML output – Set to true by default to facilitate extracting a large number of class instances to XML: <env name= “compatibility/BIXUseOptimizedClipboardXML” value= “true” />

• Disable forward chaining – Enable or disable forward chaining calculations of properties when loading the clipboard for BIX extract: <env name= “compatibility/BIXdisableForwardChaining” value= “true”>

  The default setting is TRUE.

• Disable backward chaining – Enable or disable backward chaining of properties when loading the clipboard for BIX extracts: <env name=”compatibility/BIXdisableBackwardChaining” value = “true” />

  The default setting is TRUE.

• Disable declarative processing – Enable or disable declarative processing: <env name=”declarative/enabled” value = “false” />

  Note: Only use this setting when you are running BIX from the command line. If you use this setting on a node to improve performance, you cannot open or create rules on that node.

• Include class instances added during a batch run – Enable or disable whether class instances added to the Pega Platform database after a batch run begins execution are included in the extract: <env name=”bix/useHistoryClasses” value=”true” />

  Note: bix/useHistoryClasses only works when using the Use Last Updated Time as Start filter option. If command line parameters such as –u, -U, -d, and -D are passed while running the BIX script, bix/useHistoryClasses will not have any effect even if it is set to true.

• Running a BIX command-line extraction
• Configuring environments for command-line extractions
• Stand-alone command-line BIX extractions

• Understanding BIX command-line extractions