Explain about PEGA Data transform?

A data transform describes how data in one format and class is into data in another format and class. Setting property values with a data transform rather than an operation speeds up growth and simplifies device maintenance.

Data transform in PEGA

A data transform is a collection of steps that must be in a certain order. When the machine calls the data transform, it performs each operation in the order specified in the record form of the data transform. A data transform can be used as follows.

• Prepare data for use on a data page by normalizing it.
• With operations, you can define, copy, or map info.
• To render a new website, copy a clipboard page.
• Map one page’s properties (and their values) to another, already existing page.
• On one tab, map properties (and their values) to a different page.
• Create one or more initial properties on a particular clipboard page and set their values. In one processing stage, a data transform will set several property values on a page.
• Pages from one Web List property are appended to another.

Kinds of transformations in PEGA

Data transformations and data pages are two kinds of data transformations.

Data pages are used in the following data transformations for data management.

Copying a subset of data from the data page to the property using the data transform.

When you pick Copy data from a data page on the Edit Property type, the Optional Data Mapping field appears. Copy a subset of the data from the data page to the property using this data transform. The machine copies all of the data from the data page to the property if you don’t define a data transform.

Create a data transformation submission in PEGA

The request data transform lets you map Pega Platform data to the fields that the connector uses to communicate with the data provider while the data source for data. On the Data Page rule form’s Description tab, in the Data sources section, pick the data to transform to use in the Request Data Transform sector. Learn Pega Online Training

The transformation of response data in PEGA

Normalize data from data sources into the standard application data model with response data transformations. Where the data source class and the data page class are incompatible, an answer data transform is required (the recommended pattern to achieve true data virtualization). On the Data Page rule form’s Description tab, in the Data sources section, pick the data to transform to use in the Response Data Transform region.

A data transform describes how to transform data from one format and class (the source) into data of a different format and class (the target). Clipboard and JSON are also supported formats. Setting property values with a data transform rather than an operation speeds up growth and simplifies device maintenance.

Benefits of Data transformations in PEGA

Data transformations are beneficial in the following situations.

• When handling framework data with data pages (see the Where referenced section below).
• When it comes to operations, when:
• Making a new website from a clipboard page.
• Mapping properties (and their values) from one page to a previously generated page.
• Objects (and their values) from one page are mapped to a different one.

A data transform can be created for either a clipboard or a JSON model file. On the Create Data Transform method, you choose the type of data transform in the Additional configuration options portion. Depending on which model format you choose, you may have different choices.

You may opt to map all data in the JSON string or individual properties. This is in the JSON model format automatically. When you have a long JSON string and just think for a few properties, when you want to modify the JSON structure, and when the fields in the JSON have different names from the clipboard properties to which you are mapping, mapping individual properties is helpful.

Data pages are used in the following data transformations for data management.

Data mapping on the property type in PEGA

It is an optional feature. When you pick Copy data from a data page on the Edit Property type, the Optional Data Mapping field appears. Copy a subset of the data from the data page to the property using this data transform. The machine copies all of the data from the data page to the property if you don’t define a data transform.

The request data transform

Lets you map Pega Platform data to the fields that the connector uses to communicate with the data provider while the data source for a data page is a connector. This is an integration with an external data service.

Response data

You convert and normalize data from data sources into a standard application data format. Where the data source class and the data page class are incompatible. This is an answer to the question of whether you need not a data transform. This is as well as the suggested pattern for achieving true data virtualization. On the Data Page rule form’s Description tab, in the Data sources section, pick the data to transform to use in the Response Data Transform region.

Normative naming

For most basic concrete classes and some standard abstract classes, the Pega 7 Platform provides a standard data transform called by default. The Data-Admin-Operator-ID, for example. In the Operator ID data case, the by default data transform provides initial values for around 25 properties.

There are no particular features of this name and it is not a protected name. In any class or RuleSet, you can construct data transformations with this or other names.

Data transformations that refer to Work-derived groups

The Pega 7 Platform uses the pyFlowName property in the object to define a flow rule to start if a new work item is produced.

Include a value for the pyFlowName property if you construct a data transform called by default with the Applies To main part class derived from the Job- base class. To apply the ancestor by default data transformations as well, pick the Call SuperClass data to transform the check box in most situations.

Set the Flow Name main component of a flow law as the meaning of this property. The code uses this value with rule resolution to locate the flow rule to run when a user begins a new flow in the form of that Work-class.

Data transformations that refer to the class System-User-MyRules

As the Applies, data transforms with System-User-MyRules. The order and link labels for reports in the Monitor Operation workspace are managed by the main component by default. Data transformations are also referenced in other aspects of the Pega Platform, such as follows.

• A data transform can be used by many operation methods that run on websites. This includes Apply-DataTransform, Apply-Model, Page-New, Page-Copy, and Page-Change-Class.
• Starter flows (flows that generate work items) may define a data transform for a Work-class to set initial properties for the work object (on the flow’s Phase tab).
• The framework will add a data transform before or after showing the flow action user interface to the user, according to the Action tab for a flow action.
• Data transformations can be defined on the Set Properties tab of the Connector Properties panel for flows that have been edited using the Flow type.
• The Client Event Editor, for example, has the following user interface elements:
• re-energize This Segment is taking initiative.
• When circumstances change, refresh
• Control law actions that occur when a user clicks a button Open URL In Window, Show Harness, and Refresh Section

Conclusion

Other data transformations can make use of data transform laws. Data transformations may be used for rule types that build clipboard pages, such as Connector rules, Service rules, and another rule type. You can know more about data transformations in PEGA through PEGA training.