Changes for page 240 - Spring Cleaning

Summary

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

Details

Page properties

Content

...	...	@@ -3,33 +3,61 @@
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!** 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!
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}}
	8	+== **Deployment Plan Improvements** ==
9	9
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.
	10	+//__Monitoring Trigger - Improvements__//
13	13
14		-[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
	12	+* For the step type "Monitoring Trigger," we have re-introduced the "Enable" option.
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).
	14	+[[image:Main.Images.Release Blog.WebHome@release-229-enable-option.png]]
	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.
	22	+
	23	+[[image:Main.Images.Release Blog.WebHome@release-229-disable-option.png]]
	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.
18	18
	27	+In the coming weeks, we will actively monitor eMagiz models to see to what extent this advice has been implemented.{{/warning}}
	28	+
	29	+//__Default Plan - Improvements__//
	30	+
	31	+* When you press the "Default Plan" option, the following changes will occur (assuming you also have a default plan on your environment):
	32	+** The existing "Disable" step is extended to define that eMagiz will automatically enable triggers after 60 minutes have passed.
	33	+** The "Enable" step is added as the last step of your deployment plan.
	34	+
	35	+[[image:Main.Images.Release Blog.WebHome@release-229-new-default-plan.png]]
	36	+
	37	+== **SFTP Authentication Option Added - New Runtime Image** ==
	38	+
	39	+With this release we launch a new runtime image that provides an additional configuration option on our SFTP (caching) session factory support object. With this option you can define the **order** in which the authentication is handled and which options are **allowed**. The following options are possible. The default configuration option (which is valid in 99% of the cases) is "Keyboard-Interactive and Password".
	40	+
	41	+* Password
	42	+* Keyboard-Interactive
	43	+* Password and Keyboard-Interactive
	44	+* Keyboard-Interactive and Password
	45	+
	46	+[[image:Main.Images.Release Blog.WebHome@release-229-new-auth-option-sftp.png]]
	47	+
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.
	49	+//__XPath Header Enricher - Help Text Improvement__//
	50	+We have added a help text segment that explain that you will get the first result back if your XPath returns a list of values. Secondly, we have added an additional help text segment that explains how to change the XPath expression in case you want to get a list of values back.
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.
	52	+//__XPath Configuration - Transformation__//
	53	+We fixed a bug that caused the “Value“ input field to disappear once you switched from the "custom xpath" to the "if exists" option when adding a Conditional block in the Create Transformation tooling.
25	25
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"]]
	59	+* [[Spaces handled differently in folder name after using SMB components for file connectivity>>https://my.emagiz.com/p/question/172825635703940018||target="blank"]]
	60	+* [[How to process messages with invalid XML content like "&#x2">>https://my.emagiz.com/p/question/172825635703939917||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"]]
	70	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.229 - Xpath Alignment.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