Changes for page 243 - Migration Magic

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+241 - Wild West

Content

...	...	@@ -1,32 +1,31 @@
1		-The release finished many new improvements to our 3rd generation runtime offering and fixed various annoying bugs and minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
	1	+In the last sprint, we have released a lot in terms of usability improvements while working within the various phases of eMagiz and 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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.241 - Wild West.WebHome||target="blank"]].
4	4
5		-=====New features=====
6		-* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7		-* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your JMS server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
	5	+====Minor Changes====
8	8
9		-=====Major changes=====
	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 **no longer allowed** in the technical name. The technical name can only consist of lowercase 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 creation. 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.
10	10
11		-* 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.
12		-
13		-=====Minor changes=====
14		-
15		-* 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.
16		-* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17		-* 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.
18		-* Create - Flow Designer: when importing a store item from another partner, an error popup will be shown instead of the default error message.
19		-* Deploy - Releases: The activate release functionality improved performance for 3rd generation models.
20		-* 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)
21		-* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22		-* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings," where you can enable/disable both HTTP and control bus per runtime.
23		-* 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.
24		-
25	25	====Bug fixes====
26		-* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27		-* 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)
28		-* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in the setup step.
29		-* Deploy - Containers: We fixed an issue that the container overview does not show the entry flows which should run on that container. (#863)
30		-* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31		-* 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.
32	32
	16	+* Capture - Add System: A loading bar is displayed before showing the pop-up when a user tries to create or edit a system. (#1228)
	17	+* Capture - Edit System: When editing a system, the validation now considers that the name cannot be an empty string. (#1562)
	18	+* Design - Message Definition: Two minor improvements are introduced:
	19	+** The widget prevents users from adding the same message attribute within a message definition multiple times.
	20	+** When adding a new message entity within your message definition and expanding the existing message definition, it doesn’t throw an exception when the user presses the Save button multiple times in a short time frame.
	21	+* Design - Catalog: When creating the Swagger JSON, all custom examples users add will be shown correctly when displaying the 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 can untransfer a flow even when there is a property attached to the flow. (#1590)
	24	+* Create - Add Integrations: When an integration is transferred from the Create phase, the flow, flow versions, and the corresponding integration in the Deploy phase are cleaned.
	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 an existing property description. (#1526)
	29	+* Deploy - Environment Template: Fixed a bug that caused upgrading a fully on-premise environment to exclude some machines incorrectly.
	30	+* Manage - Queue Browser: Switching environments when exploring a queue in Manage → Explore 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 flows using code mappings from encountering errors when stopping their runtime while messages are still being processed. (#1550)