Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 591.1
edited by CarlijnKokkeler
on 2024/07/16 10:45
Change comment: There is no comment for this version
To version 371.1
edited by CarlijnKokkeler
on 2024/01/31 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +213 - Joyful Journeys
Content
... ... @@ -3,76 +3,78 @@
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 are bringing a significant performance improvement to flow testing, with execution times now accelerated by at least three times faster, and up to five times faster. Next to that, 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 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
7 7  
8 -== **Faster Flow Testing** ==
8 +== **Pop-up Improvements** ==
9 9  
10 -We are rolling out a major upgrade to flow testing performance, boosting execution speeds by at least three times faster, and up to five times faster. 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 +//__Property releases__//
11 +When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
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.
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
15 +//__Runtime deletion__//
16 +When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container.
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.
18 +//__Wiretap & debug error messages__//
19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
21 +//__Action messages__//
22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
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.
24 +== **Formatting & Alignments** ==
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.
26 +//__Input fields__//
27 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
29 +//__UI improvements__//
30 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
34 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.
32 +//__Component changes reversion__//
33 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
37 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.
35 +//__State generation statistics__//
36 +The state generation graphs will now show the correct number of cache hits and misses.
40 40  
41 -//__Editing Flow Resource__//
42 -While editing a flow in Create, if users attempt to modify a resource that is used by multiple flows, they will now see a warning indicating that this resource is shared and that all flows using it may need to be updated.
38 +//__Queue browser timestamps__//
39 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
43 43  
44 -//__Helptext for HTTP methods__//
45 -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.
41 +//__Addition and deletion of internal recipients__//
42 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
46 46  
47 -//__External links__//
48 -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.
49 -
50 -//__Debugging Shortcut__//
51 -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.
44 +== **Feedback Items** ==
52 52  
53 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
46 +//__Update flows__//
47 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. This is particularly useful when changing a resouce used across multiple flows such as topic message definitions in event processors.
54 54  
55 -{{html}}
56 -<!-- 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. -->
57 -<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] -->
58 -{{/html}}
49 +//__Q&A forum search__//
50 +The option to search by pressing the Enter key has been added to the Q&A forum.
59 59  
60 -//__Test Message from Manage-Explore__//
61 -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.
52 +//__Memory settings__//
53 +It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
54 +//__Runtime validation__//
55 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
62 62  
63 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
57 +//__Runtime overview image versions__//
58 +Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
64 64  
65 65  == **Bug Fixes** ==
66 66  
67 -//__Event Processor Keystore and Trustore__//
62 +//__Removal of onramp__//
63 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
68 68  
69 -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.
65 +//__Runtime statistics details__//
66 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
70 70  
68 +//__Deployment prechecks__//
69 +During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
70 +
71 71  == **Fancy Forum Answers** ==
72 72  
73 73  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:
74 74  
75 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
75 +* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
76 +* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
77 +* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
76 76  
77 77  == **Key Takeaways** ==
78 78  
... ... @@ -82,7 +82,7 @@
82 82  * If you have feedback or ideas for us, talk to the Platypus
83 83  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84 84  * Clear your browser cache (Ctrl + Shift + Del)
85 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
87 +* Check out the release notes [here]
86 86  * Start thinking about how the license tracker can aid your development
87 87  * Start thinking about major, minor, and patch
88 88  * Keep making great integrations