Search: "transformation"

PDF Transformation

We’ll cover how to set up your transformation flow with custom XSLT and essential support objects. While visual transformation tools aren’t available for PDF, we’ll guide you through the necessary steps to configure your flow effectively.

Key concepts == This microlearning focuses on creating PDF documents with the help of the transformation functionality in eMagiz. * Custom XSLT is needed * Support Objects are needed to make the transformation work == 3.

expert-create-your-transformations-pdf-transformation

Image Transformation

expert-create-your-transformations-image-transformation

Key concepts == This microlearning focuses on performing image transformations in eMagiz. By image transformation, we mean transforming the raw data that represents an image into another image format

Image Transformation == In most cases, you will transform XML messages to other XML messages, or you will transform JSON or EDI messages in another of these formats.

[[image:Main.Images.Microlearning.WebHome@expert-create-your-transformations-image-transformation-image-transformation-component-help.png]] Secondly, we must select the desired image format we want to transform.

Transformation - Grouping

{{container}} {{container layoutStyle="columns"}} ((( In this microlearning, we will explore the grouping functionality, which allows you to organize data based on specific criteria, ensuring efficient and customized transformations. Before diving into the details of grouping functionality within eMagiz's transformation tooling, it's important to understand the basic concepts covered in the [[crash course>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-transformation-xml-to-xml||target="blank"]].

Transformation - Grouping == This provides several options for organizing a list of source entities into groups within the transformation tooling.

[[image:Main.Images.Microlearning.WebHome@intermediate-create-your-transformations-grouping--current-group-with-a-parent-group.png]] == 4.

Transformation - XPath Basic

crashcourse-platform-create-transformation-xpath-basic

Transformation XPath Basic == Sometimes the transformation tooling does not provide you with the exact correct transformation option to get the desired result in your output.

Specifically how you can use it while transforming your messages with the help of the transformation functionality in Create.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-transformation-xpath-basic--emagiz-transformation-custom-xpath-result.png]] == 4.

Transformation XML to XML

crashcourse-platform-create-transformation-xml-to-xml

Key concepts == This microlearning focuses on the transformation in Create (XML to XML). With transformation we mean: Transforming the data in such a manner that the source message will lead to a valid target message == 3.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-transformation-xml-to-xml--entitity-filter-result.png]] === 3.2 Transform === The second option at your disposal to ensure that you generate a valid target message is to transform.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-transformation-xml-to-xml--attribute-transformation-option-filled-in.png]] To visually tell you and others that a transformation has been added the blue rectangle will appear.

Data type transformations

We'll focus on transforming data from string to date/time, a common task in eMagiz.

Data type transformations == Several data type transformations could be done with eMagiz.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-data-type-transformations--data-type-transformation-starting-point.png]] As we talk about a transformation we need to select the transformation icon (the blue rectangle, remember).

Transformation - JSON to XML

Key concepts == This microlearning centers around transforming JSON to XML By transforming we mean: Making sure that the input message is transformed in a valid output message by defining how this should happen eMagiz natively supports the transformation of JSON to XML with the help of: * Default message format * Data models in Design * Message mapping in Design * Create transformation in Create * Support Objects == 3. Transformation - JSON to XML == In this microlearning, we will focus on transforming JSON to XML within the tooling of eMagiz.

If you are unsure how to do this please revisit the section on Design in the Crash Course Platform. === 3.4 Create transformation in Create === Just as you are used to you simply create the correct transformation functionality (filter, transformation, static input, etc.) as you would do when you would create the correct transformation functionality for XML messages.

Transformation - XML to JSON

Key concepts == This microlearning centers around transforming XML to JSON By transforming we mean: Making sure that the input message is transformed in a valid output message by defining how this should happen eMagiz natively supports the transformation of XML to JSON with the help of: * Default message format * Data models in Design * Message mapping in Design * Create transformation in Create * Support Objects == 3. Transformation - XML to JSON == In this microlearning, we will focus on transforming XML to JSON within the tooling of eMagiz.

If you are unsure how to do this please revisit the section on Design in the Crash Course Platform. === 3.4 Create transformation in Create === Just as you are used to you simply create the correct transformation functionality (filter, transformation, static input, etc.) as you would do when you would create the correct transformation functionality for XML messages.

Exercise - Create transformations

crashcourse-platform-exercise-execute-create-transformation

This exercise will show you how to add transformation logic to your transformation in the Create phase (and a bit in Design).

Exercise == In this exercise, please make the following changes to the system message of the TMS system: * Change dataType of the attribute called "OrderDate" to **date** * Add an attribute called "OrderReference" on the Order entity And the following changes to the transformation from CDM to TMS: * Make sure that the "OrderReference" attribute is filled with the constant value of **fixed-54321** * Make sure that the "OrderID" is filled with the input value from the CDM but also make sure that when there is no input value a constant with the value **except-12345** is filled in * Make sure that the incoming "Date" value is properly transformed from a dateTime value to a date value to prevent validation errors on the "OrderDate" attribute * Add the following custom Xpath for the "Country" attribute under "Order_PickupAddress/Address" and "Order_DeliveryAddress/Address" ** if (Country = 'NL') then 'NL' else 'FR' == 3.

Transformation - XPath Intermediate

Transformation - XPath Intermediate == Within the crash course, we already explained XPath conceptually.

[[image:Main.Images.Microlearning.WebHome@intermediate-create-your-transformations-xpath-intermediate--substring-transformation-tooling.png]] Translating that into an XPath would yield the following result: **substring(SomeAttribute,1,9)**.

Mastering these XPath functions will help streamline your transformations and improve efficiency across projects. == 5.