Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 25-TBD1 +209 - Max Verstappen - Content
-
... ... @@ -1,83 +1,69 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release,a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover,we have made progress onour alertingimprovement plans and have improved and added several pop-up screens.Find out all we released below!5 +**Hi there, eMagiz developers!** We have done ..... 7 7 8 -== **Feedback Items** == 9 -//__Alerting notification settings__// 10 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature. 7 +{{warning}}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. {{/warning}} 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]] 9 +== **Quicker Deployment Plan** == 10 +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 deploynment plan will be finished much quicker now! 13 13 14 - //__Processcontainers__//15 - Ifamodeldoesnothavelicenseforapattern,themodel contactnow hastheoption todeletetheprocesscontainerof thatgivenpattern.12 +== **Next Generation Architecture Default** == 13 +With this release, the next generation architecture will become the default. New models will use this generation as default. 16 16 17 -//__Design settings__// 18 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment. 15 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]] 19 19 20 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 17 +== **Cloud Template R11 Docker - Single Lane** == 18 +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"]]. 21 21 22 -//__Untested images__// 23 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before. 24 - 25 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 20 +== **Cloud Template R13 Docker - Double Lane** == 21 +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"]]. 26 26 27 -//__Infinispan Cache Manager__// 28 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available. 29 - 30 -//__Infinispan Cache Manager error message__// 31 -We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available. 23 +== **Feedback Items** == 32 32 33 -//__Flow bump__// 34 -When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. 35 - 36 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 25 +//__Unused properties overview__// 26 +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: 27 +* Not used by any runtime that is in the Create phase release. 28 +* Not required by a flow that is in the Create phase release. 29 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 37 37 38 -//__ Unusedsupportobjects__//39 - Support objectsarenowshownin twosections,namely'Supportobjects'and 'Unusedsupport objects'.31 +//__Send build requests asynchronously__// 32 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 40 40 41 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 42 - 43 -//__Deleting routes__// 44 -For clarity purposes, a confirmation pop-up will be shown when deleting routes. 34 +//__Queue explorer milliseconds__// 35 +The queue browser now displays milliseconds in the timestamps. 45 45 46 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 37 +//__Cancel and next buttons order__// 38 +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. 47 47 48 -//__Debug queue__// 49 -The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. 50 - 51 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 52 - 53 -== **Bug Fixes** == 54 -//__Internal server error__// 55 -The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. 40 +//__Unused images__// 41 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 56 56 57 -//__ Namespaceupdate__//58 - Editinganamespaceusedina messagedefinitionautomaticallyupdatesthemessagedefinition&transformations.43 +//__Carwash logging__// 44 +A new logging feature enabling us to make better choices in encryption standards will be released. 59 59 60 -//__ Errorpop-up__//61 - Wefixed an issuewhere apop-upwasshown with anincorrecterrorwhile editing themessage mappingofasynchronous flows.46 +//__Static alerts queue consumers__// 47 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server. 62 62 63 -//__SMB inbound channel adapter__// 64 -The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available. 49 +== **Bug Fixes** == 65 65 66 -//__ Heapmemory__//67 - Theinitialcommittedheap memoryof runtimes has beenloweredtobettermatchactualusage.Forthis,anewruntimeimage LINK is available.51 +//__Flow Designer connection line__// 52 +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. 68 68 69 -//__ Classpathconflicts__//70 -We updatedtransitive runtime dependenciestoprevent potentialconflictsontheclasspathforextendedimages.54 +//__Portal for migrated models__// 55 +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. 71 71 57 +//__Error channel inbounds__// 58 +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. 59 + 72 72 == **Fancy Forum Answers** == 73 73 74 74 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: 75 75 76 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 77 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 78 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 64 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 79 79 80 -== **Key Takeaways** ==66 +== **Key takeaways** == 81 81 82 82 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: 83 83 ... ... @@ -85,9 +85,10 @@ 85 85 * If you have feedback or ideas for us, talk to the Platypus 86 86 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 87 87 * Clear your browser cache (Ctrl + Shift + Del) 88 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]74 +* Check out the release notes [here] 89 89 * Start thinking about how the license tracker can aid your development 90 90 * Start thinking about major, minor, and patch 77 +* Upgrade to the latest build number 91 91 * Keep making great integrations 92 92 93 93 Let's stay in touch and till next time! ... ... @@ -95,11 +95,6 @@ 95 95 {{info}} 96 96 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 97 97 98 -{{/info}} 99 -))) 100 - 101 -((( 102 -{{toc/}} 103 -))) 85 +~*~* Indicates a next-generation-architecture only feature. 86 +{{/info}})))((({{toc/}}))){{/container}} 104 104 {{/container}} 105 -{{/container}}