Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 2.1
edited by eMagiz
on 2022/10/12 10:50
on 2022/10/12 10:50
Change comment:
There is no comment for this version
To version 144.1
edited by Erik Bakker
on 2023/08/15 10:23
on 2023/08/15 10:23
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 - 185-Todetermine1 +203 - Fast Paced - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Content
-
... ... @@ -2,48 +2,36 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavebeen hard at workbolstering our offeringconcerningtheupcomingrollout of our new architecture stack. Nextto that, wehavemade severalsmall updatesasthisreleasecontainedacompleterevampof the Managephase.Please take amoment to read thebelowcarefullyandworkwith the new flow designerassoon aspossibleto familiarize yourselfwith this one.5 +**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items. 6 6 7 -==**Audit trail User Management**== 7 +== **Release Properties - Early Feedback** == 8 +The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties. 8 8 9 - 10 -==**Next Generation Monitoring & Alerting engine**== 11 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations. In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach). We have already released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]] 12 - 13 -=== **Improvements** === 14 - 15 -* Performance Deployment plan 16 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release. 17 - 18 -* Flow Designer updates 19 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made. 20 - 21 - 22 - 23 - 24 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 10 +== **Feedback Items** == 25 25 26 - 27 - ==**Feedbackitems**==12 +//__"All entries" are now cleaned up as part of the migration__// 13 +To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture. 28 28 29 -We have also solved other feedback items besides the key updates around functionality. 15 +//__Trigger ID added to our alerting on the next-generation architecture__// 16 +We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable. 30 30 31 -//__Set runtime field as first selected field on property level__// 32 -With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well. 18 +== **Bug Fixes** == 33 33 34 - [[image:Main.Images.ReleaseBlog.WebHome@184- FlowDesignerreleaseblog3.png]]35 - 20 +//__Ensure no flow can be in a release twice__// 21 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this. 36 36 23 +//__Ensure no flow can be in a release twice__// 24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this. 25 + 37 37 == **Fancy Forum Answers** == 38 38 39 -As always, a gentle reminder to a ll 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:28 +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: 40 40 41 -* [[Start runtime via a delayed start in a Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]] 42 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]] 30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 43 43 44 44 == **Key takeaways** == 45 45 46 -Thanks to all that help build ,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:34 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 47 47 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 49 * If you have feedback or ideas for us, talk to the Platypus ... ... @@ -54,13 +54,12 @@ 54 54 * Start thinking about major, minor, and patch 55 55 * Upgrade to the latest build number 56 56 * Keep making great integrations 57 -* Check out the new documentation portal. 58 58 59 59 Let's stay in touch and till next time! 60 60 61 61 {{info}} 62 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 63 63 64 -~*~* Indicates a GEN3-only feature.51 +~*~* Indicates a next-generation-architecture only feature. 65 65 {{/info}})))((({{toc/}}))){{/container}} 66 66 {{/container}}