Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
Change comment: There is no comment for this version
To version 97.1
edited by Erik Bakker
on 2023/07/17 15:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +201 - Be Informed
Content
... ... @@ -1,19 +1,30 @@
1 -In the last sprint cycle, we focused on the scalability and stability of our infrastructure. 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 ahead, 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.203 - Fast Paced.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 5  =====Minor changes=====
6 6  
7 -* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023)
8 -* Manage - Alerting: Identifiers of triggers are now visible in the edit screen.
7 +* Portal - Menu: the back button is changed to have text so it shows clearer the navigation target. (#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 improvements to the edit integration page. (#954)
11 +* Create - Flow Designer: When deleting one or multiple components, you will not be able to change the selection before confirming or cancelling the delete action. (#969)
12 +* Create - Migrate to 3rd Generation: In the event one or more flows break during migration, a popup will inform the fows containing errors after migration is finished. (#983)
13 +* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to environment. (#979)
14 +* Deploy-Architecture: Upon pressing the button “Apply to environment”, a confirmation page is shown. Here all changes made in the portal that will have an effect in your running environment are listed. These changes can be applied to environment or reverted. (#828)
15 +** Changes made in Deploy Architecture with an effect to 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).
9 9  
10 10  ====Bug fixes====
11 11  
12 -* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016)
13 -* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597)
14 -* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release.
20 +* Design - Solutions: We fixed an issue that a message mapping error is displayed 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 Gen3 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 you 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)
15 15  
16 16  =====Infra and image changes=====
17 17  
18 -* Infrastructure: Tightened security policies for a more secure infrastructure.
19 -* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower
29 +* Changed the endpoint that is used for sending errormessages to the eMagiz Control Tower.
30 +* Updated the Spring version of the gateway supporting deploy and manage phase operations.