Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 258.1
edited by CarlijnKokkeler
on 2023/11/21 12:35
Change comment: There is no comment for this version
To version 502.1
edited by CarlijnKokkeler
on 2024/05/06 13:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +220 - Patch Parade
Content
... ... @@ -3,72 +3,67 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
6 +**Hi there, eMagiz developers!**
7 7  
8 -{{warning}}
9 -Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 -{{/warning}}
8 +== **Feedback Items** ==
11 11  
12 -== **Quicker Deployment Plan** ==
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
13 13  
14 -We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now!
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
15 15  
16 -== **Next Generation Architecture Default** ==
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
17 17  
18 -With this release, the next generation architecture will become the default. New models will use this generation as default.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
21 21  
22 -== **Cloud Template R11 Docker - Single Lane** ==
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
23 23  
24 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
25 25  
26 -== **Cloud Template R13 Docker - Double Lane** ==
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
27 27  
28 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
29 29  
30 -== **Feedback Items** ==
33 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
31 31  
32 -//__Unused properties overview__//
33 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
34 34  
35 -* Not used by any runtime that is in the Create phase release.
36 -* Not required by a flow that is in the Create phase release.
37 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
38 +== **Bug Fixes** ==
39 +//__Annotation styling__//
40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
38 38  
39 -//__Queue explorer milliseconds__//
40 -The queue browser now displays milliseconds in the timestamps.
42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
41 41  
42 -//__Cancel and next buttons order__//
43 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
44 +//__Filter rejection warnings__//
45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
44 44  
45 -//__Unused images__//
46 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
47 47  
48 -//__Carwash logging__//
49 -A new logging feature enabling us to make better choices in encryption standards will be released.
49 +//__Manage Explore__//
50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
50 50  
51 -//__Static alerts queue consumers__//
52 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
52 +//__Page refreshing__//
53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
53 53  
54 -== **Bug Fixes** ==
55 +//__Message redelivery__//
56 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
55 55  
56 -//__Flow Designer connection line__//
57 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
58 -
59 -//__Portal for migrated models__//
60 -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.
61 -
62 -//__Error channel inbounds__//
63 -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.
64 -
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  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:
68 68  
69 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
62 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
63 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
64 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
70 70  
71 -== **Key takeaways** ==
66 +== **Key Takeaways** ==
72 72  
73 73  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
74 74  
... ... @@ -76,10 +76,9 @@
76 76  * If you have feedback or ideas for us, talk to the Platypus
77 77  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78 78  * Clear your browser cache (Ctrl + Shift + Del)
79 -* Check out the release notes [here]
74 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
80 80  * Start thinking about how the license tracker can aid your development
81 81  * Start thinking about major, minor, and patch
82 -* Upgrade to the latest build number
83 83  * Keep making great integrations
84 84  
85 85  Let's stay in touch and till next time!
... ... @@ -87,7 +87,6 @@
87 87  {{info}}
88 88  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89 89  
90 -~*~* Indicates a next-generation-architecture only feature.
91 91  {{/info}}
92 92  )))
93 93