Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Monitoring data flows

Suggest edit
Updated on April 5, 2022

Use the Call instruction with several activities to track the status of data flows that were run in batch mode with the Call Data-Decision-DDF-RunOptions.pxRunDDFWithProgressPage method or submitted on the Data Flows landing page. You can track the number of processed records, and the elapsed or the remaining time of the data flow run.

  1. Create an instance of the Activity rule in the Dev Studio navigation panel by clicking RecordsTechnicalActivity.
  2. In the activity steps, provide the pyWorkObjectID property in order to identify which data flow run you want to monitor.
  3. In the activity steps, enter one of the following methods to monitor a data flow:
    • Call Data-Decision-DDF-RunOptions.pxInitializeProgressPage - Creates the progress page that consists of a top level page named Progress of the Data-Decision-DDF-Progress data type.
    • Call Data-Decision-DDF-Progress.pxLoadProgress - Updates the current status.
  4. Click Save.
Result:

Apart from the API methods for data flows, you can use a default section and harness to display and control execution progress of data flow runs:

  • The Data-Decision-DDF-Progress.pyProgress section displays recent information. This section, which is also used on the Data Flows landing page, refreshes periodically to update the progress information.
  • The Data-Decision-DDF-RunOptions.pxDDFProgress harness, which is also used in the run dialog box of the Data Flow rule, displays the complete harness for the data flow run. It provides the progress section and the action buttons that you use to start, stop, and restart the data flow run.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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