Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:34
From version 2.6
edited by Bouke Reitsma
on 2023/02/28 17:05
Change comment: There is no comment for this version
To version 3.1
edited by Bouke Reitsma
on 2023/03/01 09:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,11 +24,13 @@
24 24  
25 25  == 4. Impact in Create ==
26 26  
27 -The automatic flow creation in the Create phase is updated to incroperate these changes. When changing .....
27 +The automatic flow creation in the Create phase is updated to incorporate these changes. When changing the messaging format to XML, the components of newly generated flows are adapted to the changes. The image below shows the changed flow when building an API GET operation. Besides the changed naming of the transformation, no support objects are required for this GET operation, since your gateway does not require a JSON response any more.
28 +
29 + AFBEELDING 2 TOEVOEGEN
28 28  
29 29  == 4. Assignment ==
30 30  
31 -Change the default messaging format to XML.
33 +Change the default messaging format to XML.
32 32  This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
33 33  
34 34  == 5. Key takeaways ==
... ... @@ -35,7 +35,7 @@
35 35  
36 36  * The default messaging format can be changed to XML
37 37  * Updating this only affects new flows
38 -* Migrating existing operations can be done by reseting the exit flow
40 +* Migrating existing operations can be done by resetting the exit flow
39 39  
40 40  == 6. Suggested Additional Readings ==
41 41