Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/04/18 13:12
From version 87.1
edited by eMagiz
on 2023/02/28 11:58
Change comment: There is no comment for this version
To version 103.1
edited by Erik Bakker
on 2023/04/13 14:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -193 - Fan Out
1 +195 - Easter Party
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -2,73 +2,98 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last couple of weeks, we worked hard on API improvements and 3rd generation improvements for you all to see. Amongst the API improvements we now introduce the option to define REST/XML structures in your API gateway for your API callers to call. This brings more options to the user community in setting up the API Gateway structure in accordance with the needs and desires of the client. On top of that we have released several 3rd generation improvements. Amongst these we will add WS-Security functionality to the runtime and improvements on viewing release properties. Furthermore we have released new cloud templates to improve security in our current runtime and improve the auto-healing for 3rd generation runtime cloud slots. Last but not least we release the first adaptation of "State generation" that can be implemented with the help of us in your model. In the upcoming monts we will gather feedback from actual client cases and improve on this functionality.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
6 6  
7 -== **REST XML for API Gateway** ==
7 +== **Release properties** ==**
8 8  
9 -{{warning}}Note that a decision needs to be made to select XML or JSON as default format for all your operations hosted in your API Gateway.{{/warning}}
9 +With this release we bring an improved version of the release properties functionality. With the introduction of the 3rd generation runtime the way properties can be updated and when they need to be available for the solution to start up has changed compared to the current runtime architecture. More on that can be found [[here>>Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target= "blank"]].
10 10  
11 -To enhance your options when developing an API gateway that can be called by others we now introduce the option to select XML as the default message format on your API Gateway pattern. You can do this under Design -> Settings -> API Management. In here you can select and edit the settings.
11 +As of now you can not only view all property values related to a specific release by pressing the wrench icon. You can also create what we call a "property release" on each of the three environment that allows you to quickly change one or more property values and deploy the changes to your environment. When deploying such a release eMagiz will check on which runtimes the properties are used and only execute the deploy actions for the machines to which said runtime(s) belong(s).
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-default-setting.png]]
13 +{{video attachment="release-blog-easter-party--release-properties.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
14 14  
15 -Every operation made after this decision will default to XML (or JSON which is still the default). Should you want to support JSON on some operations and XML on others you can select a default and manually correct the mediaType for the requests and responses to which it matters.
15 +{{info}}The following considerations need to be taken into account when using this functionality:
16 +* This functionality works from the moment one runtime is running on the 3rd generation runtime architecture
17 +* This functionality can only change property values. Functional changes need a seperate release that needs to be promoted
18 +* In comparison to standard releases a property release can be created on each environment (as the property value is linked to a specific environment).
19 +* While changing a property in a ‘property’ release, users also have the option to alter the value in the Deploy-Properties list. By default, this is set to Yes, because when a new release is created, the values of Deploy-Properties will be used and not properties of an earlier release. When a user closes the screen for editing a property, the change will immediately be implemented.
20 +* The auto-clean release functionality is unaffected by this change, ‘property’ releases will not be counted as a release.
21 +* There is a maximum of 26 ‘property’ releases. (26 letters of the alphabet)
22 +* Only the latest release can be edited. This can be identified by checking the suffix. The suffix with the latest letter of the alphabet is editable.{{/info}}
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@193-release-blog--rest-xml-change-media-type-setting.png]]
24 +== **API improvements** ==
18 18  
19 -==**Cloud Template update** ==
26 +//__Improved auto-generated error handling__//
27 +When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
20 20  
21 -We have released several new Cloud templates which will be installed via the auto-upgrade settings of your model (or manually in case not set).
22 -
23 -====Cloud Template R23 - Single Lane ====
29 +//__Switch default message format__//
30 +We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
24 24  
25 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 2nd generation runtime. This cloud template will update some specific security settings on these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
32 +//__Re-using elements in gateway message__//
33 +This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
26 26  
27 -====Cloud Template R6 - Single Lane ====
35 +//__Improved naming of API operations when adding integrations to Create__//
36 +Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
28 28  
29 -This release introduces a new cloud template for all our customers running in a single-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
38 +== **3rd generation improvements** ==
30 30  
31 -====Cloud Template R6 - Double Lane====
40 +//__Update of the static alerting engine__//
41 +In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
32 32  
33 -This release introduces a new cloud template for all our customers running in a double-lane setup in the 3rd generation runtime. This cloud template will improve the auto-healing functionality of these cloud slots. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
43 +//__Add "Data pipeline" functionality__//
44 +This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
34 34  
35 -== **WS-Security on the 3rd generation runtime** ~*~* ==
46 +//__Fix related to the debugger__//
47 +This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
36 36  
37 -To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols.
49 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
38 38  
39 -== **State Generation ~*~* ==
51 +//__Improved migration process__//
52 +This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
40 40  
41 -With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
54 +//__Deployment plan change__//
55 +In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
42 42  
43 -{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
57 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
44 44  
45 45  == **Feedback items ** ==
46 46  
47 -//__Removed OData as option for an API Gateway operation__//
48 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
61 +//__License Tracker improvements__//
62 +With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
49 49  
50 -//__Changes in API Gateway operation paths is automatically updated in Create__//
51 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
64 +//__Ability to view the message definition for a topic__//
65 +Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
52 52  
53 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
67 +//__Restricted access for uploading custom certificates to endpoints__//
68 +To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
54 54  
55 55  == **Bug fixes ** ==
56 56  
57 -//__Prevent endless loop in Deploy -> User Management__//
58 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
72 +//__Improved deletion behavior for enumerations__//
73 +To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
59 59  
60 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
75 +//__Prevent "async" api operations__//
76 +With this release, we have removed the ability to select the "async" option when the default message format is API Management.
61 61  
62 -//__Update error handling during migration to the 3rd generation runtime__//
63 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
78 +//__Importing a response definition broke the request definition__//
79 +Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
64 64  
81 +//__Removing a flow does not update the API "all-entry" anymore__//
82 +When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
83 +
84 +//__Stop deployment plan when a property is missing__//
85 +Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
86 +
87 +//__Cap stack trace of error messages and log entries__//
88 +To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
89 +
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
68 68  
69 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
70 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
71 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
94 +* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
95 +* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
96 +* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
72 72  
73 73  == **Key takeaways** ==
74 74