Skip to main content


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

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.

Configuring the DataSet-Execute method for File

Updated on March 11, 2021

You can automate data management operations on records that are defined by the File 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 navigation panel, by clicking RecordsTechnicalActivityCreate, to start the DataSet-Execute method.
  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. In the Data Set field, enter the name of the File data set.
  8. In the Operation list, select Browse and specify additional settings by performing the following actions:
    1. 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.
    2. In the Store results in field, define the result page. The result page consists of an existing Code-Pega-List page.
  • Previous topic Configuring the DataSet-Execute method for Event store
  • Next topic Configuring the DataSet-Execute method for HBase

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us