Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/05/22 13:39
From version 83.1
edited by Erik Bakker
on 2023/05/22 15:20
on 2023/05/22 15:20
Change comment:
There is no comment for this version
To version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
on 2023/05/26 08:40
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,9 +9,8 @@ 9 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 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 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: Youcanapplyyour changesto environmentwithouthaving an active release.12 +* Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal. 13 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 15 * General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments. 16 16 17 17 ====Bug fixes====