Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 534.1
edited by Carlijn Kokkeler
on 2024/05/29 10:51
Change comment: There is no comment for this version
To version 489.1
edited by Carlijn Kokkeler
on 2024/04/24 09:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +219 - Creation Carousel
Content
... ... @@ -3,53 +3,61 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we improved the user interface for managing your failover and grouping configurations and improved the method for adding new attributes to data models. Next to this, we have improved the Event Catalog overview for Catalog users. Using the back button on the eMagiz Q&A now also brings you back to where you were with your search query. We also fixed some previous bugs, resulting in improved delete behavior for containers and correctly generated scope properties. Lastly, there will not be a warning message anymore when importing an XSD if there is no selected request or response message definition.
6 +**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
7 7  
8 8  == **Feedback Items** ==
9 -//__Q&A search__//
10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A.
11 11  
12 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
10 +//__eMagiz Mendix connector__//
11 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
13 +//__External machine agents__//
14 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal. With future releases of environment templates, your on-premise agents may also be updated.
16 16  
17 -//__Attribute placements__//
18 -Some improvements regarding the placement of attributes have been done:
19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute.
20 -* For system message definition, moving an attribute in the data model is now directly reflected in the tree structure as well. However for CDM, API Gateway, and EVS Data Model, moving an attribute will not be directly reflected in the tree structure. A pop-up confirmation, as shown below, will appear with respect to the type of message definition (i.e., system message or CDM) that the user is working with.
21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
16 +//__Improved OpenAPI import__//
17 +The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]]
19 +//__Flow test stack trace__//
20 +If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
24 24  
25 -//__Failover & grouping__//
26 -Some improvements regarding the widgets for failover and grouping have been done:
27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
22 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
24 +{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
26 +To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
33 33  
28 +In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
29 +
34 34  == **Bug Fixes** ==
35 -//__XSD import__//
36 -When importing an XSD to a new or empty response or request message, you will not receive a warning message anymore to avoid confusion.
31 +//__Error handling__//
32 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
34 +//__Volume mapping passwords__//
35 +Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
39 39  
40 -//__Container deletion__//
41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
37 +//__Create integration removal__//
38 +When removing an integration from Create, the Create phase is now correctly updated.
42 42  
43 -//__Scope properties__//
44 -We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme.
40 +//__Legacy statistics__//
41 +Legacy pages are now correctly hidden when running on the current runtime architecture.
45 45  
43 +//__Unused properties__//
44 +Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
45 +
46 +//__Enumeration values__//
47 +Users are now able to add and edit enumeration values while editing event processor flows in the Create phase.
48 +
49 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
50 +
51 +//__SFTP sessions__//
52 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
53 +
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
51 -* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
52 -* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
58 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
59 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
60 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
53 53  
54 54  == **Key Takeaways** ==
55 55  
... ... @@ -59,7 +59,7 @@
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 60  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
70 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
63 63  * Start thinking about how the license tracker can aid your development
64 64  * Start thinking about major, minor, and patch
65 65  * Keep making great integrations