Question


NASCO
US
Last activity: 17 Apr 2025 9:50 EDT
Can we use batch Data Flow rules in place of BIX rules for Data Extraction into DB,csv and XML files
We currently use BIX for offline reporting needs to extract data into XML,CSV and DB output formats.
Can we use batch Data Flow rules as an alternate to BIX?
If yes what are the limitations and advantages of using Data Flows in place of BIX?
Can Data Flow rules be used for writing real time work object data in BLOB to normalized tables by selecting the properties needed?
***Edited by Moderator Rupashree to add Capability tags***
-
Reply
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!


Ford Motor Company
US
Yes, you can use batch Data Flow rules as an alternative to BIX (Business Intelligence Exchange) to extract and transform data from Pega Platform. Batch Data Flow rules allow you to define the data sources, filters, mappings, and transformations for extracting data and writing it to an external system in batch mode. This can be an effective alternative to BIX for certain use cases, and it provides more flexibility and control over the extraction and transformation process. Keep in mind that the choice between BIX and batch Data Flow rules depends on your specific requirements and use case.
Here are the advantages and disadvantages of both BIX and batch Data Flow rules:
Advantages of BIX: 1. Pre-built integration: BIX provides a pre-built integration for extracting data from Pega Platform, making it easier to set up and use. 2. Simplified configuration: BIX offers a simplified configuration process for defining the data to be extracted and the format in which it should be delivered. 3. Support for historical data: BIX can be used to extract historical data from Pega Platform, making it suitable for data warehousing and reporting needs.
Yes, you can use batch Data Flow rules as an alternative to BIX (Business Intelligence Exchange) to extract and transform data from Pega Platform. Batch Data Flow rules allow you to define the data sources, filters, mappings, and transformations for extracting data and writing it to an external system in batch mode. This can be an effective alternative to BIX for certain use cases, and it provides more flexibility and control over the extraction and transformation process. Keep in mind that the choice between BIX and batch Data Flow rules depends on your specific requirements and use case.
Here are the advantages and disadvantages of both BIX and batch Data Flow rules:
Advantages of BIX: 1. Pre-built integration: BIX provides a pre-built integration for extracting data from Pega Platform, making it easier to set up and use. 2. Simplified configuration: BIX offers a simplified configuration process for defining the data to be extracted and the format in which it should be delivered. 3. Support for historical data: BIX can be used to extract historical data from Pega Platform, making it suitable for data warehousing and reporting needs.
Disadvantages of BIX: 1. Limited flexibility: BIX may have limited flexibility in terms of customizing the extraction and transformation process to meet specific business requirements. 2. Performance impact: BIX may have a performance impact on the Pega Platform, especially when extracting large volumes of data.
Advantages of batch Data Flow rules: 1. Flexibility and control: Batch Data Flow rules provide more flexibility and control over the data extraction and transformation process, allowing for custom logic and complex transformations. 2. Scalability: Batch Data Flow rules can be scaled to handle large volumes of data and can be scheduled to run at specific times, allowing for better resource management. 3. Integration with external systems: Batch Data Flow rules can be used to integrate with a wide range of external systems and data sources, providing more versatility.
Disadvantages of batch Data Flow rules: 1. Complexity: Setting up and configuring batch Data Flow rules may require more technical expertise and knowledge of Pega Platform data processing concepts. 2. Development effort: Building and maintaining batch Data Flow rules may require more development effort and time compared to using BIX.
Ultimately, the choice between BIX and batch Data Flow rules depends on the specific requirements and use case of your organization, as well as the technical expertise available for implementation and maintenance.
Also, please refer to the data flow run limit page: https://docs.pega.com/bundle/platform/page/platform/decision-management/data-flow-run-limits.html


Pegasystems Inc.
GB
@AravindY2749Even though it is possible to use Data Flow rules to extract data from Pega (as described by Suman), please be aware that doing this is currently subject to you also having a Process AI Event Stream Triage license.
Also, look out for our new Case Data Capture (CDC) capability coming in 24.2. This is basically BIX getting a well deserved update that will make it super easy for you to stream data in real-time to third party apps or a data warehouse (incl. Kafka, Tableau, Snowflake, etc.). More details will be announced once 24.2 goes GA later this year. Watch this space!


Ford Motor Company
US
@Philip Knoetze Great to hear BIX getting updates and have additional capabilities to push data to dat wharehouse. Very much looking forward to CDC.


Blue Zone Consulting Partnes
CR
Tks @Philip Knoetze I hope this capability (CDC) comes as part of the platform and not an additional license :)


Blue Zone Consulting Partnes
CR
Hi @Philip Knoetze , Do you have a link where I can get more information about this (CDC) feature? tks


Pegasystems Inc.
GB
@LuisGuillermoM16704517 Since 24.2 has gone live this capability is now called "BIX Real-time" (rather than CDC). You can check out the release notes for 24.2 where it is mentioned at the bottom of this page - What's new in Insights '24.2 You can also read more about how to configure it here - Configuring BIX real-time data extraction Please also note that BIX Real-time requires a separate license.
Hope this helps!