Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29

From version 336.1
edited by Carlijn Kokkeler
on 2024/11/04 11:33
Change comment: There is no comment for this version
To version 58.1
edited by Erik Bakker
on 2023/03/14 08:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -233 - Policy Polish
1 +194 - Giant Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,22 +1,33 @@
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 +The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
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.194 - Giant Leap.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 +=====New features=====
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 +* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8 +* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers and waking up a cloud slot will start those containers. (#889)
16 16  
10 +=====Minor changes=====
11 +
12 +* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you are using custom error handling on your event processors or not.
13 +* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
14 +* Deploy - User Management: Roles are sorted alphabetically. (#806)
15 +* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
16 +* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and graph and made some small visual improvements.
17 +* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
18 +
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  
21 +* Generic: We fixed an issue that you may see a screen with a broken styling when switching among phases.
22 +* Create - Flow Designer: Removed the option to create a new resource on resource selection pop-up of simple XSD schema support object.
23 +* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
24 +* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filename (>100 characters).
25 +* Deploy - Releases: You need edit rights in test environment of deploy phase to execute “Update flows to latest versions” action.
26 +* Manage - Dashboard: We update the view to visualize the split entries after you do a migration a combined entries.
27 +* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet is occurred (#825)
28 +* Manage - Logging: Reduced the occurance of 'Failed to send to Elastic' log messages which triggers alerts. (#898)
29 +* Manage - Alerting: Editable column shows the correct value.
30 +
31 +====Remarks====
32 +
33 +* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours, because of data migration. You will get an error stating that the version is not compatible with the selected feature until migration has finished.