Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 72.1
edited by Erik Bakker
on 2023/04/28 08:08
Change comment: There is no comment for this version
To version 262.3
edited by Danniar Firdausy
on 2024/07/02 13:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - The Last Post
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,38 +1,17 @@
1 -Here's our first release of this quarter. We have delivered additional small (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several improvements in the way of work for nextGen environments.
1 +During the recent sprint cycle, our focus has been on enhancing flow testing performance, resulting in up to threefold faster execution times. Additionally, we've refined platform usability based on community feedback, which includes enhancements to help text functionality, various pop-up pages, and the user interface for debugging integration flows. Find out all features and fixes below.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.224 - Summer Sonata||target="blank"]].
4 4  
5 -=====New features=====
5 +====New features====
6 +* Design - API management: Model contacts are now able to select a default SwaggerUI environment from the API management settings in Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. (#438)
7 +* Capture - Settings: It is now possible to filter the message types in Capture on whether they are used. (#1281)
8 +* Manage - Monitoring: Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be updated in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
6 6  
7 -* Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing.
8 -
9 -=====Minor changes=====
10 -
11 -* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
12 -* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
13 -* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
14 -* Administration-User management: Company contact can edit permissions of models that fall under child companies
15 -* Administration: Contracts page removed
16 -* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17 -* Deploy - Releases: We reduced the time it takes to prepare a release, before it can be deployed. The process of building runtime images has been optimized.
18 -* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
19 -* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
20 -* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
21 -* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
22 -* Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
23 -* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
24 -* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401, if no API-Key was supplied. Please reset your entry flow to apply the fix.
25 -* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
26 -* Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
27 -* Create - Flow designer: Improve responsiveness of resources tab at right panel
28 -* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
29 -
30 30  ====Bug fixes====
11 +* Create - Flow Designer: The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
12 +* Create - Flow designer: We fixed a transformation tooling issue where it was not possible to view an XSLT in certain cases.
13 +* Create - Flow Designer: In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
14 +* Create - Flow Designer: The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. (#1215)
15 +* Create - Properties: Support has been added to provide the SFTP session factories with a known_hosts in string format rather than file format, so it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
31 31  
32 -* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
33 -* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 -* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
35 -* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.
36 36  
37 -====Remarks====
38 -