Changes for page 243 - Migration Magic

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-241 - Wild West
	1	+191 - Fifty Fifty

Content

...	...	@@ -1,31 +1,36 @@
1		-In the last sprint, we have released a lot in terms of usability improvements both while working within the various phases of eMagiz as well as when deploying your hard work to the environment of your choice. As a result, we have a series of improvements and bug fixes for you to enjoy coming out of the hackathon. On top of that, we release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V330.WebHome||target="blank"]] containing a much needed improvement regarding deployment executions when working with state generation and code mappings on top of various improvements in our underlying code.
	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.241 - Wild West.WebHome||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====
	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.
6	6
7		-* Overall - Q&A Forum: When viewing a question, you can now easily copy the link to the question to your clipboard (#1471)
8		-* Capture - Add Integration: Removed the ‘remarks’ field from the ‘New Integration’ screen in Capture, because this field was not visible enough in the rest of the portal. (#1608)
9		-* Capture / Design: For new systems, message types, machines, tenants and models hyphens are not allowed in the technical name anymore. The technical name can only consist of lower case letters and digits and must start with a letter. This also applies to systems, message types and tenants that have not yet been transferred from design to create. The portal will give an error message while transferring and the hyphen has to be removed manually.
10		-* Create - Flow designer: Display name character limitations are visible in the validation feedback when adding new flow components (#1554)
11		-* Create - Resources: When trying to delete a message definition, the portal shows which transformation(s) use this message definition and should be deleted as well (#1616)
12		-* Deploy - Deployment Plan Execution: We have improved the stability of the deployment plan procedure.
	13	+=====Major changes=====
13	13
	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	+
14	14	====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.
15	15
16		-* Capture - Add System: When a user tries to creates a system or edits a system, loading bar is displayed before showing the pop-up. (#1228)
17		-* Capture - Edit System: When editing a system, the validation now takes into account that the name cannot be an empty string. (#1562)
18		-* Design - Message Definition: small improvements are introduced:
19		-** the widget can prevent user multiple message attributes on a message entity for the same attribute in datamodel.
20		-** when adding a new message entity to a current message entity, it doesn’t throw exception when user double click to many times in Save button
21		-* Design - Catalog: When exporting swagger json, in case an operation has example in request, the example will be shown correctly in swagger. (#1597)
22		-* Design - Solution Architecture: When modifying the number of runtimes of a system, the validation will now take into account that the value may not be empty (#1513)
23		-* Create - Add Integrations: Users are able to untransfer a flow even when there is a property attached to the flow. (#1590)
24		-* Create - Add Integrations: Flow, flow versions and the corresponding integration in the Deploy phase is cleaned when an integration is utransferred from the Create phase.
25		-* Create - Components: The browser page now displays the correct page title (#1509)
26		-* Create - Flow designer: When removing a wiretap from a channel, confirmation will only be asked once now. (#1549)
27		-* Create - Flow Designer: The default name of the REST template support object generated in passthrough API gateway operations now matches the (technical) name of the integration. (#1560)
28		-* Deploy - Properties: Fixed a bug where property descriptions were not updated when there was already a property description in place. (#1526)
29		-* Deploy - Environment Template: Fixed a bug where upgrading a fully on-premise environment would incorrectly exclude some machines.
30		-* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore now moves the user to the queue browser of the correct environment. (#1408)
31		-* Infra - Runtime Image: The cache used for code mappings is now properly started and stopped with the application. This prevents that flows using code mappings may encounter errors when stopping their runtime and messages were still processed. (#1550)