Data modeling: ------------The Data Model category contains "property rules" and six other rule types closely

related to property initialization, editing, and validation.

1.Data Transform 2.Edit Input 3.Edit Validate 4.Field Value

5. Property 6.Property Alias 7.Property Qualifier

1.Data Transform rules: -----------------------

Purpose: -------

Use a data transform rule to define how to take source data values data that is in one format and class and turn them into data of another format and class (the "destination" or "target").

In general, data transformation involves both mapping data from a source to a target, and performing any conversions or other transformations on that data that might be required to achieve the intended mapped results.

Some examples of situations in which to use a data transform rule are:

Copying a clipboard page to make a new page.

Mapping properties (and their values) on one page to another, existing page.

Mapping properties (and their values) on one page to a new page.

On a given clipboard page, defining one or more initial properties on that page and setting their values. A data transform can set many property values on a page in one processing step.

---------from PDN--Introduction to data transforms Article ID Category Applies from Last Updated --------------------PRKB-26379 Data Structures PRPCv62 August 4, 2011

Question: --------What is a data transform and what can I as a developer accomplish with data transforms?

1.What is a data transform? --------------------------ans:Data transformation typically involves both mapping data from a source to a target, and performing any conversions or other transformations on that data that might be required to achieve the intended mapped results.

-->Data transform rules are instances of the "Rule-Obj-Model" class. Prior to Version 6.2, these rules were known as" model rules", and only involved setting property values. Starting with Version 6.2, these rules provide more powerful actions than in V5X-V6.1 .

-->A data transform is presented as a "structured sequence of actions". When the system invokes the data transform rule, it invokes each action in turn, following the sequence defined in the data transform's rule form.

The Data Transform rule form: ---------------------------The actions to be taken are presented as a sequence of rows in a tree grid. Except for the conditional types of actions (such as When, For Each Page In, and similar actions) and transitional actions (such as Exit For Each and similar actions), the system invokes each row in sequence, starting with the first row.

Definition tab with sample row

In general, each row provides for:

Column Action: Target :

Description An action to be taken. A target, if the action requires a target.

Relation: A relation, if the action requires a relation to be specified. This relation is a relationship between the specified target and source. Source : A source, if the action requires a source.

Some actions do not involve sources, targets, or relationships. The form makes an item unavailable for selection if it cannot be used in the specific context of the particular action in that row, or in the row's position in the array with respect to its parent rows.

Best practice: In general, aim to limit a data transform to fewer than 25 steps. If more actions are needed, create a separate data transform rule and use the Apply Data Transform action in the first data transform rule to invoke the second data transform, that will complete the subsequent actions. Rows as siblings and children In the Definition tab, you can set the logical structure of actions by rightclicking an existing row and selecting to add a sibling (either above or below the existing row) or add a child row (for actions that can have children).

This tree-like structure is automatically applied when you use conditional actions. The array on the Definition tab reflects the conditionalized sequence using an expanding-collapsing tree structure.

For example, the following image shows a When - Otherwise conditional sequence. In this example, if a property value indicates that the customer's Billing Address is the same as the Shipping Address, then the BillingInformation page is updated by copying values from the ShippingInformation page. Otherwise, the BillingInformation page's properties are set to blank.

Example of When and Otherwise actions

When you specify an action that requires certain subsequent actions, the system automatically adds rows for those required children actions. Parameters tab Define variables that input data to, or return data from, a data transform. Parameter names and values are held on a special page the parameter page that is not visible on the Clipboard tool display.

In fields on the Definition tab, use the notation param.ParamName to reference a parameter value.. Pages & Classes tab To use page names in fields on the Definition tab, those pages must be specified on the Pages & Classes tab.

At runtime, the system uses this information to find properties on the clipboard that are referenced on the Definition tab using the notation .Propertyname. The page name for the property is identified according to the specific context at runtime (depending on things such as the particular data transform action involved, a preceding action that set the page name, etc). The leading period

(or dot) is required.

The system also uses information on this tab to interpret property references of the form Pagename.Propertyname used in various fields on the Definition tab. Scroll to top