Skip to Content

Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 335.2
edited by Carlijn Kokkeler
on 2024/11/04 11:32
Change comment: Update document after refactoring.
To version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -233 - Policy Polish
1 +204 - Found It
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,22 +1,18 @@
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 the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.232 - Bug Busters||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.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.
5 +=====Minor changes=====
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.
7 +* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers.
16 16  
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  
11 +* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
12 +* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
13 +* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release.
14 +* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
15 +
16 +=====Infra and image changes=====
17 +
18 +* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.