Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 55.1
edited by Erik Bakker
on 2022/11/24 11:53
on 2022/11/24 11:53
Change comment:
There is no comment for this version
To version 574.33
edited by dfirdausy
on 2024/07/02 10:51
on 2024/07/02 10:51
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 - 188-CloseEncounters1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -1,90 +1,81 @@ 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!** Thisreleaseischaracterizedmainlybyoureffortsto bolster our3rdgeneration runtime and allits interactions.Furthermore,someminor fixes andbetafeatureswillbe releasedtothecommunity.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 runtime bolstering** == 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 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 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. 10 10 11 -//__ Migrationof JMS backupconfiguration improved__//12 - Withthisrelease,theconfigurationoftheJMS backupconfigurationis improved to preventpotentialconnectivityissuesaftermigrating tothe3rdgenerationruntime.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. 13 13 14 -//__Prechecks on Upgrade option made available for 3rd generation runtime__// 15 -As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture. 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. 16 16 17 -//__Autogenerated exits can be deployed at once__// 18 -This release has fixed a bug that prevented you from deploying an exit flow correctly. 23 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 19 19 20 -//__ Codemapping functionalityavailable on3rd generation runtime__//21 - Asofthis release,codemappingfunctionality isalsoavailableforthe3rd generation runtime.This removestherestrictionon migrating tothenew 3rd generationruntimefor our clientsthat usethe code mappingfunctionality.25 +//__Improved text in Design architecture__// 26 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 22 22 23 -//__ Failing runtimeswon'tberestartedindefinitely anymore__//24 -We haveputacap onthisbehaviortopreventyour logsfromexplodingduetoafailingruntimebeing restartedindefinitely. As ofthisrelease,fiveattemptswillbemade to restartafailingruntime.Ifthe runtimecannotstart correctlyafterthese attempts,theruntimewillbe stopped.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. 25 25 26 -== **Exportable Release Audit** ~* == 31 +//__Helptext for HTTP methods__// 32 +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. 27 27 28 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 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. 29 29 30 -[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]] 37 +//__Debugging Shortcut__// 38 +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. 31 31 32 -{{warning}}Note that the following restrictions apply when exporting an audit document: 33 - * Works **only** for releases that are promoted and made active on **Production** 34 - * You will **only** see changes made during the **current** calendar year 35 - * On the first of April all objects of the **last** calendar year will be **removed**. 36 - ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}} 40 +<Screenshot here> 37 37 38 -== **Feedback items ** == 42 +//__Test Message from Manage-Explore__// 43 +We improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section. 39 39 40 - Wehavealsosolved otherfeedback items besides theflow designer's critical updates.45 +<Screenshot here> 41 41 42 -//__ Improved naming convention on Store related pages__//43 - Wehaveimprovedvariousdisplaynamesto ensurethatit is clearfromthe namingthat storecontent canbeimplementedinall integration patterns.47 +//__Password property__// 48 +In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 44 44 45 -//__Press "Enter" to search on multiple pages__// 46 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 50 +== **Bug Fixes** == 47 47 48 -* Deploy → Deployment Plan 49 -* Deploy → Properties → History 50 -* Deploy → User Management → Roles 51 -* Manage → Error Messages → Error Messages 52 -* Manage → Error Messages → Flows with Error Messages 53 -* Manage → Error Messages → Exceptions of Error Messages 54 -* Manage → Log Entries 55 -* Manage → Alerts 56 -* Manage → Triggers 57 -* Manage → Tags – Cant find (only Gen2) 58 -* Manage → Notifications 59 -* Manage → Notification Settings 60 -* Manage → Data Usage → History 61 -* Manage → Code mappings → All tabs 52 +//__Event Processor Keystore and Trustore__// 62 62 63 - ==**Bugfixes**==54 +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. 64 64 65 -//__Loading problems of Deployment plan execution overview__// 66 -We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. 67 67 57 + 58 + 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 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 73 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 74 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 63 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 64 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 65 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 66 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 75 75 76 -== **Key takeaways** ==68 +== **Key Takeaways** == 77 77 78 -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:70 +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: 79 79 80 80 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 81 81 * If you have feedback or ideas for us, talk to the Platypus 82 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 83 83 * Clear your browser cache (Ctrl + Shift + Del) 84 -* Check out the release notes [here] 76 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 85 85 * Start thinking about how the license tracker can aid your development 86 86 * Start thinking about major, minor, and patch 87 -* Upgrade to the latest build number 88 88 * Keep making great integrations 89 89 90 90 Let's stay in touch and till next time! ... ... @@ -92,6 +92,11 @@ 92 92 {{info}} 93 93 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 94 94 95 -~*~* Indicates a GEN3-only feature. 96 -{{/info}})))((({{toc/}}))){{/container}} 86 +{{/info}} 87 +))) 88 + 89 +((( 90 +{{toc/}} 91 +))) 97 97 {{/container}} 93 +{{/container}}