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 - 224-SummerSonata1 +185 - To determine - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.eMagiz - Content
-
... ... @@ -1,95 +1,78 @@ 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!** Inthis release,wearebringingasignificantperformanceimprovementtoflow testing,with executiontimes now accelerated by up to 3 times.Nextto that, overthepast week, we focusedon improvingthe usabilityof ourplatform andaddressingcommunity feedback.Specifically,weenhanceduserinterfaceelementson severalpages,including thedescriptionsofhelptexts,externallinkswithinhelptexts,andthe overalllayout of help text pages.Additionally, wemadeimprovementstoseveral pop-up pages. Wealso madetheuserinterfacemoreuser-friendlyfordebuggingintegrationflows.Lastly, weresolvedanissueforsomemodelswhencreatinganEvent Processor.5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one. 7 7 8 -== **Faster FlowTesting**==7 +==**Flow Designer V3**== 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 +The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider. 10 + 11 +=== **Improvements** === 12 +The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy. 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. 14 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 15 15 16 -//__Help text panel in Capture__// 17 -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. 16 +Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow. 17 + 18 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]] 19 + 20 +* **Alerts** 21 +In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location. 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. 23 +* **Resources** 24 +In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these. 25 + 26 +* **Support objects** 27 +The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 29 +* **Properties** 30 +The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry. 31 + 32 +=== **User interaction changes** === 33 +There are some small changes to consider compared to the old flow designer. Please take a moment to read these: 34 + 35 +* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select 36 +* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier 23 23 24 -//__Improved text in Design architecture__// 25 -We fixed some spelling mistakes in the steps to be executed within the pop-up page when applying to environment in Design architecture. 26 26 27 -//__Property value page__// 28 -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. 39 +== **Feedback items ** == 29 29 30 - [[image:Main.Images.ReleaseBlog.WebHome@release-224-pop-ups-wrapped-property-values.png]]41 +We have also solved other feedback items besides the key updates around functionality. 31 31 32 -//__ Adding attributesforamessagedefinition__//33 -W e fixedanissuewhereyour selectedattributeswerelost whennavigatingbetweenpaginations whileaddingmoreattributestotheentityinthepop-up shownwhen you pressthe'AddAttribute'buttonon therightpanel ofyourSystemMessage, CDM, API DataModel, orEventStreamingDataModel.43 +//__Set runtime field as first selected field on property level__// 44 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well. 34 34 35 -//__Helptext for HTTP methods__// 36 -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. 37 - 38 -//__External links__// 39 -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 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 40 40 41 -//__Enumeration values__// 42 -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. 43 43 44 -//__Debugging Shortcut__// 45 -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. 46 - 47 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 48 - 49 -{{html}} 50 -<!-- 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. --> 51 -<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] --> 52 -{{/html}} 53 - 54 -//__Test Message from Manage-Explore__// 55 -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. 56 - 57 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 58 - 59 -//__Password property__// 60 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 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 -As always, this isa 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:51 +As always, a gentle reminder to all 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"]] 53 +* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]] 54 +* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]] 73 73 74 -== **Key Takeaways** ==56 +== **Key takeaways** == 75 75 76 -Thanks to all whohelpedbuildandthose who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:58 +Thanks to all that help build, 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 79 * If you have feedback or ideas for us, talk to the Platypus 80 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 +* 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"]]64 +* 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 67 +* Upgrade to the latest build number 85 85 * Keep making great integrations 69 +* Check out the new documentation portal. 86 86 87 87 Let's stay in touch and till next time! 88 88 89 -))) 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]] 90 90 91 -((( 92 -{{toc/}} 93 -))) 76 +~*~* Indicates a GEN3-only feature. 77 +{{/info}})))((({{toc/}}))){{/container}} 94 94 {{/container}} 95 -{{/container}}