Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-226 - Alerting Alchemy
	1	+191 - Fifty Fifty

Author

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

Content

...	...	@@ -1,12 +1,36 @@
1		-During our recent sprint cycle, we have worked to release a new design for queue alerting. Find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Moreover, we have worked on tenant items, machine pop-ups and progress bars, and the Infinispan Cache Manager. Please find out all below!
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.191 - Fifty Fifty.WebHome||target="blank"]].
4	4
5		-====Minor changes====
6		-* Create - Flow Designer: The Infinispan Cache Manager has been updated to provide an additional 'transport type' to offer more means for creating a clustered setup, provide clearer helptexts, and include validation on fields depending on the selected 'transport type'.
7		-* Design - Tenant: The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
8		-* Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
9		-* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
10		-* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually.
11		-* Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
12		-* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Find out more information in our [[release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]] and our [[new alerting microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].
	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	+=====Minor changes=====
	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.
	28	+
	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	+