Changes for page 234 - Alert Adventures

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-233 - Policy Polish
	1	+207 - Aligned State

Content

...	...	@@ -1,22 +1,44 @@
1		-During our recent sprint cycle, We did a hackathon again so we have a lot of bug fixes! The visibility of several buttons has been improved, as well as pop-ups and search functionalities. Find out all below!
	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.233 - Policy Polish||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		-====New features====
6		-* Login: Our password policy has been updated such that the minimum length is 14 characters, other requirements have remained the same. All users will be required to update their password when logging in. You will not be able to close this popup until your password has been updated successfully.
7	7
8		-====Minor changes====
9		-* Create - Flow Designer: We have added two additional configuration options to the SMB session factory support object.
10		-** Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected.
11		-** Force SMB version 2: We have added the option to enforce the usage of SMB version 2. This effectively disables backwards-compatible version negotiation.
12		-* Deploy - Architecture: Several improvements for our failover functionality have been done:
13		-** We have improved the warning message for the balance failover deployment plan step, making it more clear how to solve this issue should it occur during your deployment.
14		-** We have added the option to manually initiate the failover balancing process, saving you from having to execute your deployment. This action can be found in Deploy Architecture, when right clicking on the white canvas.
15		-** We have added a visualization of connector systems that are pending a failover enable or disable in Deploy Architecture. Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment.
	6	+=====Minor changes=====
16	16
	8	+* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
	9	+* Create - Framework: The framework used in the flow designer has been updated, improving performance.
	10	+* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
	11	+* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
	12	+* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
	13	+* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
	14	+* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
	15	+* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
	16	+* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	17	+* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
	18	+* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
	19	+* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
	20	+* 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)
	21	+* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
	22	+* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
	23	+* 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.
	24	+* 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.
	25	+
	26	+
	27	+
17	17	====Bug fixes====
18		-* Create - Flow Designer: If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing.
19		-* Create - Flow Designer: The XML to flat file and flat file to XML transformers have been restyled, such that they are similar to all other components.
20		-* Create - Flow Designer: We fixed an issue where the browser page would get frozen when editing a flow component.
21		-* Manage - Explore: When clicking the queue browser button, the user will not be redirected to the home page anymore.
22	22
	30	+* 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.
	31	+* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
	32	+* 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.
	33	+* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
	34	+* 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)
	35	+* 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.
	36	+* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
	37	+* 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.
	38	+* 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".
	39	+
	40	+
	41	+
	42	+=====Infra and image changes=====
	43	+
	44	+* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.