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.

Decision data rule type enhancements

Updated on August 31, 2018

The import and export functionality for decision data is extended to help manage generic decision data records. Generic decision data records are records that do not belong to the Strategy Results class.

To use the import functionality, you configure decision data records in a CSV file and import the file to the Pega 7 Platform. To use the export functionality, you can save the existing configuration of decision data records to a CSV file and store that file outside of the Pega 7 Platform. The Import and Export options are on the Design tab of the Decision data rule form.

The Edit Decision Data form

Decision data record rule form for a non-SR class decision data record

To ensure that each generic decision data record that you store is unique, you can select the properties that are used as keys on the Form tab of the Decision Data rule form. You can use multiple properties as keys. When you import decision data records to the Pega 7 Platform or save the rule instance, the system determines whether the composite key value is unique. If no unique values for properties have been defined as keys for two or more records, you cannot import or save the duplicated records, and an error message is displayed.

You cannot edit or define new keys for decision data records that hold the proposition data.

Consider the following sample records:

  • pyLabel: Customer1; pyName: Anthony Wayne; pyOrganization: ACME
  • pyLabel: Customer2; pyName: Bruce Stark; pyOrganization: ACME

Key configuration

pyOrganization and pyName properties defined as keys for a generic decision data record

If you define pyOrganization as the key, you cannot import or save the records, because the property value for pyOrganization is the same for both records. However, if you add pyName as an additional key, you can import or save those records because at least one property that is defined as the key is unique.

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