Changes for page 235 - Last Log

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-191 - Fifty Fifty
	1	+235 - Last Log

Author

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

Content

...	...	@@ -1,36 +1,16 @@
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 this release, our new log alerting will be available! Please find out more about it **LINK**. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).
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.235 - Last Log||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.
	5	+====Minor changes====
	6	+* Manage - Alerting: We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well. Please check out our [[release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]] for the migration actions, and our new **ML LINK** about the design.
	7	+* Manage - Alerting: We have improved the visibility of titles of larger columns in the new Alerting page.
	8	+* Create - Flow Designer: Some configuration options have been added to our SMB connectors that will solidify the connections with a SMB share:
	9	+** It is now possible to add a local filter to the SMB inbound channel adapter.
	10	+** It is now possible to add a 'Request handler advice chain' to the SMB outbound channel adaptor, SMB outbound gateway, FTP outbound gateway and SFTP outbound gateway.
	11	+* All: We no longer support our legacy Mendix connector (< version 4.x).
12	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	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		-
	14	+* Design - Flow Designer: The delete and download buttons in Resources have been re-aligned such that their positions are consistent when switching from view to edit mode. (#1381)
	15	+* Design - Flow Testing: The error that is sometimes thrown while switching between traces in flowtester is fixed. (#1521)
	16	+* Deploy - Releases: The performance of selecting a runtime when editing properties in Deploy has been improved. (#1124)