Skip to main content

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

Parse Delimited rules

Updated on April 6, 2022

Use a Parse Delimited rule to upload data into your Pega Platform system from an external file or files. Within each input record, a comma, tab, quote, or other character might separate fields. The rule extracts the text between the delimiter characters and stores it in a Single Value property or as one element of a Value List property. This rule expects a single row of data.

Note: As a best practice, upload CSV and XLSX files into your application by using the Integration Designer in App Studio. For more information, see Creating a data model from a spreadsheet.

For complex inputs, one parse rule can call processing that is defined by other Parse Delimited or Parse XML rules.

To process files with multiple rows of data, use the Parse Delimited rule in conjunction with a Service rule.

Where referenced

Parse Delimited rules are primarily used for importing character-delimited text with Service File rules. For more information, see Service File rules.

In addition, an activity can employ a Parse Delimited rule to extract text strings from the value of a property, using the Apply-Parse-Delimited method.


Use the Application Explorer in Dev Studio to access Parse Delimited rules that apply to the work types of your application. Use the Records Explorer in Dev Studio to list all Parse Delimited rules available to you.


Parse Delimited rules are instances of the Rule-Parse-Delimited class. They belong to the Integration-Mapping category.

  • Previous topic Configuring a file listener associated with a storage repository
  • Next topic Creating a Parse Delimited rule

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