Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 127.1
edited by Samet Kaya
on 2023/06/20 13:14
on 2023/06/20 13:14
Change comment:
There is no comment for this version
To version 366.1
edited by Carlijn Kokkeler
on 2024/01/29 15:02
on 2024/01/29 15:02
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 00-UnchartedTerritories1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SametKaya1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,66 +1,93 @@ 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 e lastfew weeks,wehaveworked hardona lotofthingsthatareunfortunatelynotquite readyto bereleased. As asulttheoutputofthisreleaseislimited.Havingsaidthat we still bringsomekeyimprovementsin theDeploy andManagephasethatwould makelife mucheasier.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 -== ** Next generationimprovementsand bug fixes** ==8 +== **Pop-up Improvements** == 8 8 9 -//__ Enhancedright-handview within Deployment Plan context__//10 -When executing your deployment planweillshow specific log entriesof the infocategorythatindicatethat a container(i.e.runtime) hasstartedupcorrectly. Ontop of thatweshowthewarnings and errors inthis overview.10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 11 11 12 - {{info}}Note that when the JMS containergetsrestartedconnectionerrors in theogs arenormalthingtowitness so keepyoureseeled forthestartup logging on JMS levelto gain confidence in the deployment.{{/info}}13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 13 13 14 -//__ Improvedtimeoutsettings whendeploying__//15 - To avoid mismatchesbetweenvariouspartsoftheinfrastructurewe haveimprovedthe timeoutconfigurationon certaindeployment planstepstoreduce thechancethatthesemismatchesoccur.15 +//__Runtime deletion__// 16 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 16 16 17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 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. 18 18 19 -//__ Detailed HTTP Statistics now show user info in specific additionalcases__//20 -T o solvea bugforspecificclientwechangedthelogicto show theuserinfo(i.e. firstpartfthe apikey) ina specific implementationjust aswealreadydoinourstandardimplementations.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 - {{info}}Notethat this fix is partof a newruntime image forthe next-generationruntimes.The release notes of this canbefound [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}24 +== **Formatting & Alignments** == 23 23 24 -//__I mproved loading speedofManageDashboard__//25 - This releaseimprovestheloadingspeedwith which allthedashboardsinManage are showntheuser. Thiswillenhance the userexperiencewithintheManage phase.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. 26 26 27 -== **Store Improvements** == 29 +//__UI improvements__// 30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 28 28 29 -//__ Importing inDesignis improved__//30 - Wehavesolved a bugthatcould causeissueswhenimportingsomethinginDesign whiletheaccompanyingintegrationwasnot yet inCreate.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. 31 31 32 -== **Bug Fixes** == 35 +//__State generation statistics__// 36 +The state generation graphs will now show the correct number of cache hits and misses. 33 33 34 -//__ Deprecatedreminderpop-up removed__//35 - Wehave removedareminderpop-uponapendingcloud template asitwas deprecatedand could causeissueswhenusingit incommunicationwithothersystems.38 +//__Queue browser timestamps__// 39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 36 36 37 -//__ ImprovedselectionareainFlowDesigner__//38 - Whenworkingonalargeflowyoucannow selectspecificareaseasilywhileyouarescrolleddownfurther down theflow.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. 39 39 40 -//__Improved Kafka settings__// 41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 44 +== **Feedback Items** == 42 42 43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 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. 44 44 49 +//__Q&A forum search__// 50 +The option to search by pressing the Enter key has been added to the Q&A forum. 51 + 52 +//__Memory settings__// 53 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine. 54 + 55 +//__Runtime validation__// 56 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 57 + 58 +//__Runtime overview image versions__// 59 +Insight into invented 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. 60 + 61 +== **Bug Fixes** == 62 + 63 +//__Removal of onramp__// 64 +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). 65 + 66 +//__Runtime statistics details__// 67 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 68 + 69 +//__Deployment prechecks__// 70 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 71 + 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 76 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 77 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 78 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 51 51 52 -== **Key takeaways** ==80 +== **Key Takeaways** == 53 53 54 -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:82 +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: 55 55 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 86 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 60 * Check out the release notes [here] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 -* Upgrade to the latest build number 64 64 * Keep making great integrations 65 65 66 66 Let's stay in touch and till next time! ... ... @@ -68,6 +68,11 @@ 68 68 {{info}} 69 69 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 71 -~*~* Indicates a GEN3-only feature. 72 -{{/info}})))((({{toc/}}))){{/container}} 98 +{{/info}} 99 +))) 100 + 101 +((( 102 +{{toc/}} 103 +))) 73 73 {{/container}} 105 +{{/container}}