Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 149.1
edited by Erik Bakker
on 2023/08/29 10:56
on 2023/08/29 10:56
Change comment:
There is no comment for this version
To version 359.1
edited by Carlijn Kokkeler
on 2024/01/29 14:34
on 2024/01/29 14:34
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 04-FoundIt1 +213 - Joyful Journeys - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,49 +1,89 @@ 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!** Wehave processedadditional feedback on thereleaseproperties in the last few weeks.On top of that, we have improved the error handling and manageability of our new generation monitoring stack.6 +**Hi there, eMagiz developers!** This release .... 6 6 8 + 7 7 == **Feedback Items** == 8 8 9 -//__ Improved check on nestedpropertyplaceholders__//10 - To avoid problems whenusingnestedpropertyplaceholders inyourconfiguration, wehave added additional checks to identifythesenestedproperties asmissingif theyareindeedmissing.11 +//__Property releases__// 12 +When a new property release is created, this property release can now be viewed and deleted. 11 11 12 -//__Removed outdated properties when deploying on the new generation architecture stack__// 13 -We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate. 14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 14 14 15 -{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}} 16 +//__Runtime deletion__// 17 +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 -//__ ImprovedperformanceManage Dashboards__//18 - Wehave improvedthe efficiencyofretrievingthedatashownin the ManageDashboardsforthenext-generation architecture.19 +//__Update flows__// 20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 19 19 22 +//__Input fields__// 23 +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. 24 + 25 +//__Memory settings__// 26 +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. 27 + 28 +//__Runtime validation__// 29 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 30 + 31 +//__UI improvements__// 32 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 33 + 34 +//__Q&A forum search__// 35 +The option to search by pressing the Enter key has been added to the Q&A forum. 36 + 37 +//__Wiretap & debug error messages__// 38 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 39 + 40 +//__Runtime overview image versions__// 41 +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. 42 + 20 20 == **Bug Fixes** == 44 +//__Action messages__// 45 +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 -//__ Errors with long stack traces or longmessage histories will nowalsoshowineMagiz__//23 -We havefixed abug that could cause anerror messageto be lost betweentheflowndtheManagephaseof eMagiz. Thishappened insituations whereeitherthe stack tracerthemessage historywas very long. To ensurethisnewfunctionalityisapplied to yourflows, createa newreleaseanddeploy itto your environment(s).47 +//__Removal of onramp__// 48 +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). 24 24 25 -//__ Moving runtimes from on-premisetothecloud willnot resultin a broken containeranymore__//26 - Wehave fixeda bugthatcausedspecific runtimes todeployon-premises but latermigratedtothecloud, notto start up. By fixingthis bug,youhavemore flexibilityinmovingcontainersaroundwhenrunning inahybrid configuration.50 +//__Component changes reversion__// 51 +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. 27 27 53 +//__State generation statistics__// 54 +The state generation graphs will now show the correct number of cache hits and misses. 55 + 56 +//__Runtime statistics details__// 57 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 58 + 59 +//__Queue browser timestamps__// 60 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 61 + 62 +//__Deployment prechecks__// 63 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 64 + 65 +//__Addition and deletion of internal recipients__// 66 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 67 + 28 28 == **Fancy Forum Answers** == 29 29 30 30 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: 31 31 32 -* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]] 33 -* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]] 72 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 73 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 74 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 34 34 35 -== **Key takeaways** ==76 +== **Key Takeaways** == 36 36 37 37 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: 38 38 39 39 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 40 40 * If you have feedback or ideas for us, talk to the Platypus 41 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 82 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 42 42 * Clear your browser cache (Ctrl + Shift + Del) 43 43 * Check out the release notes [here] 44 44 * Start thinking about how the license tracker can aid your development 45 45 * Start thinking about major, minor, and patch 46 -* Upgrade to the latest build number 47 47 * Keep making great integrations 48 48 49 49 Let's stay in touch and till next time! ... ... @@ -51,6 +51,11 @@ 51 51 {{info}} 52 52 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 53 53 54 -~*~* Indicates a next-generation-architecture only feature. 55 -{{/info}})))((({{toc/}}))){{/container}} 94 +{{/info}} 95 +))) 96 + 97 +((( 98 +{{toc/}} 99 +))) 56 56 {{/container}} 101 +{{/container}}