Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 00-UnchartedTerritories1 +223 - TBD - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SametKaya1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,66 +1,59 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortunately not quite ready to be released. As a result the output of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier. 6 +**Hi there, eMagiz developers!** 7 + 8 +== **Feedback Items** == 9 +//__SwaggerUI default__// 10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. 6 6 7 - == **Nextgenerationimprovements andbugfixes** ==12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 8 8 9 -//__Enhanced right-hand view within Deployment Plan context__// 10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview. 14 +== **Bug Fixes** == 15 +//__Cron triggers__// 16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 11 11 12 - {{info}}Note that when the JMS containergetsrestarted connection errorsin the logs area normal thing to witness so keep youreyespeeled forthe startup loggingon JMS level togain confidence in the deployment.{{/info}}18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 13 13 14 -//__ Improvedtimeoutsettings when deploying__//15 - To avoid mismatchesbetweenvariouspartsof theinfrastructurewe haveimproved the timeoutconfiguration on certain deploymentplan stepstoreduce thechancethatthesemismatches occur.20 +//__Trigger activation__// 21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. 16 16 17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 23 +//__Multiple users deploying__// 24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. 18 18 19 -//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 21 21 22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 23 23 24 -//__ Improved loading speedof ManageDashboard__//25 - Thisrelease improvesthe loadingspeedwithwhich allthedashboardsinManageare showntotheuser.This will enhancetheuserexperiencewithinthe Managephase.31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 26 26 27 -== **Store Improvements** == 34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 28 28 29 -//__Importing in Design is improved__// 30 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 31 31 32 -== **Bug Fixes** == 33 - 34 -//__Deprecated reminder pop-up removed__// 35 -We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems. 36 - 37 -//__Improved selection area in Flow Designer__// 38 -When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow. 39 - 40 -//__Improved Kafka settings__// 41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 42 - 43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 44 - 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[ HTTPURL must notbenull>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]50 -* [[ removingthecurledbracketsin aJSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] 44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] 51 51 52 -== **Key takeaways** ==46 +== **Key Takeaways** == 53 53 54 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:48 +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: 55 55 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 -* Check out the release notes [here] 54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 -* Upgrade to the latest build number 64 64 * Keep making great integrations 65 65 66 66 Let's stay in touch and till next time! ... ... @@ -68,6 +68,11 @@ 68 68 {{info}} 69 69 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 71 -~*~* Indicates a GEN3-only feature. 72 -{{/info}})))((({{toc/}}))){{/container}} 64 +{{/info}} 65 +))) 66 + 67 +((( 68 +{{toc/}} 69 +))) 73 73 {{/container}} 71 +{{/container}}