Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring optional prconfig.xml settings in on-premises systems

Updated on April 6, 2022

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.

This content only applies to on-premises systems and is not supported in Pega Cloud environments.

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 calculations 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. For details on command-line parameters, see BIX parameters and command-line arguments.
  • Previous topic Configuring the target database for BIX command-line extractions in on-premises systems
  • Next topic Configuring BIX logs for command-line extractions in on-premises systems

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us