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 +210 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,76 +3,59 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release, we a rebringing asignificantperformanceimprovement toflowtesting,with executiontimes now accelerated by upto3 times. Next to that, overthe past week, wefocusedonimproving theusabilityof our platformand addressingcommunity feedback.Specifically,we enhanceduserinterfaceelementsonseveralpages,includingthedescriptions of helptexts, externallinks withinhelptexts,andtheoverall layoutof helptextpages. Additionally, we madeimprovementsto several pop-up pages.We alsomadetheuser interfacemore user-friendlyfor debugging integrationflows.Lastly,we resolved an issue for some models whencreating an Event Processor.6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving. 7 7 8 -== ** Faster Flow Testing** ==8 +== **Alerts** == 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. 10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives. 11 11 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 15 + 12 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. 15 15 16 -//__ Helptext panelinCapture__//17 - Collapsingthe helptextofthispop-uppage by clicking the"?"iconon the toprightcornerofthepop-uppage willnowcorrectly hidethehelptextpane.18 +//__Container version overview__// 19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. By having this overview, you can check which versions of the containers that exist in Deploy Architecture are in the release. 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 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 23 +//__Unchanged containers__// 24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. This decreases the deployment time and improves the performance. 23 23 24 -//__ Addingattributes foramessagedefinition__//25 - We fixedanissuewhereyour selected attributeswerelostwhen navigatingbetween paginationswhile addingmore attributestotheentity inthepop-up shownwhenyoupressthe'Add Attribute'button on the rightpanelofyour SystemMessage, CDM, API Data Model, or Event Streaming Data Model.26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 26 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. 29 - 30 -//__Property value page__// 31 -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. 29 +== **Bug Fixes** == 32 32 33 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 31 +//__Runtime metrics processing__// 32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 34 34 35 -//__ Passwordproperty__//36 - In theFlow designerwithin theCreatephase,copyingpassword propertiesnowcopiestheactual password valueinsteadof the encodedvalue.34 +//__Deployment plan__// 35 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 37 37 38 -//__ Enumerationvalues__//39 - Whenediting a messagedefinition (i.e.,aSystemMessage,CDM, API Data Model,or Event StreamingData Model)intheFlowdesignerwithintheCreatephase, userscanaddenumeration valuesforattributeswith anEnumeration data type. In this release,we’veadded a "Save and Add New"button tostreamlinethe processofaddingmultiple enumeration values.37 +//__View all store items__// 38 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 40 40 41 -//__ HelptextforHTTP methods__//42 -We improved the help text fortheHTTP methodfieldin theHTTPoutbound gatewayand HTTP outbound channel adapter flow components to provide clearerdescriptionsfordifferentHTTPmethods.Additionally, we implementedavalidationforthese componentstopreventselectingtheHTTP method 'PATCH' ifan ApacheHttpComponentsREST template is not provided.40 +//__Out of memory behavior__// 41 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 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. 43 +//__Max fetch size__// 44 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior. 49 49 50 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 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 names and descriptions 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 - 62 -== **Bug Fixes** == 63 - 64 -//__Event Processor Keystore and Trustore__// 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 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]] 50 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 51 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 52 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 53 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 54 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 73 73 74 -== **Key Takeaways** == 75 75 57 +== **Key takeaways** == 58 + 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 78 78 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -79,13 +79,19 @@ 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"]]65 +* 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 68 +* 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 88 73 +{{info}} 74 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 + 76 +~*~* Indicates a next-generation-architecture only feature. 77 +{{/info}} 89 89 ))) 90 90 91 91 (((