More about Extract rules
Testing
- Click Run.
- Enter a unique identifier and the maximum number of records to extract.
- Click Perform Extract.
- Review the resulting data and log files.
Scheduling Extract rule runs
For more efficient operation, you should schedule run of an Extract rule using a Pega Platform agent or from a Windows or UNIX/Linux command-line. See Running the command-line extract process and Running an Extract rule using a Pega Platform agent .
For more efficient operation, you should schedule run of an Extract rule using a Pega Platform agent or from a Windows or UNIX/Linux command-line. See Running the command-line extract process and Running an Extract rule using a Pega Platform agent .
For more efficient operation, you should schedule run of an Extract rule using a Pega Platform agent.
Exception handling
Executing BIX may result in errors or exceptions being reported. These exceptions may relate to syntax errors (in command-line execution), database constraint violations (when exporting to a database), or similar issues. See BIX logging and error handling. See BIX logging and error handling.
Rule operation
Extract rules can operate on the BLOB column ( Storage Stream Storage Stream Storage Stream ) of tables in the PegaRULES database or they can be used to extract data from tables with no BLOB column. However, when a class table includes a BLOB (pzPVStream column), extraction always is performed from that BLOB value, and not from other database columns.
If the extract rule class is a class group, the query on the source database gets all WorkObject instances of all classes within the class group. If the extract rule class is not a class group, the query on the source database only gets instances of the particular class.
Forward and backward chaining during BIX extract
In the prconfig file, a setting governs whether forward and backward chaining are enabled during a BIX extract. You should disable forward and backward chaining for better throughput when running BIX.