Close popover

Table of Contents

Deleting an external data flow run

Version:

Use the Call instruction with the pxDeleteRunById activity to delete an external data flow run that is in the New, Completed, Failed, or Stopped state.

  1. Create an instance of the Activity rule in the Dev Studio navigation panel by clicking Records Technical Activity .

  2. In the activity steps, enter the Call pxDeleteRunById method:

    1. Add the first step:

      • Method: Page-New

      • Step page: runOptions

    2. Add the second step:

      • Method: Call pxDeleteRunById

      • Step page: runOptions

    3. In the second step, click the arrow to the left of the Method and specify the runID parameter.

      You can find the run ID on the Data Flows landing page.

  3. Click Save.

  • Data Flows landing page

    This landing page provides facilities for managing data flows in your application. Data flows allow you to sequence and combine data based on various sources, and write the results to a destination. Data flow runs that are initiated through this landing page run in the access group context. They always use the checked-in instance of the Data Flow rule and the referenced rules.

  • Creating external data flows

    External Data Flow (EDF) is a rule for defining the flow of data on the graphical canvas and executing that flow on an external system. With EDF, you can run predictive analytics models in a Hadoop environment and utilize its infrastructure to process large numbers of records to limit the data transfer between Hadoop and the Pega Platform.

  • External Data Flow Run window

    You can monitor and manage each instance of running an external data flow from the External Data Flow Run window. This window gives you detailed information about each stage that an external data flow advances through to completion.

  • Creating and starting an external data flow run

    Use the Call instruction with the pxStartRun activity to create and start an external data flow run.

  • Calling another activity
  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • Decision Management methods

Have a question? Get answers now.

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