Skip to main content


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

Data Transforms - Completing the Create, Save As, or Specialization form

Updated on November 15, 2021

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields using the following Developer Help topicsusing the following Developer Help topics:

This information identifies the key parts and options that apply to the record type that you are creating.

Create a data transform rule by selecting Data Transform from the Data Model category.

A data transform rule has two key parts:

FieldDescription
Apply to Select a class that this data transform applies to.

The list of available class names depends on the ruleset that you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form.

Name Enter a name that is a Java identifier. Begin the name with a letter, and use only letters, numbers, and hyphens. See How to enter a Java identifier.

A conventional name for the initial, and typically the simplest, data transform in a class is pyDefault. This name is not reserved and has no special significance.

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