Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 261.1
edited by Carlijn Kokkeler
on 2024/06/18 12:21
Change comment: There is no comment for this version
To version 76.1
edited by Erik Bakker
on 2023/05/02 14:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - Idyllic Image
1 +196 - The Last Post
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,17 +1,35 @@
1 -In the last sprint cycle, we have worked on releasing a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]], which contains several bug fixes, and increases the debugger duration. Moreover, we have worked on our SwaggerUI settings, filtering, and SpEL Expressions. Find out all features and fixes below.
1 +Here is our first release of this quarter. We have delivered additional minor (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 enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.223 - Idyllic Image||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.196 - The Last Post.WebHome||target= "blank"]].
4 4  
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 reset (or updated) in order to also store the messages for 10 minutes instead of 5.
5 +=====New features=====
9 9  
10 -====Bug fixes====
11 -* Create - Flow Designer: The SMB outbound gateway with the GET command did not work, this has been resolved.
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
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.
7 +* Create - Flow Testing: Till now, Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), running them, and comparing the actual and expected messages. In this release, "Live Mode Testing" is introduced, making testing communication with an actual "live" endpoint possible. As a result, an "HTTP outbound gateway" can be set in "Live Mode." When you do this, the HTTP outbound gateway will send its request to the endpoint. Consequently, the response will be handled by the flow in the flow test so you can determine whether the actual endpoint behaves as expected.
16 16  
9 +=====Minor changes=====
17 17  
11 +* Design - Store: You can encounter a warning message when you import a transformation from the store because your imported transformation requires information from the related store fragment. To avoid a non-functional transformation in the Create phase, you should include that store fragment. Afterward, we will update your default flow component transformer to make it work correctly.
12 +* Design - Store: We updated importing to help you avoid an error while importing store items that will break your message definition in some cases.
13 +* Design - Store: We fixed an issue that you import the message definition(s), and a specialized DataType of imported message definition(s) is not matched with the exported message definition(s). Now, they are matched, and your transformation won't get issues.
14 +* Create - Store: We automatically excluded resources that are not good enough from the exporting wizard. Then you will find it easy to recognize a problem and avoid creating unusable store items.
15 +* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can only change the CDM message definition, Gateway message definition, or even Event streaming message definition with the proper rights. (#690)
16 +* Create - Flow designer: Model resources tab removed on the resources page when adding a resource to a validating filter. (#921)
17 +* Create - Flow designer: Improve the responsiveness of the resources tab on the right panel.
18 +* Create - Flow Designer: Resources in the "Unused resources" section can be marked as used when components refer to the resources through property placeholders or in custom SPeL expressions.
19 +* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests if that parameter was not supplied, so please reset your entry flow to apply the fix.
20 +* 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.
21 +* Create - Resources: When viewing a resource, its full name will be shown, removing the need to download the resource to obtain its name. (#922)
22 +* 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.
23 +* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
24 +* Deploy - Architecture: The topics are now ordered alphabetically, and the runtimes will now get the same order as design architecture (after 'apply to environment') (#543)
25 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are run.
26 +* Manage - Explore: A new queue delete button is added. This button is only visible to authorized personnel.
27 +* Administration -User management: Company contact can edit permissions of models that fall under child companies. (#895)
28 +* Administration - Overview: Contracts page removed. (#907)
29 +
30 +====Bug fixes====
31 +
32 +* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They better explain what you need them for and mention essential security considerations.
33 +* Create - Flow designer: Various minor (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34 +* Deploy - Releases: We fixed an issue where after removing containers from a machine, during the execution of the deployment plan, the removed containers are not recognized as change, causing the 'Deploy machine' step to be skipped. (#514)
35 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs. (#940)