Skip to Content
Last modified by Erik Bakker on 2024/09/09 12:46
From version 39.1
edited by Erik Bakker
on 2022/06/13 15:17
Change comment: Deleted image "migration-path-json-related-transformations--json-to-xml-transformation-support-objects.png"
To version 42.1
edited by Erik Bakker
on 2023/01/23 13:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -migration-path-json-related-transformations
1 +JSON Related Transformations
Content
... ... @@ -1,13 +1,8 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -= JSON Related Transformations =
3 -
4 4  Within eMagiz, you have the option to transform messages from JSON to XML, XML to JSON, and from JSON to JSON. In all these scenarios, you had to resort to using at least a custom XSLT, sometimes even in combination with standard components provided by eMagiz. With the new functionality, it has become possible to define what the input and output of a message transformation are and have the option to interpret the input against which can be validated.
5 5  
6 6  Should you have any questions, please get in touch with academy@emagiz.com.
7 7  
8 -* Last update: March 1st, 2022
9 -* Required reading time: 6 minutes
10 -
11 11  == 1. Prerequisites ==
12 12  
13 13  * Basic knowledge of the eMagiz platform
... ... @@ -57,7 +57,9 @@
57 57   o In an asynchronous offramp, no validations need to be changed because you validate the CDM, which is still based on XML.
58 58   o This logic applies the same for other asynchronous and synchronous flows.
59 59  13. If the answer is yes for the flow you are currently editing, you should add a JSON source factory support object and couple this to the validation. See below for how this looks
55 +
60 60  [[image:Main.Images.Migrationpath.WebHome@migration-path-json-related-transformations--JSON-to-XML-transformation-add-support-objects.png]]
57 +
61 61  14. Determine whether any transformation component in your flow has a JSON message. For example:
62 62   a) In an asynchronous onramp, this would be the standard transformation based on your message mapping made in Design
63 63   b) In an asynchronous offramp, no transformation will have JSON as input because here you transform message from CDM to system message and the CDM and that is still based on XML.