Skip to Content

Changes for page 204 - Found It

Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 99.1
edited by Erik Bakker
on 2023/08/01 14:57
Change comment: There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +198 - Great Migration
Content
... ... @@ -1,36 +1,24 @@
1 -In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
1 +Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.202 - New Equilibrium.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
6 -
7 -* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 -* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 -* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
11 -
12 12  =====Minor changes=====
13 13  
14 -* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 -* Deploy - Releases: The infographic has been updated.
16 -* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 -* Deploy - Property release: Names of properties can be created/removed/edited.
18 -* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 -* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#996)
20 -* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21 -* Infrastructure: Tightened security policies for a more secure infrastructure.
7 +* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 +* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 +* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10 +* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11 +* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12 +* Deploy - Architecture: You can apply your changes to environment without having an active release.
13 +* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 +(control tower, so Gen3 only)
15 +* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
22 22  
23 23  ====Bug fixes====
24 24  
25 -* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26 -* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27 -* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28 -* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29 -* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30 -* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31 -* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32 -* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33 -* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34 -* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35 -* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
19 +* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
20 +* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
36 36  
22 +====Remarks====
23 +
24 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.