Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+227 - Fix Frenzy

Content

...	...	@@ -1,17 +1,17 @@
1		-In the last sprint cycle, we done several improvements for the Design and Deploy phases. Moreover, we have improved the Event Catalog overview for Catalog users. Our bug fixes concern the import of xsds, the deletion behaviour of containerse, and the generation of scope properties.
	1	+During our recent sprint cycle, we have ......
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.222 - Flee Frustration||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4	4
5		-====New features====
6		-* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
7		-* Create - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
	5	+====Minor changes====
	6	+* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
8	8
9	9	====Bug fixes====
10		-* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
11		-* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
12		-* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)
13		-* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
14		-* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)
15		-
16		-
17		-
	9	+* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
	10	+* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
	11	+* 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.
	12	+* 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.
	13	+* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release
	14	+* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
	15	+* 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.
	16	+* 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.
	17	+* 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.