Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/05/22 13:36
From version 106.1
edited by Erik Bakker
on 2023/09/15 08:33
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 -205 - World Explorers
1 +201 - Be Informed
Content
... ... @@ -1,24 +1,30 @@
1 -In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact.
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.205 - World Explorers.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 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 -
8 8  =====Minor changes=====
9 9  
10 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
11 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
12 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046)
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).
13 13  
14 14  ====Bug fixes====
15 15  
16 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
17 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
18 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
19 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
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)
20 20  
21 -
22 22  =====Infra and image changes=====
23 23  
24 -* No infra and/or image changes is this release.
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.