Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 518.1
edited by Carlijn Kokkeler
on 2024/05/08 08:55
on 2024/05/08 08:55
Change comment:
There is no comment for this version
To version 528.1
edited by Carlijn Kokkeler
on 2024/05/21 11:57
on 2024/05/21 11:57
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 0-PatchParade1 +221 - Swift Shift - Content
-
... ... @@ -3,82 +3,53 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In thelast fewweeks,weworkedhardonveralfeedbackitemsandbugfixes.Ontopofthat, we have releaseda new[[runtimeimage>>doc:Main.ReleaseInformation.Runtime Images.V306.WebHome||target="blank"]]thatensuresthatKafkaoutboundchanneladapterscan nowalso parsejms_destinationandjms_replyToheaders.Withoutfurther ado,let uslook at ourimprovementsnd bugfixesbelow.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. 7 7 8 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. 9 9 10 -//__ Integrationpatterninformation__//11 - Integrationpatterninformationoftheselectedmessagetype hasbeenaddedtothe pop-upthatis showninCapturewhen creating a newintegration.12 +//__Event catalog__// 13 +For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-22 0-integration-pattern.png]]15 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]] 14 14 15 -//__Message queue history__// 16 -All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase. 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. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-22 0-manage-history.png]]23 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]] 19 19 20 -//__Search boxes__// 21 -Search boxes in the properties overview are now shown by default. 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 -[[image:Main.Images.Release Blog.WebHome@release-22 0-search-boxes.png]]30 +[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]] 24 24 25 -//__Set as mapped__// 26 -It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 32 +[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]] 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 29 - 30 -//__SSL settings__// 31 -Changes can now be deployed on SSL level without creating a new version of a flow in Create. 32 - 33 -//__Machine deletion__// 34 -When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. 35 - 36 -[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 37 - 38 38 == **Bug Fixes** == 39 -//__ Annotation styling__//40 - Itisnowpossibletouseentersin Annotations,so thatmultiplelinespacescan be added,ensuringbetterreadability.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. 41 41 42 -[[image:Main.Images.Release Blog.WebHome@release-22 0-edit-annotation.png]]38 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 43 43 44 -//__ Filterrejectionwarnings__//45 - Adiscard channelis requiredforfiltercomponentswhen“Throwexceptiononrejection”value issetto false.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. 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 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. 48 48 49 -//__Manage Explore__// 50 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 51 - 52 -//__Page refreshing__// 53 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 54 - 55 -//__JMS header handling__// 56 -Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. 57 - 58 -//__Message redelivery__// 59 -An issue has been fixed where large messages would be shown at the bottom of the Redelivery page instead of the right side of the page. 60 - 61 -//__Deployment plan__// 62 -We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps. 63 - 64 -//__Overview pages__// 65 -We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. 66 - 67 -//__Memory check__// 68 -Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines. 69 - 70 -//__Copy password__// 71 -The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. 72 - 73 -//__Gateway infra flows__// 74 -We fixed the incorrect generation of gateway infra flows for models using the OAuth 2.0 security scheme in Spring 6. 75 - 76 76 == **Fancy Forum Answers** == 77 77 78 78 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: 79 79 80 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 81 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||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"]] 82 82 83 83 == **Key Takeaways** == 84 84