Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 608.1
edited by Erik Bakker
on 2024/07/16 14:55
Change comment: There is no comment for this version
To version 128.1
edited by Erik Bakker
on 2023/07/17 14:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - Pop-up Party
1 +201 - Be Informed
Content
... ... @@ -1,97 +1,70 @@
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!** In this release, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
7 7  
8 -== **Feedback Items** ==
9 -//__Alerting notification settings__//
7 +== **Announcement - Release Properties** ==
8 +As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
10 10  
11 -//__Process containers__//
12 -If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
10 +== ** Deploy Architecture - Apply To Environment improvements ** ==
11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
13 13  
14 -//__Design settings__//
15 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
13 +//__Enhanced right-hand view within Deployment Plan context__//
14 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
16 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
18 18  
19 -//__Untested images__//
20 - A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before.
21 -
22 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
23 -
24 -{{warning}}
25 -The following restrictions apply to this functionality:
26 -
27 -* When accepting the risk you accept the risk for the **whole** model.
28 -* If any release based on the same runtime image is already activated on Acceptance you will **not** be warned.
29 -{{/warning}}
18 +//__Improved timeout settings when deploying__//
19 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
30 30  
31 -//__Infinispan Cache Manager__//
32 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
33 -
34 -//__Infinispan Cache Manager error message__//
35 -We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
21 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
36 36  
37 -//__Flow bump__//
38 -When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
39 -
40 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
23 +//__Detailed HTTP Statistics now show user info in specific additional cases__//
24 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
41 41  
42 -//__Unused support objects__//
43 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
26 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
44 44  
45 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
46 -
47 -//__Deleting routes__//
48 -For clarity purposes, a confirmation pop-up will be shown when deleting routes.
28 +//__Improved loading speed of Manage Dashboard__//
29 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
49 49  
50 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
31 +== **Store Improvements** ==
51 51  
52 -//__Debug queue__//
53 -The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
54 -
55 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
56 -
33 +//__Importing in Design is improved__//
34 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
35 +
57 57  == **Bug Fixes** ==
58 -//__Internal server error__//
59 -The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
60 60  
61 -//__Namespace update__//
62 -Editing a namespace used in a message definition automatically updates the message definition & transformations.
38 +//__Deprecated reminder pop-up removed__//
39 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
63 63  
64 -//__Error pop-up__//
65 -We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
41 +//__Improved selection area in Flow Designer__//
42 +When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
66 66  
67 -//__SMB inbound channel adapter__//
68 -The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
44 +//__Improved Kafka settings__//
45 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
69 69  
70 -//__Heap memory__//
71 -The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
47 +{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
72 72  
73 -//__Classpath conflicts__//
74 -We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
75 -
76 76  == **Fancy Forum Answers** ==
77 77  
78 78  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:
79 79  
80 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
81 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
82 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
53 +* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
54 +* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
83 83  
84 -== **Key Takeaways** ==
56 +== **Key takeaways** ==
85 85  
86 -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:
58 +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:
87 87  
88 88  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89 89  * If you have feedback or ideas for us, talk to the Platypus
90 -* 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.
91 91  * Clear your browser cache (Ctrl + Shift + Del)
92 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
64 +* Check out the release notes [here]
93 93  * Start thinking about how the license tracker can aid your development
94 94  * Start thinking about major, minor, and patch
67 +* Upgrade to the latest build number
95 95  * Keep making great integrations
96 96  
97 97  Let's stay in touch and till next time!
... ... @@ -99,11 +99,6 @@
99 99  {{info}}
100 100  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
101 101  
102 -{{/info}}
103 -)))
104 -
105 -(((
106 -{{toc/}}
107 -)))
75 +~*~* Indicates a GEN3-only feature.
76 +{{/info}})))((({{toc/}}))){{/container}}
108 108  {{/container}}
109 -{{/container}}