Changes for page 61

Summary

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

Details

Page properties

Content

...	...	@@ -1,31 +1,20 @@
1		-Release that introduces a visual refresh on the Capture widget. In addition, this release includes several other improvements and tackles some minor issues.
	1	+Small update that fixes three specific issues.
2	2
3		-To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
4		-
5	5	Find out more in our [release blog]
6	6
7	7
8		-===== New features =====
9		-
10		-* Built-in support for EDI messages
11		- ** Design - System: EDI is a new message format supported in eMagiz. You can select this as the default option when editing a system or when editing a system message. Note that, this option is supported only for Generation 3 runtimes.
12		- ** Create - Flow designer: The autogenerated definitions and transformations components are customized so that EDI to XML validations and transformations are possible. Note that in this version the filter will not work with the eMagiz message definitions if they use multiple namespaces, in that case, a custom XSD should be used.
13		-
14	14	===== Minor Changes =====
15	15
16		-* Deploy - Releases: Improved performance for deploying releases using the deployment plan.
17		-* Capture - Requirements Designer: The requirements designer got a visual refresh. Furthermore, new (multi-tenant) systems can now be created by clicking the blue rectangles in the left panel, rather than by dragging them in.
18		-* Design - System Message Definition: Importing message definitions from store with multiple namespaces is supported.
19		-* Deploy - Releases. You are now able to prevent releases to be deleted (either by eMagiz or manually) by enabling the block autodeletion feature per release. This can be done for at most 3 releases in total. (#587)
20		-* Create - Flow designer: Improved the help texts of HTTP outbound components to clarify the exact working of the ‘encoding mode’ setting.
	8	+* Updated bundle 'com.emagiz.bundles.groovy-all' from 3.0.9.1 to 3.0.9.2
	9	+* Removed bundle 'com.sun.mail.javax.mail' because it was not used anymore
	10	+* Updated bundle 'com.emagiz.components.security' from 7.1.1 to 7.2.0
	11	+* Updated bundle 'com.emagiz.components.http' from 7.2.1 to 7.2.2
	12	+* Updated bundle 'com.emagiz.util.codec' from 6.1.0 to 6.1.1
21	21
22		-
23	23	===== Bug Fixes =====
24	24
25		-* Deploy - Releases: We fix a small issue that adds an onramp (or an offramp) that is linked to an exit/entry connector to a release at a later moment. (#442)
26		-* Community - Q&A: The richtext editor no longer adds a break line when you change a style of text.
27		-* Create - Transformation: Fixed the position of the ‘View XSLT Button’ that in some cases was not correct.
28		-* Manage - Dashboard: The popup with detailed information on errors did not work for certain types of errors. (#583)
29		-* Deploy - Releases: You will not see an error in “Outdated Flows” pop-up if your release has outdated flows.
30		-* The help text is appearing correctly when clicking attributes on a page.
	16	+* The OAuth 2.0 authorization interceptor in the Rest Template component contained client 'Authentication methods’ that were invalid and caused a flow not to start in build 59. Also the clockskew is now configurable so we can handle the requirements of more oauth2 authentication providers.
	17	+* The Amazon S3 authentication interceptor in the Rest Template component had a threading issue where the key would be invalid on heavy usage. The threading has been changed and is now behaving correctly.
	18	+* In several flow designer components you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) did not work.
	19	+* For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches.
31	31