Transformation

This document will help you to understand and work with the MAPPING and TRANSFORMATION functionality in APPSeCONNECT portal. Primarily transformation is the field where the corresponding schemas are to be mapped. This is also the place where the logic behind the transformation is implemented such that the integration proceeds uninterrupted.

What is Mapping

The transfer of information between the schemas is done by mapping the source and the destination schema for an attribute in the touchpoint level. The attributes of the schema may vary for different applications. Mapping of a touchpoint is required to define which attributes of the target schema correspond to those of the source schema.

Click to know more about the source and destination mapping.

Pathway to Transformation

1. Login to the APPSeCONNECT Portal with valid credentials.
2. Navigate to the ‘Connections’ Page in the APPSeCONNECT Portal.
3. Click ‘View the connection’ button in the Connection which you have created.
4. Navigate to any of the touchpoints where you want to implement the mapping.
5. Click on the Transform button. The Transformation Window opens.
   
6. The Mapping of the Attributes are done at the transform level of the touchpoint.

Note: This is the Mapping Screen of touchpoint Invoice Add. The user can expand the Transformation node, to view the attributes present in the touchpoint.

Protip: The user can see the existing mapping for this touchpoint as it is Pre-Packaged. If the user clicks on any other touchpoint, for any other connection, the pathway and the structure of the Transformations mapping remains the same.

Structure of Mapping

Click to know about structure of Mapping

Process of Transformation

The data coming from the source schema requires to be transformed individually such that it matches the format of the destination schema, everytime the touchpoint is synced.

E.g: Suppose you are executing Invoice Add touchpoint, you can see that records of all the Invoices are drew from the source app and for this case the similar execution process of transformation is deployed multiple times. Here a loop is set relatively than writing the transformation logic multiple times, and this undergoes execution whenever the touchpoint is synced in the For-Each Loop Node.

Expanding the For-each loop the user gets the view of the node oInvoices. oInvoices is an object that is used to send data to the target application.

Note: For different touchpoints the object is different. For the touchpoint Sales Order Add the object is oOrders for Simple Product Add it is oItems and so on.

On expanding the object oInvoices the user gets the view of the several attributes that are listed under it. Each attribute has separate information about the entity that it belongs to.
Each of these attributes will contain different information about the customer record.

For Example: Document_Lines will contain the details of the Product in terms of Quantity and Unit Price etc, DocumentsAdditionalExpenses contains the Freight, Tax information etc of the product.

Note: Different objects in different touchpoints will have different attributes

Expanding the row, displays the destination attributes in the touchpoint level.

All fields or attributes present in the touchpoint are mapped with the corresponding fields of the source schema.

Root entity variable

A root entity variable is a variable that is value specific to every iteration. Every entity item has this variable declared with it such that it is present in every iteration and has a different value for every schema item.

Root Entity Variable can be used several times in different parts of the transformation process underlying in the touchpoint. Its value however will be different for every iteration.

Protip Every Object has - Query params and Root Entity variable, whatever touchpoint they cater to