Changes for page 220 - Patch Parade

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-191 - Fifty Fifty
	1	+199 - Home Improvements

Content

...	...	@@ -1,36 +1,20 @@
1		-The release introduces a lot of small fixes as a result of our "hackathon" efforts. Subsequently we will release several 3rd generation runtime offerings.
	1	+In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
4	4
5		-=====New features=====
6		-* Manage - Alerting: There are 4 new types of triggers available for Model in G3.
7		-** Error Message is to evaluate the headers of the original message which resulted in an error.
8		-** Log Keyword is to evaluate logging messages. You can provide a one or several words which you expect in your logging events.
9		-** Queue Consumers is to configure for queues where more than 1 consumer is expected.
10		-** Queue Messages is to configure for queues where more than 100 messages on a queue can occur
11		-** Queue Throughput is to monitor issues with your system by setting thresholds for the number of messages that are expected to pass through the flow.
12		-
13		-=====Major changes=====
14		-
15		-* Manage - Redelivery: You can explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Besides that, you can also redeliver the message(s) on this page.
16		-
17	17	=====Minor changes=====
18	18
19		-* Design - System message: 'Request' and 'Response' entities are automatically generated and set as root entities for new SOAP web service integrations in 3rd generation runtimes.
20		-* Create - Flow designer: sensitive information stored in property values is masked. (#790)
21		-* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so the user can use it to compare the previous versions.
22		-* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
23		-* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
24		-* Deploy - Architecture: Before pressing "Apply to environment," we require a confirmation from you if you accept the topology changes suggested by eMagiz that might impact AWS. (#828)
25		-* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
26		-* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
27		-* Deploy - Releases - You will be reminded of empty runtimes when activating a release. Empty runtimes are runtimes without flows in the release, and these runtimes should be removed from your architecture.
	7	+* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
	8	+* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
	9	+* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
	10	+* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
	11	+* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
	12	+* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
	13	+* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
	14	+* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
28	28
29	29	====Bug fixes====
30		-* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
31		-* Create - Flow Designer: When copying and pasting, support objects such as "property placeholder," "support.bus-connection-caching," and "support. bus-connection-plain" are not duplicated (#793)
32		-* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
33		-* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
34		-* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
35		-* Deploy - Architecture: The deploy runtimes option is only visible for admin. A new menu item, "Deploy agent," is added and visible for all users to show the command which can be used to deploy the agent to an on-premises machine.
36	36
	18	+* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
	19	+* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
	20	+