Changes for page 210 - Deployment Delights
Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 267.1
edited by Carlijn Kokkeler
on 2023/11/23 08:57
on 2023/11/23 08:57
Change comment:
There is no comment for this version
To version 263.1
edited by Carlijn Kokkeler
on 2023/11/22 15:02
on 2023/11/22 15:02
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -36,11 +36,15 @@ 36 36 * Not required by a flow that is in the Create phase release. 37 37 * If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 38 38 39 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]] 40 - 41 41 //__Queue explorer milliseconds__// 42 42 The queue browser now displays milliseconds in the timestamps. 43 43 42 +//__Unused images__// 43 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 44 + 45 +//__Carwash logging__// 46 +A new logging feature enabling us to make better choices in encryption standards will be released. 47 + 44 44 //__Static alerts queue consumers__// 45 45 Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 46 46 ... ... @@ -50,8 +50,11 @@ 50 50 In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. 51 51 52 52 //__Portal for migrated models__// 53 -We fixed a rare case where a runtime either (1)could not start, or(2)logging, errors,and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.57 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 54 54 59 +//__Error channel inbounds__// 60 +We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 61 + 55 55 == **Fancy Forum Answers** == 56 56 57 57 As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: