Changes for page 241 - Wild West

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-241 - Wild West
	1	+209 - Max Verstappen

Author

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

Content

...	...	@@ -1,31 +1,37 @@
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.
	1	+In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.209 - Max Verstappen.WebHome||target="blank"]].
4	4
5		-====Minor Changes====
	5	+=====Runtime release notes=====
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 **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.
	7	+There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. For specific information, please check out this link to the [[release notes>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime/eMagiz%20Mendix%20Connector%20-%206.0.2/]]
13	13
	9	+=====Minor changes=====
	10	+
	11	+* Design - Message Mapping: The button 'Import from Store' will directly open the store.
	12	+* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
	13	+* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
	14	+* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
	15	+* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
	16	+* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
	17	+* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	18	+* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
	19	+* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
	20	+* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
	21	+* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
	22	+* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
	23	+* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
	24	+* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
	25	+* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
	26	+
14	14	====Bug fixes====
15	15
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)
	29	+* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
	30	+* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
	31	+* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
	32	+* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
	33	+
	34	+
	35	+=====Infra and image changes=====
	36	+
	37	+* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.