Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 620.1
edited by Carlijn Kokkeler
on 2024/07/16 15:45
Change comment: There is no comment for this version
To version 658.1
edited by Carlijn Kokkeler
on 2024/08/12 11:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - Pop-up Party
1 +227 - Fix Frenzy
Content
... ... @@ -3,80 +3,57 @@
3 3  (((
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!
6 +**Hi there, eMagiz developers!** This release we have many fixes! Mainly for flow testing, the deploy phase, and alerting for hybrid models several small bugs have been resolved. Apart from these fixes, search functionality has been added to the start/stop flows screen. Moreover, the tracing information for errorChannel messages in flow test traces has been improved. Find out all about it below!
7 7  
8 8  == **Feedback Items** ==
9 -//__Process containers__//
10 -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.
9 +//__Start/stop flows search__//
10 +The user is now able to search in the Start/Stop flows overview.
11 11  
12 -//__Design settings__//
13 -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.
12 +[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
14 +//__Tracing information__//
15 +The tracing information for errorChannel messages in flow test traces has been improved.
16 16  
17 -//__Untested images__//
18 - 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.
19 -
20 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
17 +[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
21 21  
22 -{{warning}}
23 -The following restrictions apply to this functionality:
19 +
20 +== **Bug Fixes** ==
21 +//__Update namespace resources__//
22 +The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
24 24  
25 -* When accepting the risk you accept the risk for the **whole** model.
26 -* If any release based on the same runtime image is already activated on Acceptance you will **not** be warned.{{/warning}}
24 +//__Queue triggers hybrid models__//
25 +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 a new component called GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] 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>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
27 +//__Internal/External recipients__//
28 +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 all flows using a specific resource, you can specify which version type you want to create, Major, Minor or Patch version. On top of this you can also give more information in a description.
36 -
37 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
30 +//__Tenant queue trigger__//
31 +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'.
33 +//__Area selector__//
34 +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.
36 +//__Runtime overview__//
37 +The runtime overview will now always display the correct container version.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
39 +//__List of flows__//
40 +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 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
53 -
54 -== **Bug Fixes** ==
55 -//__Internal server error__//
56 -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.
42 +//__Deploy prevention__//
43 +When moving to Deploy phase for the first time, a background action could fail, which would prevent deploying a release. This has been resolved.
57 57  
58 -//__Namespace update__//
59 -Editing a namespace used in a message definition automatically updates the message definition & transformations.
45 +//__Cancel button__//
46 +The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
60 60  
61 -//__Error pop-up__//
62 -We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
48 +//__Log test execution__//
49 +In case opening a log of test execution is not possible in flow testing, a warning message will now be shown.
63 63  
64 -//__SMB inbound channel adapter__//
65 -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.
66 -
67 -//__Heap memory__//
68 -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.
69 -
70 -//__Classpath conflicts__//
71 -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.
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 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
78 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
79 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
55 +* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]]
56 +* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]]
80 80  
81 81  == **Key Takeaways** ==
82 82  
... ... @@ -86,7 +86,7 @@
86 86  * If you have feedback or ideas for us, talk to the Platypus
87 87  * 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>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
66 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.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 92  * Keep making great integrations