Changes for page 236 - Another Agent

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-186 - Daemon Switch
	1	+209 - Max Verstappen

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,35 +1,33 @@
1		-The release brings the new monitoring stack to fruition and various updates to handling multiple namespaces. On top of that, we have released a slew of smaller feedback items and bug fixes.
	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.186 - Daemon Switch.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
4	4
5	5	=====New features=====
6		-* Generic - New monitoring stack: As of this release, you can run on the new monitoring stack. For more information on becoming an early adopter, don't hesitate to get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
7	7
	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	+
8	8	=====Minor changes=====
9	9
10		-* Create - Flow designer: You can now see who/when a resource was changed on a resource view page.
11		-* Design - Solution: You will see a warning in the Solution view on operation if it is not connected to a backend API operation or in "Transformation" mode.
12		-* Create - Flow designer: You can see all related configurations that use a specific resource when viewing the details of the resource.
13		-* Design - API Gateway: Changes in your Gateway messages are reflected directly in your OpenAPI JSON document.
14		-* Model Dashboard - Going to manage from the model dashboard now loads the error message dashboard without having to click on the error messages dashboard explicitly
15		-* Create - Flow testing: The name of the starting point in the flow testing result tab is matched with the component type.
16		-* Deploy - Releases: The automated flow test pop-up can now be closed by pressing "Enter."
17		-* Deploy - Properties: Password-type properties are masked in the unused properties pop-up.
18		-* Deploy - User management: "Generate Keystore" button is renamed "Download Keystore," and the file name contains environment information.
19		-* Create - Flow Testing: Added a button to display the content of a selected trace message in a pop-out.
20		-* Deploy - Properties: You can use enter key to search on the property overview page.
21		-* Create - Flow designer: Increased size of the SpEL expression input field of standard transformer component.
22		-* Create - Flow Designer: Show generated resources toggle is not disabled by default; your preference for showing or hiding generated resources will be saved.
23		-* Administration - Licenses: Added event streaming storage usage of your models.
24		-* Store: Compatibility check is added, which prevents importing G3 store items into G2 flow/integration
25		-* General: Improved help texts explaining options and screens related to the new runtime architecture or the migration towards it.
	13	+* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
	14	+* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	15	+* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
	16	+* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
26	26
27	27	====Bug fixes====
28		-* Deploy - Properties: Improved the layout of the cron trigger generator page
29		-* Deploy - Properties: Generating a password or CRON trigger will not reset the runtime field
30		-* Create - Flow designer: While editing an exit flow, the system message is not editable.
31		-* Design - Integration designer: For event streaming integrations, switching between Design Mapping and Create Transformation sometimes did not work.
32		-* Create - Transformation: For event streaming integrations, the 'Start editing' button sometimes did not work.
33		-* Create - Flow designer: Comparing two flow versions works again.
34		-* Create- Flow Designer: When creating my initial version of a flow, the notification pop-up shows the correct information.
35		-* Create - Flow Designer: All relevant support objects will be highlighted when selecting a support object.
	19	+
	20	+* Create - Flow Designer: An issue has been fixed in the flow designer where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
	21	+* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
	22	+* Deploy - Deployment plan: We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped.
	23	+* Manage - Monitoring - We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that has just migrated to the next generation architecture.
	24	+
	25	+====Infra and image changes====
	26	+
	27	+* Infra: New logging feature enabling us to make better choices in encryption standards.
	28	+
	29	+
	30	+
	31	+
	32	+
	33	+