Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 598.1
edited by Carlijn Kokkeler
on 2024/07/16 14:03
Change comment: There is no comment for this version
To version 653.1
edited by Carlijn Kokkeler
on 2024/08/12 11:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +227 - TBD
Content
... ... @@ -5,61 +5,45 @@
5 5  
6 6  **Hi there, eMagiz developers!**
7 7  
8 -
9 9  == **Feedback Items** ==
10 -//__Alerting notification settings__//
11 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
9 +//__Start/stop flows search__//
10 +The user is now able to search in the Start/Stop flows overview.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12 +[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
14 14  
15 -//__Process containers__//
16 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
14 +//__Tracing information__//
15 +The tracing information for errorChannel messages in flow test traces has been improved.
17 17  
18 -//__Design settings__//
19 -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.
17 +[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
19 +== **Bug Fixes** ==
20 +//__Update namespace resources__//
21 +The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes on your namespaces in your message definitions.
22 22  
23 -//__Untested images__//
24 - 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.
25 -
26 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
23 +//__Queue triggers hybrid models__//
24 +We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
27 27  
28 -//__Infinispan Cache Manager__//
29 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
30 -
31 -//__Infinispan Cache Manager error message__//
32 -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 LINK is available.
26 +//__Internal/External recipients__//
27 +You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly. Cases where this was applied incorrectly have been automatically fixed.
33 33  
34 -//__Flow bump__//
35 -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.
36 -
37 -IMAGE
29 +//__Tenant queue trigger__//
30 +We have fixed a case where a tenant queue trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
38 38  
39 -//__Unused support objects__//
40 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
32 +//__Area selector__//
33 +We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
43 -
44 -//__Deleting routes__//
45 -For clarity purposes, a confirmation pop-up will be shown when deleting routes.
35 +//__Runtime overview__//
36 +The runtime overview will now always display the correct container version.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
38 +//__List of flows__//
39 +We fixed a bug where runtimes that did not appear in the list of flows of the deployment plan were restarted anyway.
48 48  
49 -//__Debug queue__//
50 -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.
51 -
52 -== **Bug Fixes** ==
53 -
54 -
55 -
56 -
57 -
58 58  == **Fancy Forum Answers** ==
59 59  
60 60  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:
61 61  
62 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
45 +* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
46 +* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
63 63  
64 64  == **Key Takeaways** ==
65 65  
... ... @@ -69,7 +69,7 @@
69 69  * If you have feedback or ideas for us, talk to the Platypus
70 70  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
71 71  * Clear your browser cache (Ctrl + Shift + Del)
72 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
56 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
73 73  * Start thinking about how the license tracker can aid your development
74 74  * Start thinking about major, minor, and patch
75 75  * Keep making great integrations