Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Content

...	...	@@ -48,9 +48,34 @@
48	48
49	49	//__Cancel and next buttons order//
50	50	The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
51		-
52	52
	52	+//__Data sink page__//
	53	+The data sink page has been moved to the “Explore” tab.
	54	+
	55	+//__Unused images removal__//
	56	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
	57	+
	58	+//__Flow Designer performance__//
	59	+Performance improvements for the Flow Designer have been implemented.
	60	+
	61	+//__Properties with special characters__//
	62	+When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
	63	+
	64	+//__Hidden flow fragements__//
	65	+When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
	66	+
	67	+//__Resources disappearances__//
	68	+Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
	69	+
	70	+//__Error channel for all inbounds__//
	71	+If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
	72	+We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
	73	+
	74	+//__Highlighting resources__//
	75	+The performance of highlighting resources of selected components is improved in Read only mode.
	76	+
53	53	== **Bug Fixes** ==
	78	+
54	54	//__Topic and event-processor names__//
55	55	The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
56	56
...	...	@@ -57,8 +57,23 @@
57	57	//__System alignment__//
58	58	The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
59	59
60		-
61		-
	85	+//__Error checking__//
	86	+Besides checking error header, the error trigger is now configured to check if an error message contains a term.
	87	+
	88	+//__Alerting__//
	89	+For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
	90	+For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
	91	+The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
	92	+
	93	+//__Unused containers__//
	94	+Containers are set inactive when they are unused and removed in Design.
	95	+
	96	+//__Error popups when promoting a release version__//
	97	+We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
	98	+
	99	+//__Memory leak__//
	100	+A memory leak when using gen 3 metrics has been fixed.
	101	+
62	62	== **Fancy Forum Answers** ==
63	63
64	64	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: