Last modified by Danniar Firdausy on 2024/09/30 17:12

From version 25.1
edited by Eva Torken
on 2023/08/23 13:29
Change comment: There is no comment for this version
To version 26.1
edited by Eva Torken
on 2023/08/25 11:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,7 +38,7 @@
38 38  * When you change something to the configuration of the backend operation (i.e. endpoint, parameter, system request/response) the change will **only** impact the specific exit gate
39 39  * When you change the gateway request/response message (with transformation) the change will impact **both** the all-entry and the specific exit gate
40 40  
41 -In all cases, you need a version bump of the flow to which you can relate the change. For exit gates, this process is identical to when you do a version bump of any messaging flow after updating for example a CDM message or message mapping. However, when you update something on the all-entry level this becomes less simple. Because eMagiz does not only pre-configure the resources for you in Create but the complete all-entry flow you **need** a reset of the all-entry to reflect these changes. To reset a flow simply access the context menu on flow level in Create (via a right-mouse click) and press Reset flow.
41 +In some cases, version bumps are needed to confirm the change in Create. For exit gates, this process is identical to when you do a version bump of any messaging flow after updating for example a CDM message or message mapping. However, when you update something on the all-entry level what is needed differs. In case of a security change you need to reset the all-entry flow. To reset a flow simply access the context menu on flow level in Create (via a right-mouse click) and press Reset flow. In case of all other changes, no reset is needed, just a version bump.
42 42  
43 43  [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-updating-your-api-gateway-operations--reset-flow-context-menu.png]]
44 44