Changes for page 240 - Spring Cleaning

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -6,16 +6,16 @@
6	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	8	== **Feedback Items** ==
9		-//__Tracing information__//
10		-The tracing errors in flow testing has been improved.
11		-
12		-[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
13		-
14	14	//__Start/stop flows search__//
15	15	The user is now able to search in the Start/Stop flows overview.
16	16
17	17	[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
18	18
	14	+//__Tracing information__//
	15	+The tracing information for errorChannel messages in flow test traces has been improved.
	16	+
	17	+[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
	18	+
19	19	//__Message redelivery queue triggers__//
20	20	The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
21	21
...	...	@@ -24,7 +24,7 @@
24	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.
25	25
26	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.
	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 test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
28	28
29	29	//__Internal/External recipients__//
30	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.
...	...	@@ -39,16 +39,16 @@
39	39	The runtime overview will now always display the correct container version.
40	40
41	41	//__List of flows__//
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.
	42	+We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
43	43
44	44	//__Deploy prevention__//
45		-We have resolved a bug that prevented you from deploying anything on a model.
	45	+When moving to the Deploy phase for the first time, a background action could fail, which would prevent deploying a release. This has been resolved.
46	46
47	47	//__Cancel button__//
48	48	The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
49	49
50	50	//__Log test execution__//
51		-If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
	51	+In case opening a log of test execution is not possible in flow testing, a warning message will now be shown.
52	52
53	53	== **Fancy Forum Answers** ==
54	54