Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 24- Summer Sonata1 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,77 +1,54 @@ 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!** In th is release, we are bringing a significantperformanceimprovement to flowtesting,withexecution timesnowacceleratedby up to 3 times. Next to that,overthepastweek,wefocused on improvingtheusabilityof ourplatform and addressingcommunityfeedback.Specifically, weenhanceduserinterfaceelementson severalpages, includingthedescriptions of help texts, externallinks within helptexts,andtheoveralllayoutofhelp text pages. Additionally, wemade improvementstoseveralpop-up pages. We alsomadetheuserinterfacemore user-friendlyfordebugging integration flows.Lastly,we resolvedan issuefor some modelswhen creatingan Event Processor.5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you. 7 7 8 -== ** Faster Flow Testing** ==7 +== **Deployment Plan** == 9 9 10 -We are rolling out a major upgrade to flow testing performance, boosting execution speeds by up to three times. This enhancement will greatly accelerate your workflow when developing integrations, enabling you to run tests faster and more efficiently. Consequently, this will further support users for delivering higher-quality integrations. 9 +//__Improved deployment plan to make the process better and more predictable__// 10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 11 11 12 -== **Feedback Items** == 13 -//__Retention duration and bytes in Capture__// 14 -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. 12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 15 15 16 -//__ HelptextpanelinCapture__//17 - Collapsingthehelptextofthispop-up pageby clicking the "?" icon on the topright cornerof thepop-up pagewillnowcorrectlyhidethehelptext pane.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 18 18 19 -//__Adding tags in Capture__// 20 -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. 21 - 22 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 23 - 24 -//__Adding attributes for a message definition__// 25 -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. 26 - 27 -//__Improved text in Design architecture__// 28 -We fixed some spelling mistakes in the steps to be executed within the pop-up page when applying to environment in Design architecture. 18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 20 + 21 +//__Cleanup old images__// 29 29 30 - //__Property value page__//31 - Pop-uppageswith 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.23 +== **Store Improvements** == 24 + 32 32 33 - [[image:Main.Images.ReleaseBlog.WebHome@release-224-pop-ups-wrapped-property-values.png]]26 +== **Feedback Items** == 34 34 35 -//__ Passwordproperty__//36 - IntheFlow designerwithin theCreatephase,copyingpassword properties nowcopies the actualpasswordvalueinsteadof the encodedvalue.28 +//__Alerting manual pause__// 29 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 37 37 38 -//__ Enumerationvalues__//39 - Wheneditingamessagedefinition(i.e., a SystemMessage,CDM, API DataModel,orEvent StreamingData Model)in the Flowdesignerwithin theCreatephase, userscanaddenumeration valuesforattributeswithan Enumerationdatatype. Inthis release, we’ve addeda"SaveandAdd New"buttontostreamline theprocessofadding multipleenumerationvalues.31 +//__Ordering of graphs in Manage__// 32 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 40 40 41 -//__ HelptextforHTTP methods__//42 - Weimprovedthehelptext fortheHTTPmethod fieldin theHTTP outbound gatewayandHTTP outboundchanneladapterflowcomponentsto provideclearerdescriptionsfor different HTTP methods.Additionally,weimplementeda validationfor thesecomponents topreventselectingtheHTTP method'PATCH'if anApacheHttpComponentsRESTtemplateis not provided.34 +//__UTC times in Grafana panels__// 35 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 43 43 44 -//__External links__// 45 -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. 46 - 47 -//__Debugging Shortcut__// 48 -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. 37 +//__Update flow designer version__// 38 +The framework used in the flow designer has been updated to the latest version. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 51 51 52 -{{html}} 53 -<!-- 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. --> 54 -<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] --> 55 -{{/html}} 56 - 57 -//__Test Message from Manage-Explore__// 58 -Additionally, we have improved the name and description of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section. 59 - 60 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 61 - 41 + 62 62 == **Bug Fixes** == 63 63 64 -//__Event Processor Keystore and Trustore__// 65 65 66 -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. 67 - 68 68 == **Fancy Forum Answers** == 69 69 70 70 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: 71 71 72 -* [[ PreparingImage for<runtime>failed: Reached the numberof attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]49 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 73 73 74 -== **Key Takeaways** ==51 +== **Key takeaways** == 75 75 76 76 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: 77 77 ... ... @@ -79,21 +79,17 @@ 79 79 * If you have feedback or ideas for us, talk to the Platypus 80 80 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 81 81 * Clear your browser cache (Ctrl + Shift + Del) 82 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]59 +* Check out the release notes [here] 83 83 * Start thinking about how the license tracker can aid your development 84 84 * Start thinking about major, minor, and patch 62 +* Upgrade to the latest build number 85 85 * Keep making great integrations 86 86 87 87 Let's stay in touch and till next time! 88 - 66 + 89 89 {{info}} 90 90 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 91 91 92 -{{/info}} 93 -))) 94 - 95 -((( 96 -{{toc/}} 97 -))) 70 +~*~* Indicates a next-generation-architecture only feature. 71 +{{/info}})))((({{toc/}}))){{/container}} 98 98 {{/container}} 99 -{{/container}}