Changes for page 240 - Spring Cleaning

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-229 - Xpath Alignment
	1	+227 - Fix Frenzy

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -3,52 +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 made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Find out all the improvements and bug fixes 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		-== **Deployment Plan Improvements** ==
	8	+== **Feedback Items** ==
	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.
9	9
10		-//__Monitoring Trigger - Improvements__//
	12	+[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
11	11
12		-* For the step type "Monitoring Trigger," we have re-introduced the "Enable" option.
	14	+//__Start/stop flows search__//
	15	+It is now possible to search in the Start/Stop flows overview.
13	13
14		-[[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]]
	17	+[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-searchterm.png]]
15	15
16		-* The "Disable" option under this step type comes with two new options.
17		-** End Action. Here, you can opt for the following three options
18		-*** Auto-enable triggers
19		-*** Send email
20		-*** Both
21		-* Duration. Here, you can define a waiting period that states how long eMagiz should wait before executing the end action. The value of this field needs to lie between 15 and 120 minutes. Note that the timer starts when your deployment plan's "disable" step is finished.
	19	+//__Message redelivery queue triggers__//
	20	+The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
	21	+
	22	+== **Bug Fixes** ==
	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		-[[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]]
	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.
24	24
25		-{{warning}}Note that the end action is only triggered when the deployment plan cannot complete all steps. When all steps are completed, the timer is **stopped**. Therefore, we advise adding the "enable" step back to the end of your deployment plan to ensure that triggers are automatically re-enabled when the deployment is successfully finished. This also covers cases where the deployment plan is automatically executed (by pressing the play button), after which the user moves on to other things and forgets to move away from the page once the deployment plan is completed.
26		-
27		-In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}}
	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.
28	28
	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.
29	29
30		-//__Default Plan - Improvements__//
	35	+//__Area selector__//
	36	+We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
31	31
32		-* When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment).
	38	+//__Runtime overview__//
	39	+The runtime overview will now always display the correct container version.
33	33
34		-* The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed.
35		-* The "Enable" step is added as the last step of your deployment plan.
	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.
36	36
37		-[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]]
	44	+//__Deploy prevention__//
	45	+We have resolved a bug that prevented you from deploying anything on a newly created model.
38	38
39		-== **Bug Fixes** ==
40		-//__XPath Header Enricher - Help Text Improvement__//
41		-We have added various help text segments that explain which results the XPath expression will yield in this context and how to ensure that a list of results is returned when executing this action.
	47	+//__Cancel button__//
	48	+The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
42	42
43		-//__XPath Configuration - Transformation__//
44		-We fixed a bug that caused data loss once you switched between the "custom xpath" and "if exists" options when adding a filter or transformation in the Create Transformation tooling.
	50	+//__Log test execution__//
	51	+If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
45	45
46	46	== **Fancy Forum Answers** ==
47	47
48	48	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:
49	49
50		-* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]]
51		-* [[How to process messages with invalid XML content like "&#x2">>https://my.emagiz.com/p/question/172825635703939917||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"]]
52	52
53	53	== **Key Takeaways** ==
54	54
...	...	@@ -58,7 +58,7 @@
58	58	* If you have feedback or ideas for us, talk to the Platypus
59	59	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
60	60	* Clear your browser cache (Ctrl + Shift + Del)
61		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.WebHome||target="blank"]]
	68	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]]
62	62	* Start thinking about how the license tracker can aid your development
63	63	* Start thinking about major, minor, and patch
64	64	* Keep making great integrations