Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 245.1
edited by CarlijnKokkeler
on 2023/11/21 11:31
Change comment: There is no comment for this version
To version 574.31
edited by dfirdausy
on 2024/07/01 17:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.dfirdausy
Content
... ... @@ -1,74 +1,67 @@
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!** We have done .....
6 +**Hi there, eMagiz developers!** 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 -{{warning}}Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC. {{/warning}}
8 +== **Feedback Items** ==
9 +//__Retention duration and bytes in Capture__//
10 +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.
8 8  
9 -== **Next Generation Architecture Default** ==
10 -With this release, the next generation architecture will become the default. New models will use this generation as default.
12 +//__Help text panel in Capture__//
13 +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.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
15 +//__Adding tags in Capture__//
16 +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.
13 13  
14 -== **Cloud Template R11 - Single Lane** ==
15 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found here
18 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
19 +
20 +//__Property value page__//
21 +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.
16 16  
17 -== **Cloud Template R13 - Double Lane** ==
23 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
18 18  
25 +//__Improved text in Design architecture__//
26 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture.
19 19  
20 -== **Feedback Items** ==
28 +//__Adding attributes for a message definition__//
29 +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.
21 21  
22 -//__Unused properties overview__//
23 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
24 -* Not used by any runtime that is in the Create phase release.
25 -* Not required by a flow that is in the Create phase release.
26 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
31 +//__Helptext for HTTP methods__//
32 +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.
27 27  
28 -//__Send build requests asynchronously__//
29 -The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
34 +//__External links__//
35 +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.
30 30  
31 -//__Queue explorer milliseconds__//
32 -The queue browser now displays milliseconds in the timestamps.
37 +//__Test Message from Manage-Explore__//
38 +We improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section.
33 33  
34 -//__Cancel and next buttons order__//
35 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
40 +<Screenshot here>
36 36  
37 -//__Unused images__//
38 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
42 +//__Password property__//
43 +In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value.
39 39  
40 -//__Carwash logging__//
41 -A new logging feature enabling us to make better choices in encryption standards will be released.
42 -
43 -//__Static alerts queue consumers__//
44 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
45 -
46 46  == **Bug Fixes** ==
47 47  
48 -//__Images rebuild__//
49 -We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
47 +//__Event Processor Keystore and Trustore__//
50 50  
51 -//__Flow Designer connection line__//
52 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
49 +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.
53 53  
54 -//__Portal for migrated models__//
55 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
56 56  
57 -//__Error channel inbounds__//
58 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
59 59  
53 +
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
58 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
59 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
60 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
61 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
68 68  
63 +== **Key Takeaways** ==
69 69  
70 -== **Key takeaways** ==
71 -
72 72  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:
73 73  
74 74  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -75,10 +75,9 @@
75 75  * If you have feedback or ideas for us, talk to the Platypus
76 76  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77 77  * Clear your browser cache (Ctrl + Shift + Del)
78 -* Check out the release notes [here]
71 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
79 79  * Start thinking about how the license tracker can aid your development
80 80  * Start thinking about major, minor, and patch
81 -* Upgrade to the latest build number
82 82  * Keep making great integrations
83 83  
84 84  Let's stay in touch and till next time!
... ... @@ -86,6 +86,11 @@
86 86  {{info}}
87 87  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88 88  
89 -~*~* Indicates a next-generation-architecture only feature.
90 -{{/info}})))((({{toc/}}))){{/container}}
81 +{{/info}}
82 +)))
83 +
84 +(((
85 +{{toc/}}
86 +)))
91 91  {{/container}}
88 +{{/container}}