Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 71.1
edited by Erik Bakker
on 2023/04/25 16:36
Change comment: There is no comment for this version
To version 98.1
edited by Erik Bakker
on 2023/07/17 21:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -196 - Last Post
1 +201 - Be Informed
Content
... ... @@ -1,38 +1,30 @@
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 +In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
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.201 - Be Informed.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
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 9  =====Minor changes=====
10 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)
7 +* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8 +* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 +* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 +* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11 +* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12 +* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13 +* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14 +* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15 +** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16 +** Changes with a direct effect will not be listed (for example, restarting a machine).
29 29  
30 30  ====Bug fixes====
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.
20 +* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21 +* Design - Settings: The full length of the contract number can now be registered. (#958)
22 +* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23 +* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24 +* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25 +* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
36 36  
37 -====Remarks====
27 +=====Infra and image changes=====
38 38  
29 +* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30 +* Updated the Spring version of the gateway supporting deploy and manage phase operations.