Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 192.1
edited by Carlijn Kokkeler
on 2024/01/29 15:39
Change comment: There is no comment for this version
To version 73.1
edited by Erik Bakker
on 2023/04/28 08:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +196 - The Last Post
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,31 +1,35 @@
1 -In the last sprint cycle, we focused on improving pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.213 - Joyful Journeys||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 5  =====New features=====
6 6  
7 -* Home - Q&A: The option to search by pressing the Enter key has been added.
7 +* Create - Flow Testing: Till now, the Flow Testing allowed to test eMagiz flows by defining a testing point on the start (and end) point(s), run them and compare the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with an actual "live" endpoint. As a result a “HTTP outbound gateway” can be set in “Live Mode”. When you do this, the HTTP outbound gateway will send its HTTP request to the actual 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.
8 8  
9 9  =====Minor changes=====
10 10  
11 -* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822)
12 -* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172)
13 -* Create - Transformation: UI improvements for static input components have been done. (#1172)
14 -* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129)
15 -* Deploy - Releases: When a new property release is created, this property release can now not only be viewed but also release properties can be deleted. (#1031)
16 -* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053)
17 -* Deploy - Runtime overview: Insight into intended and actual deployments has been improved.
18 -* Deploy - Architecture: It is now possible to change the memory settings of a new container before pressing "Apply to environment". (#968)
19 -* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977)
20 -* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.
21 -* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved.
11 +* 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.
12 +* 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.
13 +* 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.
14 +* 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.
15 +* 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.
16 +* Create - Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17 +* Create - Flow designer: Improve responsiveness of resources tab at right panel.
18 +* Create - 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.
19 +* 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.
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 in order to obtain its name
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’)
25 +* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
26 +* Manage - Explore: A new button to delete queue is added. This button is only visible for authorized personnel.
27 +* Administration -User management: Company contact can edit permissions of models that fall under child companies.
28 +* Administration - Overview: Contracts page removed.
22 22  
23 23  ====Bug fixes====
24 24  
25 -* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021)
26 -* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030)
27 -* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
28 -* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161)
29 -* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
30 -* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS. (#1151)
31 -* Manage - Notification settings: Internal recipients are now added correctly.
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 +* 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.
35 +* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.