Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
on 2023/08/29 10:57
Change comment:
There is no comment for this version
To version 296.1
edited by Carlijn Kokkeler
on 2023/12/18 12:45
on 2023/12/18 12:45
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 04-Found It1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,37 +1,43 @@ 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!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** Feedback Items** ==8 +== **TBD** == 8 8 9 -//__Improved check on nested property placeholders__// 10 -To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing. 11 11 12 -//__Removed outdated properties when deploying on the new generation architecture stack__// 13 -We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate. 14 14 15 - {{warning}}Shouldyou still usetheproperties called"emagiz.runtime.name"and "emagiz.runtime.environment"**after**successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}12 +== **Feedback Items** == 16 16 17 -//__ ImprovedperformanceManage Dashboards__//18 - Wehaveimprovedthe efficiencyof retrievingthe datashownintheManageDashboardsforthenext-generationarchitecture.14 +//__Missing properties overview__// 15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 19 19 17 +ADD FIGURE 18 + 19 +//__Broker queue metrics dashboards__// 20 +It is now possible to select the MQTT broker in the queue metrics dashboards. 21 + 20 20 == **Bug Fixes** == 21 21 22 -//__ Errors withlong stacktracesor longmessage historieswill now also show in eMagiz__//23 - Wehavefixedabugthatcould causean errormessageto belostbetweenthe flowand theManagephase ofeMagiz. This happenedin situationswhere either thestacktrace or themessagehistorywas verylong.To ensure thisnew functionality is appliedtoyourflows,createa newreleaseanddeployitto yourenvironment(s).24 +//__Deployment execution error message__// 25 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup. 24 24 25 -//__ Moving runtimes fromon-premiseto thecloudwillnot resultin a broken container anymore__//26 - We have fixeda bug that caused specificruntimestodeployon-premises butlatermigratedto thecloud,nottostartup. By fixing this bug,youhavemore flexibility in movingcontainers aroundwhenrunningin ahybridconfiguration.27 +//__Cloud template upgrade unjust rollback__// 28 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 27 27 28 28 == **Fancy Forum Answers** == 29 29 30 30 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: 31 31 32 -* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]] 33 -* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]] 34 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 35 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 36 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 37 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 38 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 34 34 40 + 35 35 == **Key takeaways** == 36 36 37 37 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: ... ... @@ -38,7 +38,7 @@ 38 38 39 39 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 40 40 * If you have feedback or ideas for us, talk to the Platypus 41 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 47 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 42 42 * Clear your browser cache (Ctrl + Shift + Del) 43 43 * Check out the release notes [here] 44 44 * Start thinking about how the license tracker can aid your development ... ... @@ -52,5 +52,11 @@ 52 52 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 53 53 54 54 ~*~* Indicates a next-generation-architecture only feature. 55 -{{/info}})))((({{toc/}}))){{/container}} 61 +{{/info}} 62 +))) 63 + 64 +((( 65 +{{toc/}} 66 +))) 56 56 {{/container}} 68 +{{/container}}