Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 85-To determine1 +221 - Swift Shift - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. eMagiz1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,54 +1,74 @@ 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 been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.6 +**Hi there, eMagiz developers!** 6 6 7 -==**Audit trail User Management**== 8 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section. 9 - 10 -[[image:Main.Images.Release Blog.WebHome@185 - Releaseblog 1.png]] 8 +== **Feedback Items** == 9 +//__Q&A search__// 10 +Search results are now persisted when pressing the back button after opening a question in the community Q & A. 11 11 12 -==**Next Generation Monitoring & Alerting engine**== 13 -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"]] 14 - 15 -=== **Improvements** === 16 - 17 -* Performance Deployment plan 18 -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. 19 - 20 -* Flow Designer updates 21 -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. 22 - 23 -[[image:Main.Images.Release Blog.WebHome@185 - Releaseblog 2.png]] 24 - 12 +//__Event catalog__// 13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 14 + 15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]] 16 + 17 +//__Attribute placements__// 18 +Some improvements regarding the placement of attributes have been done: 19 +* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add new attribute. 20 +* Moving an attribute in the datamodel is now directly shown in the tree structure as well. 21 +* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. 22 + 23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]] 24 + 25 +//__Failover & grouping__// 26 +Some improvements regarding the widgets for failover and grouping have been done: 27 +* When executing a start/stop action on a group, the description of the step now contains the name of the group. 28 +* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 29 + 30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]] 31 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]] 32 + 33 +== **Bug Fixes** == 34 +//__XSD import__// 35 +When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. 36 + 37 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 38 + 39 +//__XSD import__// 40 +The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows. 41 + 25 25 == **Fancy Forum Answers** == 26 26 27 -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:44 +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: 28 28 29 -* [[S tartruntimeviaa delayed startina Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]30 -* [[ FailedtocreatesFTPsession: Hetsysteemkan het opgegeven pad nietvinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]46 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 47 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]] 31 31 32 -== **Key takeaways** ==49 +== **Key Takeaways** == 33 33 34 -Thanks to all thathelp build,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:51 +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: 35 35 36 36 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 37 37 * If you have feedback or ideas for us, talk to the Platypus 38 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 55 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 39 39 * Clear your browser cache (Ctrl + Shift + Del) 40 -* Check out the release notes [here] 57 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]] 41 41 * Start thinking about how the license tracker can aid your development 42 42 * Start thinking about major, minor, and patch 43 -* Upgrade to the latest build number 44 44 * Keep making great integrations 45 -* Check out the new documentation portal. 46 46 47 47 Let's stay in touch and till next time! 48 48 49 49 {{info}} 50 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 51 51 52 -~*~* Indicates a GEN3-only feature. 53 -{{/info}})))((({{toc/}}))){{/container}} 67 +{{/info}} 68 +))) 69 + 70 +((( 71 +{{toc/}} 72 +))) 54 54 {{/container}} 74 +{{/container}}