Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 82.1
edited by Erik Bakker
on 2023/05/22 15:19
on 2023/05/22 15:19
Change comment:
There is no comment for this version
To version 218.1
edited by Erik Bakker
on 2025/01/13 09:30
on 2025/01/13 09:30
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 198-GreatMigration1 +236 - Another Agent - Content
-
... ... @@ -1,27 +1,20 @@ 1 - Anothercouple of weeks have passed, so itistime foranewrelease.Wehavefocusedinthis periodonimprovingtheigrationprocess towardsthe next-generation architectureas wellashow the user experience andinteraction withthenext-generationarchitectureworks.1 +In the last sprint cycle, we focused on delivering new [[cloud templates>>Main.Release Information.Cloud Templates||target="blank"]] for docker single and docker double lane. Moreover, we have addressed several key feedback points within our platform. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 198-GreatMigration.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.236 - Another Agent||target="blank"]]. 4 4 5 -==== =New features=====5 +====Major Changes==== 6 6 7 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 7 7 8 -==== =Minorchanges=====9 +====Minor Changes==== 9 9 10 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete. 11 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too. 12 -* 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. 13 -* 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. 14 -* 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. 15 -* Deploy - Architecture: You can apply your changes to environment without having an active release. 16 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing. 17 -(control tower, so Gen3 only) 18 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments. 11 +* Create - Flow Designer: Improved help texts for the FTP & SFTP local filter options. 12 +* Deploy - Overview: Spring6 pop-up has been removed. 13 +* Manage - Alerting: The recipients tab for the new Alerting triggers has seen a small update in regards of UX: You will get an explanation when you are trying to enable notifications when no recipients are selected yet. 19 19 20 20 ====Bug fixes==== 21 21 22 -* 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. 23 -* 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. 17 +* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456) 18 +* Create - Transfer Settings: You can now increase and decrease the number of runtimes for existing Systems. And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543) 19 +* Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients. 24 24 25 -====Remarks==== 26 - 27 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.