Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 130.1
edited by Erik Bakker
on 2023/07/17 15:13
on 2023/07/17 15:13
Change comment:
There is no comment for this version
To version 371.1
edited by Carlijn Kokkeler
on 2024/01/31 12:09
on 2024/01/31 12:09
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 -2 01 -Be Informed1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,73 +1,92 @@ 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 th elastfewweeks,wehaveworkedhard onplanningthe upcomingQandfinishingup features of theprevious Q. More onthatlater.On topofthat, we haveseveralsmaller items asa resultofourhackathoneffortsto presenttoyou.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done. 6 6 7 -== **Announcement - Release Properties** == 8 -As of the next release (202), we will introduce a 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 get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 +== **Pop-up Improvements** == 9 9 10 - == ** Deploy Architecture - ApplyTo Environment improvements** ==11 - Asofthisrelease,we willshowyoualistofall changesabout to be changedonce youpress "Apply toheenvironment" in DeployArchitecture.Thiswill makeitclearer forusers,especially thoseworking inteams,what willchangewhenpressingthis button.10 +//__Property releases__// 11 +When a new property release is created, this property release can now not only be viewed but also release properties can be deleted. 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-blog-213-joyful-journeys-property-release.png]] 14 14 15 - == ** BreadcrumbnavigationineMagiz ** ==16 - Thisreleaseintroducesthe"breadcrumb"navigationincertain partsofeMagiz.Thiswillmostly benoticedandimpacttheCreate phasewhen you check out yourtransformationor systemmessageon the flowevel.Apart fromthere,the navigation is implemented consistentlyacrosstheportalfora unifiedlookand feel.15 +//__Runtime deletion__// 16 +When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 18 +//__Wiretap & debug error messages__// 19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 19 19 20 -== **Feedback Items** == 21 +//__Action messages__// 22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 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 of several operations. 24 +== **Formatting & Alignments** == 24 24 25 -//__I mproved layoutof"Edit integration" pop-up for API Gateway integrations__//26 - Currently,thefullpathofyourbackendsystemwill beshownwhenopeningthe"Edit integration"pop-up onyourAPI Gatewayintegration.26 +//__Input fields__// 27 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions. 27 27 28 -//__ Additional help texts onDesign Architecture__//29 - Wehaveimproved thehelptextsinDesignArchitectureconcerningtheEventStreamingtopicstorageoverview.29 +//__UI improvements__// 30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 30 30 31 -//__ Improved AuditTrail onal places__//32 -In severalplacestheportal,we haveimproved theaudittrail tospecifybetterwhochangedwhat atwhichpointin time.32 +//__Component changes reversion__// 33 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed. 33 33 34 -//__ Removedthe erroneous alertmessage mapping when having a passthrough API__//35 -Th is releaseremoveshe erroneousalertpeoplereportedon "errorsinssagemapping"forapassthrough API.35 +//__State generation statistics__// 36 +The state generation graphs will now show the correct number of cache hits and misses. 36 36 37 -== **Bug Fixes** == 38 +//__Queue browser timestamps__// 39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 38 38 39 -//__A voidclickingonother componentswhiledeletinganother__//40 - Toavoidunexpectedbehavior, we now ensurethatnothingcanbeselected onceyousee the"deletion"pop-upwhenyou want toremoveomethingintheflow designer.41 +//__Addition and deletion of internal recipients__// 42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 41 41 42 -//__Improved validation feedback in migrating to the next-generation architecture__// 43 -We have improved the validation feedback when migrating to the next-generation architecture. 44 +== **Feedback Items** == 44 44 45 -//__ Make surethat usercredentials can be viewed with view rights__//46 - Thisreleasemakessurethat theusercredentialsinDeploycanbe consideredwithviewrightsandnotonly when having editrights.46 +//__Update flows__// 47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. This is particularly useful when changing a resouce used across multiple flows such as topic message definitions in event processors. 47 47 48 -//__ Refreshbehaviorwithin the deploymentplan isfixed__//49 -Th is releasechangestherefresh behaviorwithinthedeploymentplanto show,oncemore,the"tobeinstalled"flowsbeforetheuserpresses Execute.49 +//__Q&A forum search__// 50 +The option to search by pressing the Enter key has been added to the Q&A forum. 50 50 52 +//__Memory settings__// 53 +It is now possible to change the memory settings of a newly added container before pressing "Apply to environment". 54 +//__Runtime validation__// 55 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 56 + 57 +//__Runtime overview image versions__// 58 +Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 59 + 60 +== **Bug Fixes** == 61 + 62 +//__Removal of onramp__// 63 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 64 + 65 +//__Runtime statistics details__// 66 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 67 + 68 +//__Deployment prechecks__// 69 +During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture. 70 + 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 -* [[ ReplacingLegacyeMagiz-MendixConnector:Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]56 -* [[ Unknown character(s)doesnotcreateerrormessage.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]57 -* [[ SplitwayconfigurationforlocalGEN3gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]75 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 76 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 77 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 58 58 59 -== **Key takeaways** ==79 +== **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:81 +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. 85 +* 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 67 * Check out the release notes [here] 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}} 97 +{{/info}} 98 +))) 99 + 100 +((( 101 +{{toc/}} 102 +))) 80 80 {{/container}} 104 +{{/container}}