Configuring the DataSet-Execute method for Decision Data Store

You can automate data management operations on records that are defined by the Decision Data Store data set by using the DataSet-Execute method. You can perform these operations programmatically, instead of doing them manually.

  1. Create an activity rule from the Explorer panel, by clicking Records > Technical > Activity > +Create, to start the DataSet-Execute method.

    For more information, see Activities - Completing the New or Save As form.

  2. Click the activity Steps tab.

  3. In the Method field, enter DataSet-Execute.

  4. In the Step page field, specify the step page on which the method operates, or leave this field blank to use the primary page of this activity.

  5. Optional: Enter a description for the method.

  6. Click the Arrow icon to the left of the Method field to expand the Method Parameters section.

  7. Specify the following parameters:

    1. In the Data Set field, enter the name of the data set that is used to represent data in decision data stores.

    2. In the Operation list, select the type of operation. Depending on the type of operation, specify additional settings.

      • Save — Save records passed by a page or data transform in the decision data store.

        • Select the Save list of pages defined in a named page check box to save the list of pages from an existing Code-Pega-List page.

        • Select the Specify time to live (in seconds) check box to specify the life span of the records in the decision data store. This parameter accepts constant values (for example, 3600), property references of values calculated through expressions.

        • Select the Save single track check box to save a single track represented by an embedded property. You can also specify this property by using an expression. All other properties are ignored if you specify the single track.

      • Browse — Read records from the decision data store.

        • In the Maximum number of records to read field, enter a value to define the threshold for stopping the browse operation. You can also define this value through an expression.

        • In the Store results in field, define the result page. The result page consists of an existing Code-Pega-List page.

      • Browse by keys — Read records from the decision data store by a key.

        • Select a key and enter the key value. You can also define the key value through an expression.

        • Optional: To define more than one key, click Add key.

        • In the Store results in field, define the result page. The result page consists of an existing Code-Pega-List page.

      • Delete by keys — Remove records from the decision data store by a key.

        • Select a key and enter the key value. You can also define the key value through an expression.

        • Optional: To define more than one key, click the Add key button.

      • Delete track — Remove a single track from the decision data store.

        • In the Track name field, specify the embedded property that identifies the track to be removed by this operation. You can also specify this property using an expression.

        Note: This operation can take a considerable amount of time to complete in environments with many decision nodes because it removes the values from every single decision node.
      • Truncate — Remove all records from the decision data store.