Skip to Content

Changes for page 204 - Found It

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +197 - Pay Attention
Content
... ... @@ -1,30 +1,26 @@
1 -In the last sprint cycle, we focused on planning ahead, finishing up and working on the Hackathon to fix several smaller items.
1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. 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.201 - Be Informed.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
4 4  
5 +=====New features=====
6 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
8 +
5 5  =====Minor changes=====
6 6  
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).
11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
17 17  
18 18  ====Bug fixes====
19 19  
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)
17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 +* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.
22 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
26 26  
27 -=====Infra and image changes=====
24 +====Remarks====
28 28  
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.
26 +* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.