Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 587.1
edited by Erik Bakker
on 2024/07/02 15:05
on 2024/07/02 15:05
Change comment:
There is no comment for this version
To version 705.1
edited by Erik Bakker
on 2024/09/09 10:16
on 2024/09/09 10:16
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 4-Summer Sonata1 +229 - Xpath Alignment - Content
-
... ... @@ -3,73 +3,52 @@ 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 asignificant performanceimprovementto flow testing,with executiontimes now accelerated by uptothreetimes. Next tothat, overthe past week, we focused onmproving the usabilityofour platformandaddressingcommunity feedback.Specifically,we enhanced userinterface elementsonseveral pages,includingthedescriptions of helptexts, externallinkswithin helpxts, andtheoveralllayout of helptextpages.Additionally,wemadeimprovementsto several pop-up pages. We also made the user interface more user-friendlyfor debuggingintegrationflows. Lastly, we resolved anissueforsomemodelswhencreating an Event Processor.6 +**Hi there, eMagiz developers!** In this release, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Find out all the improvements and bug fixes below! 7 7 8 -== ** Faster Flow Testing** ==8 +== **Deployment Plan Improvements** == 9 9 10 - We are rolling outa majorupgrade to flow testingperformance, boosting execution speeds by up to three times.This enhancement will greatly accelerate your workflow when developingintegrations,enabling you toruntestsfaster andmore efficiently. Consequently, this will further support users for delivering higher-quality integrations.10 +//__Monitoring Trigger - Improvements__// 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 +* For the step type "Monitoring Trigger," we have re-introduced the "Enable" option. 15 15 16 -//__Help text panel in Capture__// 17 -Collapsing the help text of this pop-up page by clicking the "i" icon on the top right corner of the pop-up page will now correctly hide the help text pane. 14 +[[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]] 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. 16 +* The "Disable" option under this step type comes with two new options. 17 +** End Action. Here, you can opt for the following three options 18 +*** Auto-enable triggers 19 +*** Send email 20 +*** Both 21 +* Duration. Here, you can define a waiting period that states how long eMagiz should wait before executing the end action. The value of this field needs to lie between 15 and 120 minutes. Note that the timer starts when your deployment plan's "disable" step is finished. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-22 4-selectable-cursor-for-tags.png]]23 +[[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]] 23 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. 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. 32 - 33 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 34 - 35 -//__Password property__// 36 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 37 - 38 -//__Enumeration values__// 39 -When editing a message definition (i.e., a System Message, CDM, API Data Model, or Event Streaming Data Model) in the Flow designer within 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. 40 - 41 -//__Helptext for HTTP methods__// 42 -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. 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. 25 +{{warning}}Note that the end action is only triggered when the deployment plan cannot complete all steps. When all steps are completed, the timer is **stopped**. Therefore, we advise adding the "enable" step back to the end of your deployment plan to ensure that triggers are automatically re-enabled when the deployment is successfully finished. This also covers cases where the deployment plan is automatically executed (by pressing the play button), after which the user moves on to other things and forgets to move away from the page once the deployment plan is completed. 46 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. 27 +In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}} 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}} 30 +//__Default Plan - Improvements__// 56 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. 32 +* When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment). 59 59 60 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 34 +* The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed. 35 +* The "Enable" step is added as the last step of your deployment plan. 61 61 37 +[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]] 38 + 62 62 == **Bug Fixes** == 40 +//__XPath Header Enricher - Help Text Improvement__// 41 +We have added various help text segments that explain which results the XPath expression will yield in this context and how to ensure that a list of results is returned when executing this action. 63 63 64 -//__Event Processor Keystore and Trustore__// 43 +//__XPath Configuration - Transformation__// 44 +We fixed a bug that caused data loss once you switched between the "custom xpath" and "if exists" options when adding a filter or transformation in the Create Transformation tooling. 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 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]] 50 +* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]] 51 +* [[How to process messages with invalid XML content like "">>https://my.emagiz.com/p/question/172825635703939917||target="blank"]] 73 73 74 74 == **Key Takeaways** == 75 75 ... ... @@ -79,7 +79,7 @@ 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.22 4-Summer Sonata.WebHome||target="blank"]]61 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.228 - Monitoring Mania.WebHome||target="blank"]] 83 83 * Start thinking about how the license tracker can aid your development 84 84 * Start thinking about major, minor, and patch 85 85 * Keep making great integrations