Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
on 2023/06/08 08:11
Change comment:
There is no comment for this version
To version 528.1
edited by CarlijnKokkeler
on 2024/05/21 11:57
on 2024/05/21 11:57
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 -1 99-HomeImprovements1 +221 - Swift Shift - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,57 +1,67 @@ 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 lastfew weeks, we haveworkedhardonimprovingvarious aspectsofourhome.Amongothers we have improved the logging,alerting,andsecurityofournext-generationarchitecture.Ontopof thatwe have improvedthe innerworkings ofthestore andthecertificatemanagementforthoseofususingtheEventStreaming pattern.6 +**Hi there, eMagiz developers!** This release, we have done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users. It is now also possible to use the back button on the eMagiz Q&A without your search being removed. Regarding bug fixes, the delete behaviour for containers has been improved, and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty. 6 6 7 -== **Next generation improvements and bug fixes** == 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. 8 8 9 -//__E nhanced overview oftheHTTP Statistics__//10 - Asof now allresourcesthathave been called atleastoncesincedeployingthemwill nowshow upinthe left-bottom graph of the HTTP Statistics. This will make iteasier to see whether aparticularoperation was calledwithin a timeframe.Ontopof thatit makes comparingdataonvarious operationseasier.In here you can also filter on one (bypressingthe + icon) ormore byclickingonthefiltericon. In caseyouwanttosortthetablein a differentmanner you can click on the name ofthe column on which you want to sort.12 +//__Event catalog__// 13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 11 11 12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]] 14 14 15 -{{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}} 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. 16 16 17 -//__Forced congestion control__// 18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]] 19 19 20 -//__Unused images are cleaned up__// 21 -This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan. 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". 22 22 23 - == **StoreImprovements** ==30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]] 24 24 25 -//__Improved importing behavior for specific use cases__// 26 -Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users. 32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]] 27 27 28 -//__Fixed bug in creating a message mapping on top of an imported system message__// 29 -It is now possbile to create a message mapping to an imported system message from the store. 34 +== **Bug Fixes** == 35 +//__XSD import__// 36 +When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. 30 30 31 - == **Event Streaming- CertificateManagement** ==38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 32 32 33 -//__ Expired certificationnotification__//34 - As of now wehavefunctionality in placethat will inform you(and us) when a client certificateofanEventStreaming userisgoingto expire within theupcomingthree months. This way you can take actionearlyon and reportback thattheupdatewas succesfullsowecan revoke the expiring clientcertificate accordingly.Ifyouwantspecificinformationonthis pleasereach out to usat[[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].40 +//__Container deletion__// 41 +The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows. 35 35 43 +//__Scope properties__// 44 +We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme. 45 + 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 41 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 50 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]] 51 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]] 52 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]] 42 42 43 -== **Key takeaways** ==54 +== **Key Takeaways** == 44 44 45 -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:56 +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: 46 46 47 47 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 48 48 * If you have feedback or ideas for us, talk to the Platypus 49 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 60 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 50 * Clear your browser cache (Ctrl + Shift + Del) 51 -* Check out the release notes [here] 62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]] 52 52 * Start thinking about how the license tracker can aid your development 53 53 * Start thinking about major, minor, and patch 54 -* Upgrade to the latest build number 55 55 * Keep making great integrations 56 56 57 57 Let's stay in touch and till next time! ... ... @@ -59,6 +59,11 @@ 59 59 {{info}} 60 60 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 62 -~*~* Indicates a GEN3-only feature. 63 -{{/info}})))((({{toc/}}))){{/container}} 72 +{{/info}} 73 +))) 74 + 75 +((( 76 +{{toc/}} 77 +))) 64 64 {{/container}} 79 +{{/container}}