Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:34
From version 15.1
edited by Eva Torken
on 2023/11/23 16:36
Change comment: There is no comment for this version
To version 14.1
edited by Eva Torken
on 2023/08/23 13:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,7 +22,7 @@
22 22  
23 23  {{info}}~* Note Changing the default messaging format does not affect existing operations in Create. Migrating these flows requires a reset of the exit flow. Additionally, the default response in Catalog has to be changed to application/xml. {{/info}}
24 24  
25 -== 3.1 Impact in Create ==
25 +== 4. Impact in Create ==
26 26  
27 27  After the flows are resetted in Create, the automatic flow creation in the Create phase is adapted to the new default setting. When changing the messaging format to XML, the components of newly generated flows are created with different names and settings. The image below shows an example of an API GET operation with XML as the default messaging format. Besides the changed naming of the transformation, no JSON factory support objects are required in your flow in comparison with a JSON messaging format.
28 28