Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 117.1
edited by Erik Bakker
on 2023/05/22 14:03
on 2023/05/22 14:03
Change comment:
There is no comment for this version
To version 574.24
edited by dfirdausy
on 2024/07/01 15:50
on 2024/07/01 15:50
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 - 198-Great Migration1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -1,60 +1,63 @@ 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!** Inthelastfewweeks, wehave workedhardon improving themigrationtowardsournext-generation architectureaswell as improvedthegeneralbehaviorwhenrunningonthenext-generationarchitecture.Furthermore,several improvementshavebeenmade toourowninfrastructuretoensurethat alldataflowingviathis infrastructurenowmore andmorecustomersaremigratingcanbehandled as good if notbetteras before.6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor. 6 6 7 -== **3rd generation improvements and bug fixes** == 8 +== **Feedback Items** == 9 +//__Retention duration and bytes in Capture__// 10 +The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes. 8 8 9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__// 10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e karaf based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release that behavior is changed. 12 +//__Help text panel in Capture__// 13 +Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane. 14 + 15 +//__Property value page__// 16 +Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page. 11 11 12 - {{info}}Note that this fix is part of a new runtime imagefor the karaf based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.CrashCourse.Crash CoursePlatform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}18 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 13 13 14 -//__ RemovedcertaindependenciesbetweenDeploy Architectureand Releases__//15 - Inthis release, we have removed severalspecific dependencies that causedconfusionbetweenthefunctionalityin the DeployArchitecture overview compared to the functionalitythat islinkedtoarelease and specificallythedeploymentof arelease.20 +//__Improved text in Design architecture__// 21 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 16 16 17 -//__Improved validation errors on invalid configuration of HTTP outbound components__// 18 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup. 23 +== **Bug Fixes** == 24 +//__Adding tags in Capture__// 25 +In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon. 19 19 20 -//__Improved migration behavior__// 21 -This release introduces several improvements with regards to the migration behavior via "Transfer settings from Design". Among these are a smoother migration of your JMS (and backup JMS) process, additional feedback given to the user and feedback when the migration process is finished. 27 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 22 22 23 -//__ Improved auto-healing whenrunning inahybrid situation__//24 - In situationswhere you runina hybridsituation(i.e., partly next-genand partlythecurrentgeneration),we haveimprovedtheauto-healingfunctionalityin casean"outofmemory"appears ona runtimerunninginthecurrentgenerationbutonanext-generationarchitecture.29 +//__External links__// 30 +Clicking links to external documentation in the eMagiz portal is now configured to always open the links in a new tab, rather than replacing your current tab. 25 25 26 -//__ Improvedrollup andstorageof metricswhen running yoursolutionin thenextgenerationarchticture__//27 - Toimprovethe stabilityoftheManage phase and,inparticular,themetricswhenzoomingoutontheprovidedinformation,wehavemadesomestructuralchangesthatsupportthisuserfunctionalitybetter.32 +//__Adding attributes for a message definition__// 33 +We fixed an issue where your selected attributes were lost when navigating between paginations while adding more attributes to the entity in the pop-up shown when you press the 'Add Attribute' button on the right panel of your System Message, CDM, API Data Model, or Event Streaming Data Model. 28 28 29 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}} 35 +//__View XSLT__// 36 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 30 30 31 -== **Feedback items ** == 38 +//__Multipart/form-data HTTP request__// 39 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available. 32 32 33 -//__Make sure the message format can be viewed without "Start editing"__// 34 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode. 35 - 36 -//__Various styling improvements in the flow testing functionality__// 37 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details. 38 - 39 39 == **Fancy Forum Answers** == 40 40 41 41 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: 42 42 43 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]] 44 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]] 45 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 46 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 47 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 48 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 45 45 46 -== **Key takeaways** ==50 +== **Key Takeaways** == 47 47 48 -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:52 +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: 49 49 50 50 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 51 51 * If you have feedback or ideas for us, talk to the Platypus 52 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 56 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 53 53 * Clear your browser cache (Ctrl + Shift + Del) 54 -* Check out the release notes [here] 58 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 55 55 * Start thinking about how the license tracker can aid your development 56 56 * Start thinking about major, minor, and patch 57 -* Upgrade to the latest build number 58 58 * Keep making great integrations 59 59 60 60 Let's stay in touch and till next time! ... ... @@ -62,6 +62,11 @@ 62 62 {{info}} 63 63 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 65 -~*~* Indicates a GEN3-only feature. 66 -{{/info}})))((({{toc/}}))){{/container}} 68 +{{/info}} 69 +))) 70 + 71 +((( 72 +{{toc/}} 73 +))) 67 67 {{/container}} 75 +{{/container}}