Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 361.1
edited by Carlijn Kokkeler
on 2024/01/29 14:48
on 2024/01/29 14:48
Change comment:
There is no comment for this version
To version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
on 2023/08/29 10:57
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 13-Joyful Journeys1 +204 - Found It - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,94 +1,49 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This release ....5 +**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack. 7 7 8 -== **Pop-up Improvements** == 9 -//__Property releases__// 10 -When a new property release is created, this property release can now be viewed and deleted. 11 - 12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 13 - 14 -//__Runtime deletion__// 15 -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 - 17 -//__Wiretap & debug error messages__// 18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 19 - 20 -//__Action messages__// 21 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 22 - 23 -== **Formatting & Alignments** == 24 - 25 -//__Input fields__// 26 -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 - 28 -//__UI improvements__// 29 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 30 - 31 -//__Runtime overview image versions__// 32 -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. 33 - 34 -//__Component changes reversion__// 35 -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. 36 - 37 -//__State generation statistics__// 38 -The state generation graphs will now show the correct number of cache hits and misses. 39 - 40 -//__Queue browser timestamps__// 41 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 42 - 43 -//__Addition and deletion of internal recipients__// 44 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 45 - 46 46 == **Feedback Items** == 47 47 48 -//__ Updateflows__//49 - InCreate>Resources,abutton"Update flows"has beenadded toupdateversions ofall flows inwhich asource isused.9 +//__Improved check on nested property placeholders__// 10 +To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing. 50 50 51 -//__ Q&Aforumsearch__//52 - The optionto searchbypressing theEnter keyhas beenaddedto theQ&Aforum.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 in order to connect to a Kafka cluster but have become obsolete once you migrate. 53 53 54 -//__Memory settings__// 55 -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. 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}} 56 56 57 -//__ Runtimevalidation__//58 - Validation for runtimesthat are moved fromonpremisesto thecloud orviceversa hasbeen improved.17 +//__Improved performance Manage Dashboards__// 18 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture. 59 59 60 - 61 61 == **Bug Fixes** == 62 62 63 -//__ Removal ofonramp__//64 -We fixed an issue whereit wasnot possible toremovethelastnramplinkedtottedentry(that was anall-entrybefore).22 +//__Errors with long stack traces or long message histories will now also show in eMagiz__// 23 +We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s). 65 65 66 -//__ Runtime statisticsdetails__//67 -We fixed a nissuewhereheapmemoryusagedatawasaccumulatingwhenzooming outthe runtimestatisticsdetailsdashboards.25 +//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__// 26 +We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration. 68 68 69 -//__Deployment prechecks__// 70 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 71 - 72 - 73 73 == **Fancy Forum Answers** == 74 74 75 75 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: 76 76 77 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 78 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 79 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 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"]] 80 80 81 -== **Key Takeaways** ==35 +== **Key takeaways** == 82 82 83 83 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: 84 84 85 85 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 * If you have feedback or ideas for us, talk to the Platypus 87 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 88 88 * Clear your browser cache (Ctrl + Shift + Del) 89 89 * Check out the release notes [here] 90 90 * Start thinking about how the license tracker can aid your development 91 91 * Start thinking about major, minor, and patch 46 +* Upgrade to the latest build number 92 92 * Keep making great integrations 93 93 94 94 Let's stay in touch and till next time! ... ... @@ -96,11 +96,6 @@ 96 96 {{info}} 97 97 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 98 98 99 -{{/info}} 100 -))) 101 - 102 -((( 103 -{{toc/}} 104 -))) 54 +~*~* Indicates a next-generation-architecture only feature. 55 +{{/info}})))((({{toc/}}))){{/container}} 105 105 {{/container}} 106 -{{/container}}