Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 263.1
edited by Carlijn Kokkeler
on 2023/11/22 15:02
Change comment: There is no comment for this version
To version 267.1
edited by Carlijn Kokkeler
on 2023/11/23 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -36,15 +36,11 @@
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 +
39 39  //__Queue explorer milliseconds__//
40 40  The queue browser now displays milliseconds in the timestamps.
41 41  
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 -
48 48  //__Static alerts queue consumers__//
49 49  Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
50 50  
... ... @@ -54,11 +54,8 @@
54 54  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.
55 55  
56 56  //__Portal for migrated models__//
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.
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.
58 58  
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 -
62 62  == **Fancy Forum Answers** ==
63 63  
64 64  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: