Skip to main content

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

Data Flow limitations

Updated on July 5, 2022

The following limitations apply to the configuration of Data Flows in Pega Platform. Ensure that you understand how these limitations affect your Data Flows to configure them correctly and avoid errors.

Unsupported features

  • Declarative Rules
  • Data Transform calling activity
  • Multiple destinations for single Case runs
  • The following Page List properties configured with data access settings: Refer to a Data Page and copy data from a Data Page

Partially supported features

Data Transform
To check whether Data Transform works as expected, use the Preview feature on the Data Flow canvas and a Data Flow test run to verify that Data Transform also works in a multinode environment.
Report definition
The system supports only simple report definitions. If you want to use more advanced reports, you need to test whether they work as expected. Use the Preview feature on the Data Flow canvas and a Data Flow test run to verify that report definitions also work in a multinode environment.
Data Page referenced in a Data Flow
Data Page refreshes do not always work as expected in Data Flows. Although Data Pages refresh according to a change of interaction, there is no clear definition or scope in a Data Flow. Data Flows do not have a mechanism to establish whether:
  • The interaction concerns a specific shape in the Data Flow canvas.
  • The interaction follows a single record from start to finish.

The Data Flow engine avoids adding explicit refreshes after every shape to force a refresh of an interaction because it is a performance intensive operation. An interaction refreshes:

  • For a batch Data Flow when a new partition starts processing.
  • For a real-time Data Flow when a scale up or scale down event occurs.

To work around this limitation, you can:

  • Remove the Data Page after using it to enforce a new interaction on every use.
  • Add a parameter to the Data Page to force-load a new interaction in a specific situation. For example, for a Data Page that must refresh every one hour add another optional parameter to the currentTimeStamp Data Page, which has the current hour's timestamp (dropping the minutes and seconds). With this configuration, the Data Page gets a new parameter value every one hour and loads a fresh page.
    Caution: This workaround can lead to the creation of many pages. Ensure that you clear old Data Pages by using Page-Remove or Limit to a single Data Page option on the Data Page.
Note: Data Flows are a distributed process and can process in different server nodes. Data that you store in a Data Page can be unavailable on a local web node.
  • Previous topic Configuring the DataFlow-Execute method for data flows with non-stream input
  • Next topic Reacting to real-time events

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us