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 11-Log Luminary1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.dfirdausy - Content
-
... ... @@ -3,70 +3,73 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Inthis release, wehavedonemuch work toimprove our logging andoverviews.This should improvetheuserexperienceforour platform.Nexttothis, wehavedone severalminorchanges andbugfixes,mainly relating to theDeployandManagephase.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. 7 7 8 -== **Logging** == 9 -//__Missing log entries__// 10 -We improved crash handling so that log messages clearly show when and why a container failed to start. 8 +== **Rapid Flow Testing** == 11 11 12 -//__Runtime logging__// 13 -We fixed a bug where no new log messages were showing up, even though they were produced by a container. 10 +== **Feedback Items** == 11 +//__Retention duration and bytes in Capture__// 12 +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. 14 14 15 -//__ Deploymentexecutionerror message__//16 - In some cases when a machine typestepin thedeploymentplanexecutionerrors,theportalmaygivean error when trying to display theerrormessage. This has been fixed by now showinga generic error in thedeploymentplanand loggingthefull errorintheDeployhistory. TheDeployhistorywillshowa summaryof theerror and showthefullerrormessage ina new pop-up.14 +//__Help text panel in Capture__// 15 +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. 17 17 18 -== **Overviews** == 17 +//__Adding tags in Capture__// 18 +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 -//__Runtime overview__// 21 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. 20 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 21 + 22 +//__Property value page__// 23 +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. 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release- blog-211-runtime-overview.png]]25 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 24 24 25 -//__ Missingpropertiesoverview__//26 - Themissingpropertiesoverviewhas beenupdatedto showtheruntimesandflowversions ofmissingproperty values.27 +//__Improved text in Design architecture__// 28 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 30 +//__Adding attributes for a message definition__// 31 +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. 29 29 30 -//__ Runtimerestartorredeployoverview__//31 - Before executingthe deploymentplan todeploymachines,apop-up willbe shown witha listof theaffectedruntimes.33 +//__Helptext for HTTP methods__// 34 +We improved the help text for the HTTP method field in the HTTP outbound gateway and HTTP outbound channel adapter flow components to provide clearer descriptions for different HTTP methods. Additionally, we implemented a validation for these components to prevent selecting the HTTP method 'PATCH' if an Apache HttpComponents REST template is not provided. 32 32 33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 36 +//__External links__// 37 +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. 38 + 39 +//__Enumeration values__// 40 +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. 34 34 35 -== **Feedback Items** == 42 +//__Debugging Shortcut__// 43 +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. 36 36 37 -//__Breaking changes pop-up__// 38 -Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 45 +[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 39 39 40 -[[image:Main.Images.Release Blog.WebHome@release- blog-211-breaking-changes.jpg]]47 +[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] 41 41 42 -//__ Externalrecipientsemailaddress__//43 - The overview of externalrecipientshas beenupdated.External recipients arenowcreatedona model level, insteadofcomma separated list.Thismeans that youcan addthemtoyourenvironmentdirectly, likeinternalusers.49 +//__Test Message from Manage-Explore__// 50 +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. 44 44 45 -//__Broker queue metrics dashboards__// 46 -It is now possible to select the MQTT broker in the queue metrics dashboards. 52 +[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 47 47 48 -//__ Runtime imageversion__//49 - Theversionofruntimeimagesusedtoprepareyourcontainersfordeployments willbe thesameacross allenvironments. This holdsforreleasesthat aredeployed and promotedtoanext environment.54 +//__Password property__// 55 +In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 50 50 51 - 52 52 == **Bug Fixes** == 53 53 54 -//__Message throughput__// 55 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases. 59 +//__Event Processor Keystore and Trustore__// 56 56 57 -//__Cloud template upgrade incorrect rollback__// 58 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 61 +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. 59 59 60 -//__Next generation block__// 61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 62 - 63 63 == **Fancy Forum Answers** == 64 64 65 65 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: 66 66 67 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 67 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 68 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 69 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 70 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 68 68 69 -== **Key takeaways** ==72 +== **Key Takeaways** == 70 70 71 71 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: 72 72 ... ... @@ -74,7 +74,7 @@ 74 74 * If you have feedback or ideas for us, talk to the Platypus 75 75 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 76 76 * Clear your browser cache (Ctrl + Shift + Del) 77 -* Check out the release notes [here] 80 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 78 78 * Start thinking about how the license tracker can aid your development 79 79 * Start thinking about major, minor, and patch 80 80 * Keep making great integrations