Changes for page 243 - Migration Magic

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-196 - The Last Post
	1	+241 - Wild West

Content

...	...	@@ -1,38 +1,31 @@
1		-Here's our first release of this quarter. We have delivered additional small (bug) fixes in this release and released the Live Flow testing feature. The last is a real improvement during the development process of a flow. Furthermore, you will find several improvements in the way of work for nextGen environments.
	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.196 - The Last Post.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=====
	5	+====Minor Changes====
6	6
7		-* Create - Flow Testing: so far, the Flow Testing allows test eMagiz flows by defining the testing point on the starts and the end points and comparing the actual and expected messages. In this release, “Live Mode Testing” is introduced, making it possible to test communication with real endpoint. That means that an “http output gateway” can be marked in “Live Mode”, if so, the http output gateway will send its http request to the real endpoint and received the result so we can go further with testing.
	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.
8	8
9		-=====Minor changes=====
10		-
11		-* Deploy - Architecture: The topics are now ordered alphabetically and the runtimes will now get the same order as design architecture (after ‘apply to environment’)
12		-* Create - Flow designer: CDM edit right is applied to the message definition in Create phase. You can not change CDM message definition, Gateway message definition, even Event streaming message definition without the proper right.
13		-* Deploy - Architecture: We improved the auto-healing feature of AWS machines. The new generation JMS server runtimes always start before other runtimes are ran.
14		-* Administration-User management: Company contact can edit permissions of models that fall under child companies
15		-* Administration: Contracts page removed
16		-* Create-Flow designer: Model resources tab removed on resources page when adding an resource to a validating filter.
17		-* Deploy - Releases: We reduced the time it takes to prepare a release, before it can be deployed. The process of building runtime images has been optimized.
18		-* Deploy - Releases: We have improved editing properties in releases for runtimes that are 3rd generation compatible.
19		-* Design - Store: You are able to see some warning messages when you import a transformation from store. Because your imported transformation is required some information from the related store fragment. You should include that store fragment to avoid a breaking transformation in Create phase after importing. Afterward, we will update your existing flow component transformer to make it work correctly.
20		-* Design - Store: We updated importing to help you avoiding an error during importing store item that will break your message definition in some special cases.
21		-* Create - Store: We excluded automatically resources that are not good enough from the exporting wizard. Then you will easy to recognize a problem and avoid creating unusable store item.
22		-* Flow Designer: Resources in "Unused resources" section can be marked as used for the case that the resources are referred by components through property placeholders or in custom spel expressions.
23		-* Create - API Gateway: We fixed an issue where an optional query parameter would cause failed requests, if that parameter was not supplied. Please reset your entry flow to apply the fix.
24		-* Create - API Gateway: We fixed an issue where API-Key secured requests would fail with error code 500 instead of code 401, if no API-Key was supplied. Please reset your entry flow to apply the fix.
25		-* Design - Store: We fixed an issue that you import the message definition(s) and a specialized DataType of imported message definition(s) are not matched with the exported message definition(s). Now, they are matched and your transformation won't get issues.
26		-* Create-Resources: When viewing a resource, its full name will be shown, removing the need to download the resource in order to obtain its name
27		-* Create - Flow designer: Improve responsiveness of resources tab at right panel
28		-* Manage - Explore: New button to delete queue is added and only visible for Expert Service (Admin)
29		-
30	30	====Bug fixes====
31	31
32		-* Create - Flow designer: Improved help texts of various flow components related to key-/truststores and their usage. They now better explain what you need them for and mention important security considerations.
33		-* Create - Flow designer: Various small (cosmetic) fixes and changes in the edit pages of some flow components to make them more consistent with similar pages.
34		-* Manage/Event streaming statistics. For some models, (some) topic data did not show in the graphs.
35		-* Deploy - Releases: We fixed an issue, where after removing containers from a machine, during execution of the deployment plan, the removed containers are not recognized as change, causing the ‘Deploy machine’ step to be skipped.
36		-
37		-====Remarks====
38		-
	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)