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	+210 - Deployment Delights

Content

...	...	@@ -1,19 +1,28 @@
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 improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.210 - Deployment Delights||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.
	5	+=====New features=====
8	8
	7	+* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
	8	+* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
	9	+* All - The next generation architecture is the default now. New models will use this generation as default.
	10	+
	11	+=====Minor changes=====
	12	+
	13	+* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
	14	+* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
	15	+* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
	16	+
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.
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.
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.
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.
	18	+
	19	+* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
	20	+* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
	21	+* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	22	+
	23	+
	24	+
	25	+
	26	+
	27	+
	28	+