Changes for page 273 - Squash Squash

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-239 - Modern Talking
	1	+273 - Squash Squash

Content

...	...	@@ -1,17 +1,19 @@
1		-In the last sprint, we focused on testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us, we are ready to launch the new eMagiz Mendix Connector in our community. With this release, we will make it available for all new Mendix systems in models running on the current-generation architecture. In a future release, we will bring a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the platform.
	1	+This release includes various smaller improvements throughout the various phases of the platform. On top of that, we have updated certain parts of our Mendix project to their respective latest version.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.239 - Modern Talking.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.273 - Squash Squash.WebHome||target="blank"]].
4	4
5		-====New Features====
	5	+==== Minor Changes ====
6	6
7		-* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. It is better integrated into your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models.
8		-** A migration wizard will be released later, allowing you to quickly and smoothly migrate your legacy Mendix connectors to the new Mendix connector.
	7	+* Deploy - History (Releases): Introduced various changes to this overview to make the information we show here more specific. The main changes are that we show a full timestamp in the “When” column instead of the date itself, and the “eye” icon is only present when the registered audit log exceeds a predefined length. (#1779)
9	9
10		-====Minor Changes====
	9	+===== Bug Fixes ====
11	11
12		-* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in the view mode of the Flow Designer. (#870)
	11	+* Design - Message Mapping: Bug fix for the Design Message mapping right-panel where, if the number of errors exceeded a certain threshold, it would push the bottom bar out of the viewing window. Also properly aligned action buttons.
	12	+* Design - Architecture: We fixed an inconsistency that prevented users from adding a multi-runtime system to their Design Architecture.
	13	+* Deploy - Container overview: We fixed an inconsistency in this overview that would incorrectly mark the deployed version as unexpected. Furthermore, we have renamed this overview to better align with what we show. (#1673)
	14	+* Manage - Queue dashboards: Fixed detailed message throughput graph with spikey first and last observations. (#1763)
	15	+* Manage - Alerting - Triggers (Notification Settings): Improved user feedback and interaction when no recipient is selected, preventing users from pressing Save. (#1765)
13	13
14		-====Bug fixes====
	17	+==== Remarks ====
15	15
16		-* Create - Flow Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517)
17		-* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the {{code}}[id].[system].[flow]{{/code}} convention, or when that value is longer than expected. (#1566)
	19	+* Updated various UI related modules within our Mendix project to their respective latest version.