Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version
To version 574.41
edited by dfirdausy
on 2024/07/02 12:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,87 +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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
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 -== **Private Store** ==
8 -On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
8 +== **Rapid Flow Testing** ==
9 9  
10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
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 -== **3rd generation runtime bolstering** ==
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 13  
14 -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.
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.
15 15  
16 -//__SOAP and REST web services migration, including splitting them__//
17 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
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 18  
19 -//__Changing SSL settings for 3rd generation runtime models works__//
20 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
22 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
23 +
24 +//__Property value page__//
25 +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.
21 21  
22 -//__Improved migration for JMS flows__//
23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
27 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
24 24  
25 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
29 +//__Improved text in Design architecture__//
30 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture.
26 26  
27 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 -As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
32 +//__Adding attributes for a message definition__//
33 +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.
29 29  
30 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
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.
32 32  
33 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34 -With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
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.
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.
35 35  
36 -//__Added "Reset" functionality__//
37 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
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. 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.
38 38  
39 -== **Feedback items ** ==
47 +[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
40 40  
41 -We have also solved other feedback items besides the flow designer's critical updates.
49 +[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]]
42 42  
43 -//__Improved naming convention on Store related pages__//
44 -We have improved various display names using the merge functionality within our store offering.
51 +//__Test Message from Manage-Explore__//
52 +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.
45 45  
46 -//__Update security protocols for our internal architecture__//
47 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
54 +[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
48 48  
49 -//__Improved read-only description for "if exists" constructions in Transformations__//
50 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
56 +//__Password property__//
57 +In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value.
51 51  
59 +== **Bug Fixes** ==
52 52  
53 -== **Bug fixes ** ==
61 +//__Event Processor Keystore and Trustore__//
54 54  
55 -//__Decent validation feedback when not filling in the property value__//
56 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
63 +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.
57 57  
58 -//__Incorrect resource locations__//
59 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
60 -
61 -//__Apply to environment in User Management performance improvement__//
62 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
63 -
64 64  == **Fancy Forum Answers** ==
65 65  
66 66  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:
67 67  
68 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
69 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
70 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
71 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
72 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
72 72  
73 -== **Key takeaways** ==
74 +== **Key Takeaways** ==
74 74  
75 -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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 -* 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.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
82 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a GEN3-only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
92 +{{/info}}
93 +)))
94 +
95 +(((
96 +{{toc/}}
97 +)))
94 94  {{/container}}
99 +{{/container}}