Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 724.1
edited by Carlijn Kokkeler
on 2024/09/25 16:55
Change comment: There is no comment for this version
To version 673.1
edited by Carlijn Kokkeler
on 2024/08/14 12:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +227 - Fix Frenzy
Content
... ... @@ -3,33 +3,59 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all 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 and we have enabled our new queue trigger functionality for redelivery-enabled messaging queues. Find out all about it below!
7 7  
8 -{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{/info}}
9 -
10 10  == **Feedback Items** ==
11 -//__Add integration__//
12 -When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
9 +//__Tracing information__//
10 +Tracing errors in flow testing has been improved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V312.WebHome||target="blank"]] is available.
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
12 +[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
15 15  
16 -//__Failover__//
17 -We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more on our documentation page (LINK).
18 -
14 +//__Start/stop flows search__//
15 +It is now possible to search in the Start/Stop flows overview.
16 +
17 +[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-searchterm.png]]
18 +
19 +//__Message redelivery queue triggers__//
20 +The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
21 +
19 19  == **Bug Fixes** ==
20 -//__Queues with illegal characters__//
21 -Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
23 +//__Update namespace resources__//
24 +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.
22 22  
23 -//__Blocked deployment step__//
24 -We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
26 +//__Queue triggers hybrid models__//
27 +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 use the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
25 25  
29 +//__Internal/External recipients__//
30 +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.
31 +
32 +//__Tenant queue trigger__//
33 +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.
34 +
35 +//__Area selector__//
36 +We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
37 +
38 +//__Runtime overview__//
39 +The runtime overview will now always display the correct container version.
40 +
41 +//__List of runtimes__//
42 +We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of runtimes that will be restarted.
43 +
44 +//__Deploy prevention__//
45 +We have resolved a bug that prevented you from deploying anything on a newly created model.
46 +
47 +//__Cancel button__//
48 +The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
49 +
50 +//__Log test execution__//
51 +If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
52 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
31 -* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
32 -* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
57 +* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]]
58 +* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]]
33 33  
34 34  == **Key Takeaways** ==
35 35  
... ... @@ -39,7 +39,7 @@
39 39  * If you have feedback or ideas for us, talk to the Platypus
40 40  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 41  * Clear your browser cache (Ctrl + Shift + Del)
42 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
68 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]]
43 43  * Start thinking about how the license tracker can aid your development
44 44  * Start thinking about major, minor, and patch
45 45  * Keep making great integrations