Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.37
edited by dfirdausy
on 2024/07/02 11:39
on 2024/07/02 11:39
Change comment:
There is no comment for this version
To version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
on 2023/05/22 15:07
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 - 224-SummerSonata1 +198 - Great Migration - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,86 +1,53 @@ 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!** Overthepast week, wefocused on improving theusability of ourplatform andaddressingcommunity feedback.Specifically, weenhanceduserinterface elementson severalpages, includingthe descriptionsofhelptexts,external links within helptexts,andtheoverall layout of helptext pages. Additionally,we madeimprovementsto severalpop-up pages. Wealsomade theuser interfacemoreuser-friendlyfor debugging integration flows.Lastly,weresolvedanissue for somemodelswhencreating anEventProcessor.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before. 7 7 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. 7 +== **3rd generation improvements and bug fixes** == 11 11 12 -//__ Help textpanelinCapture__//13 - Collapsingthehelp textof thispop-uppagebyclickingthe"?"icon onthe toprightcornerofthepop-uppage willnowcorrectlyhidethehelptextpane.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. 14 14 15 -//__Adding tags in Capture__// 16 -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. 12 +{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}} 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 19 - 20 -//__Property value page__// 21 -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. 14 +//__Improved efficiency in deploying a release__// 15 +This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture. 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 17 +//__Removed specific dependencies between Deploy Architecture and Releases__// 18 +In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release. 24 24 25 -//__Improved t extinDesign architecture__//26 - We fixedsomespellingmistakesin thepop-up pagewhen applyingto environmentinDesign architecture.20 +//__Improved validation errors on the invalid configuration of HTTP outbound components__// 21 +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. 27 27 28 -//__Adding attributes for a message definition__// 29 -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. 23 +//__Improved migration behavior__// 24 +This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 25 +A smoother migration of your JMS (and backup JMS) process. 26 +Shortening of names that otherwise would be too long, additional feedback given to the user. 27 +Feedback when the migration process is finished. 30 30 31 -//__ Helptext forHTTP methods__//32 - We improved the helptextfortheHTTP methodfieldintheHTTP outboundgateway andHTTPoutboundchanneladapterflowcomponents toprovideclearerdescriptionsfordifferentHTTP methods.Additionally,we implementeda validationfor thesecomponentstoprevent selectingtheHTTP method'PATCH'ifanApacheHttpComponentsREST templateisnotprovided.29 +//__Additional checks when deploying__// 30 +This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other. 33 33 34 -//__External links__// 35 -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. 36 - 37 -//__Enumeration values__// 38 -When editing a message definition (i.e., a System Message, CDM, API Data Model, or Event Streaming Data Model) in the Create phase, users can add enumeration values for attributes with an Enumeration data type. In this release, we’ve added a "Save and Add New" button to streamline the process of adding multiple enumeration values. 39 - 40 -//__Debugging Shortcut__// 41 -Debugging a flow typically requires users to activate debug on a specific flow in Deploy → Containers, then navigate to Manage → Explore → Queue Browser and manually type in emagiz.debug. In this release, we have added a shortcut button that opens the Queue Browser page directly in the pop-up page right after activating debugging. Next to that, the Queue Browser page now includes a button to directly open the debugging queue, eliminating the need to manually type in emagiz.debug in the search box. 42 - 43 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 44 - 45 -[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] 46 - 47 -//__Test Message from Manage-Explore__// 48 -Additionally, we have improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section. 49 - 50 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 51 - 52 -//__Password property__// 53 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 54 - 55 -== **Bug Fixes** == 56 - 57 -//__Event Processor Keystore and Trustore__// 58 - 59 -We fixed an issue where the keystore location and the truststore location were generated incorrectly when creating a new event processor for models that were migrated from the legacy runtime architecture to the current generation architecture. 60 - 61 - 62 - 63 - 64 64 == **Fancy Forum Answers** == 65 65 66 66 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: 67 67 68 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 69 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 70 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 71 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 36 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 37 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 72 72 73 -== **Key Takeaways** ==39 +== **Key takeaways** == 74 74 75 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:41 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 76 76 77 77 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 * If you have feedback or ideas for us, talk to the Platypus 79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 45 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 80 * Clear your browser cache (Ctrl + Shift + Del) 81 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]47 +* Check out the release notes [here] 82 82 * Start thinking about how the license tracker can aid your development 83 83 * Start thinking about major, minor, and patch 50 +* Upgrade to the latest build number 84 84 * Keep making great integrations 85 85 86 86 Let's stay in touch and till next time! ... ... @@ -88,11 +88,6 @@ 88 88 {{info}} 89 89 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 90 90 91 -{{/info}} 92 -))) 93 - 94 -((( 95 -{{toc/}} 96 -))) 58 +~*~* Indicates a GEN3-only feature. 59 +{{/info}})))((({{toc/}}))){{/container}} 97 97 {{/container}} 98 -{{/container}}