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	+207 - Aligned State

Author

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

Content

...	...	@@ -1,31 +1,46 @@
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 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.207 - Aligned State .WebHome||target="blank"]].
4	4
5		-====Minor Changes====
	5	+=====New features=====
	6	+* State generation: New state generation features have been added. Please check out [[V2.0.0>>Main.Release Information.Runtime Images.V2.0.0||target="blank"]] [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
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.
	8	+=====Minor changes=====
13	13
	10	+* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
	11	+* Create - Framework: The framework used in the flow designer has been updated, improving performance.
	12	+* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
	13	+* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
	14	+* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
	15	+* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
	16	+* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
	17	+* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
	18	+* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	19	+* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
	20	+* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
	21	+* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
	22	+* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
	23	+* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
	24	+* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
	25	+* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
	26	+* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
	27	+
	28	+
	29	+
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)
	32	+* Design - Store: We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
	33	+* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
	34	+* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
	35	+* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
	36	+* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
	37	+* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
	38	+* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
	39	+* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
	40	+* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
	41	+
	42	+
	43	+
	44	+=====Infra and image changes=====
	45	+
	46	+* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.