Skip to Content
Last modified by Erik Bakker on 2024/09/09 12:46
From version 41.1
edited by Erik Bakker
on 2023/01/23 13:19
Change comment: There is no comment for this version
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
Content
... ... @@ -52,7 +52,9 @@
52 52   o In an asynchronous offramp, no validations need to be changed because you validate the CDM, which is still based on XML.
53 53   o This logic applies the same for other asynchronous and synchronous flows.
54 54  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 +
55 55  [[image:Main.Images.Migrationpath.WebHome@migration-path-json-related-transformations--JSON-to-XML-transformation-add-support-objects.png]]
57 +
56 56  14. Determine whether any transformation component in your flow has a JSON message. For example:
57 57   a) In an asynchronous onramp, this would be the standard transformation based on your message mapping made in Design
58 58   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.