Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59
From version 113.1
edited by Carlijn Kokkeler
on 2023/10/11 13:38
Change comment: There is no comment for this version
To version 98.1
edited by Erik Bakker
on 2023/07/17 21:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +201 - Be Informed
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,43 +1,30 @@
1 -In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
1 +In the last sprint cycle, we focused on planning the upcoming quarter, finishing up, and working on the Hackathon to fix several smaller items.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.201 - Be Informed.WebHome||target= "blank"]].
4 4  
5 -
6 6  =====Minor changes=====
7 7  
8 -* Design - Framework: The framework used in the flow designer has been updated to the latest version.
9 -* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier.
10 -* 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.
11 -* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
12 -* Deploy - Architecture: The title of the'apply to environment' action for changing 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.
14 -* Deploy - Deployment plan: A change in the memory settings of the JMS triggers a redeployment of the container.
15 -* Deploy - Logging: New logging feature enabling us to make better choices in deprecating old encryption standards.
16 -* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
17 -* Deploy - Release properties: The description of a property can be changed by editing the property.
18 -* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
19 -* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
20 -* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
21 -* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment.
22 -* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
23 -* 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.
24 -* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default.
25 -* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
26 -* 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 of the action.
27 -* 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.
7 +* Portal - Menu: The back button is changed to have text on it to make the navigation much clearer. (#949)
8 +* Design-Architecture: Topic Storage detail page contains help text. (#994)
9 +* Design - API Endpoint Specification: Improved UI and added independent scroll functionality. (#832)
10 +* Design - API Gateway: Small styling improvement on the "Edit integration page." (#954)
11 +* Create - Flow Designer: When deleting one or multiple components, you cannot change the selection before confirming or canceling the delete action. (#969)
12 +* Create - Migrate to 3rd Generation: If one or more flows break during migration, a popup will inform the flows containing errors after the migration. (#983)
13 +* Deploy-User management: The user that makes a change is recorded in history instead of the user that applies to the environment. (#979)
14 +* Deploy-Architecture: Upon pressing the “Apply to the environment” button, a confirmation page is shown. All changes made in the portal that will affect your running environment are listed here. These changes can be applied to the environment or reverted. (#828)
15 +** Changes made in Deploy Architecture with an effect on your running environment will only be listed when they are made after this release.
16 +** Changes with a direct effect will not be listed (for example, restarting a machine).
28 28  
29 -
30 30  ====Bug fixes====
31 31  
32 -* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
33 -* 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.
34 -* Design - Store: We fixed an issue that static copies were missing when importing store items.
35 -* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
36 -* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release.
37 -* Manage - Monitoring: It is now possible to search on messages partially in Manage Monitoring.
38 -* 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.
20 +* Design - Solutions: We fixed an issue that displayed a message mapping error despite having a passthrough API gateway. (#935)
21 +* Design - Settings: The full length of the contract number can now be registered. (#958)
22 +* Create - Migrate to 3rd Generation: Components used in Gen 2 flows that can be used in Gen 3 will not block migration. (#982)
23 +* Deploy - Deployment plan: We fixed an issue that the list of installing flows did not show in the left pane when you deploy a release version to install/start/stop some flows into your runtimes. (#990)
24 +* Deploy - User Management: As a user with view-only rights in Deploy/User management, you can now double-click on a user to open its details. (#972)
25 +* Manage - Manage Dashboards: The screen loading speed is significantly improved for all models. This is most noticeable for larger models. (#964)
39 39  
40 -
41 41  =====Infra and image changes=====
42 42  
43 -* No infra and/or image changes is this release.
29 +* Changed the endpoint for sending error messages to the eMagiz Control Tower.
30 +* Updated the Spring version of the gateway supporting deploy and manage phase operations.