Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 96.1
edited by Erik Bakker
on 2023/04/11 10:14
Change comment: There is no comment for this version
To version 582.1
edited by dfirdausy
on 2024/07/02 14:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,95 +1,87 @@
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!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
6 +**Hi there, eMagiz developers!** In this release, we are bringing a significant performance improvement to flow testing, with execution times now accelerated by up to 3 times. 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 6  
7 -== **API improvements** ==
8 +== **Faster Flow Testing** ==
8 8  
9 -//__Improved auto-generated error handling__//
10 -When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
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.
11 11  
12 -//__Switch default message format__//
13 -We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
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 14  
15 -//__Re-using elements in gateway message__//
16 -This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
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.
17 17  
18 -//__Improved naming of API operations when adding integrations to Create__//
19 -Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
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.
20 20  
21 -== **3rd generation improvements** ==
22 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
22 22  
23 -//__Update of the static alerting engine__//
24 -In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
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.
25 25  
26 -//__Add "Data pipeline" functionality__//
27 -This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
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.
28 28  
29 -//__Fix related to the debugger__//
30 -This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
33 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
31 31  
32 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
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.
33 33  
34 -//__Improved migration process__//
35 -This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
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.
36 36  
37 -//__Deployment plan change__//
38 -In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
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.
39 39  
40 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
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.
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.
41 41  
42 -== **Feedback items ** ==
50 +[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
43 43  
44 -//__License Tracker improvements__//
45 -With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
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}}
46 46  
47 -//__Ability to view the message definition for a topic__//
48 -Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
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.
49 49  
50 -//__Restricted access for uploading custom certificates to endpoints__//
51 -To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
60 +[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
52 52  
53 -== **Bug fixes ** ==
62 +== **Bug Fixes** ==
54 54  
55 -//__Improved deletion behavior for enumerations__//
56 -To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
64 +//__Event Processor Keystore and Trustore__//
57 57  
58 -//__Prevent "async" api operations__//
59 -With this release, we have removed the ability to select the "async" option when the default message format is API Management.
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.
60 60  
61 -//__Importing a response definition broke the request definition__//
62 -Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
63 -
64 -//__Removing a flow does not update the API "all-entry" anymore__//
65 -When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
66 -
67 -//__Stop deployment plan when a property is missing__//
68 -Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
69 -
70 -//__Cap stack trace of error messages and log entries__//
71 -To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
72 -
73 73  == **Fancy Forum Answers** ==
74 74  
75 75  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:
76 76  
77 -* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
78 -* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
79 -* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
72 +* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
80 80  
81 -== **Key takeaways** ==
74 +== **Key Takeaways** ==
82 82  
83 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
76 +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:
84 84  
85 85  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  * If you have feedback or ideas for us, talk to the Platypus
87 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88 88  * Clear your browser cache (Ctrl + Shift + Del)
89 -* Check out the release notes [here]
82 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
90 90  * Start thinking about how the license tracker can aid your development
91 91  * Start thinking about major, minor, and patch
92 -* Upgrade to the latest build number
93 93  * Keep making great integrations
94 94  
95 95  Let's stay in touch and till next time!
... ... @@ -97,6 +97,11 @@
97 97  {{info}}
98 98  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
99 99  
100 -~*~* Indicates a GEN3-only feature.
101 -{{/info}})))((({{toc/}}))){{/container}}
92 +{{/info}}
93 +)))
94 +
95 +(((
96 +{{toc/}}
97 +)))
102 102  {{/container}}
99 +{{/container}}