Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
on 2023/07/17 15:10
Change comment:
There is no comment for this version
To version 505.2
edited by CarlijnKokkeler
on 2024/05/06 13:41
on 2024/05/06 13:41
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 -20 1-BeInformed1 +220 - Patch Parade - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,73 +1,91 @@ 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 last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Announcement - Release Properties** == 8 -As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 +== **Feedback Items** == 9 9 10 - == ** Deploy Architecture- Apply To Environmentimprovements ** ==11 - As ofthis release we will show you a list of all changethatare aboutto bechangedonce you press "Applyto environment"in DeployArchitecture.This willensure thatitbecomesclearerforusers, especiallythoseworkingtogetherin teams,whatwillchange whenpressingthisbutton.10 +//__Integration pattern information__// 11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@ 201-release-blog--apply-to-environment-example.png]]13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 14 14 15 - == ** Breadcrumbnavigation in eMagiz ** ==16 - With this releaseweintroducethe"breadcrumb" navigation in certainpartsofeMagiz.Thiswill mostly benoticed,and have impact,in theCreatephasewhen youare checkingout your transformationorsystem messageon flow level.Apartfrom therethe navigationis implementedconsistentlyacrossthe portalforaunified look and feel.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 17 18 -[[image:Main.Images.Release Blog.WebHome@ 201-release-blog--breadcrumb-navigation-example.png]]18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 19 19 20 -== **Feedback Items** == 20 +//__Search boxes__// 21 +Search boxes in the properties overview are now shown by default. 21 21 22 -//__Improved layout of catalog page in Design__// 23 -We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations. 23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 24 24 25 -//__ Improved layoutof "Edit integration"pop-up for API Gateway integrations__//26 - Asofnowthe fullpathof your backendsystem willbeshownwhenopeningthe"Editintegration" pop-upon yourAPIGatewayintegration.25 +//__Set as mapped__// 26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design. 27 27 28 -//__Additional help texts on Design Architecture__// 29 -We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview. 28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 30 30 31 -//__ ImprovedAuditTrail onseveral places__//32 - Inseveralplacesinthe portalwehave improvedthe audittrailtobetterspecify whochangedwhatatwhichpointintime.30 +//__SSL settings__// 31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create. 33 33 34 -//__ Removed the erroneousalerton message mapping when having a passthrough API__//35 - Thisreleaseremovestheerroneousalertpeoplereportedon"errorsinmessagemapping"forapassthrough API.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. 36 36 36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 37 + 38 +//__JMS header handling__// 39 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released. 40 + 37 37 == **Bug Fixes** == 42 +//__Annotation styling__// 43 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 38 38 39 -//__Avoid clicking on other components while deleting another__// 40 -To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 41 41 42 -//__ Improved validation feedback in migratingto thenext-generation architecture__//43 - Wehaveimprovedseveralthingswithregardsto thevalidationfeedbackwhenmigratingtothenext-generation architecture.47 +//__Filter rejection warnings__// 48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 44 44 45 -//__Make sure that user credentials can be viewed with view rights__// 46 -This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights. 50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 47 47 48 -//__ Refresh behavior withinthedeployment plan is fixed__//49 - Thisreleasechangestherefreshbehavior within thedeploymentplanto show, oncemore,the "to beinstalled" flowsbeforetheuserpressesExecute.52 +//__Manage Explore__// 53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 50 50 55 +//__Page refreshing__// 56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 57 + 58 +//__Message redelivery__// 59 +An issue has been fixed where large messages would be shown at the bottom of the 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 + 51 51 == **Fancy Forum Answers** == 52 52 53 53 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: 54 54 55 -* [[ Replacing LegacyeMagiz-MendixConnector:MigrationPlan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]56 -* [[ Unknown character(s)does notcreate errormessage.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]57 -* [[ Split gateway configurationforlocalGEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]74 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 75 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 76 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 58 58 59 -== **Key takeaways** ==78 +== **Key Takeaways** == 60 60 61 -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:80 +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: 62 62 63 63 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 * If you have feedback or ideas for us, talk to the Platypus 65 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 84 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 66 * Clear your browser cache (Ctrl + Shift + Del) 67 -* Check out the release notes [here] 86 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 68 68 * Start thinking about how the license tracker can aid your development 69 69 * Start thinking about major, minor, and patch 70 -* Upgrade to the latest build number 71 71 * Keep making great integrations 72 72 73 73 Let's stay in touch and till next time! ... ... @@ -75,6 +75,11 @@ 75 75 {{info}} 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 -~*~* Indicates a GEN3-only feature. 79 -{{/info}})))((({{toc/}}))){{/container}} 96 +{{/info}} 97 +))) 98 + 99 +((( 100 +{{toc/}} 101 +))) 80 80 {{/container}} 103 +{{/container}}