Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-227 - Fix Frenzy
	1	+207 - Aligned State

Content

...	...	@@ -1,19 +1,37 @@
1		-During our recent sprint cycle, we have done many fixes. These are mainly related to flow testing, alerting, and the deploy phase. Apart from that, we have improved the tracing information for errorChannel messages, and added search functionality to the Start/Stop flows overview.
	1	+In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
4	4
5		-====Minor changes====
6		-* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
7		-* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview. (#1311)
	5	+=====Runtime release notes=====
8	8
	7	+There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. For specific information, please check out this link to the [[release notes>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime/eMagiz%20Mendix%20Connector%20-%206.0.2/]]
	8	+
	9	+=====Minor changes=====
	10	+
	11	+* Design - Message Mapping: The button 'Import from Store' will directly open the store.
	12	+* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
	13	+* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
	14	+* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
	15	+* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
	16	+* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
	17	+* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	18	+* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
	19	+* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
	20	+* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
	21	+* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
	22	+* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
	23	+* Manage - Alerting: 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%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. 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.
	24	+* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
	25	+* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
	26	+
9	9	====Bug fixes====
10		-* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. (#1294)
11		-* Create - Flow Testing: The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
12		-* Create - Flow Testing: In case opening a log of test execution is not possible, a warning message will now be shown.
13		-* Create - Message Definitions: 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.
14		-* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted. (#1379)
15		-* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release. This has been resolved.
16		-* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310)
17		-* Manage - Alerting: 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 test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
18		-* Manage - Alerting: 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.
19		-* Manage - Alerting: 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.
	28	+
	29	+* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
	30	+* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
	31	+* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
	32	+* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
	33	+
	34	+
	35	+=====Infra and image changes=====
	36	+
	37	+* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.