Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59
From version 100.1
edited by Erik Bakker
on 2023/08/01 15:02
Change comment: There is no comment for this version
To version 113.1
edited by Carlijn Kokkeler
on 2023/10/11 13:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,36 +1,43 @@
1 -In the last sprint cycle, we focused on finishing our work on the release properties functionality introduced in this release. On top of that, we have some additional smaller feedback items and bug fixes coming out of the Hackathon for you.
1 +In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.202 - New Equilibrium.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 6  
7 -* Deploy - Releases: We removed two unnecessary release options: “Set release properties” and “Check properties. “ You can quickly update your properties via the Release properties overview.
8 -* Deploy - Releases: Before activating or deploying a new release, you should fill in all properties that relate to your deployment. If there are any properties without value, we will show them to you. Then you can update them and continue your deployment.
9 -* Deploy - Properties: This tab 'Properties' for managing properties is deprecated as of Release 202. As a result, it cannot be used anymore to manage properties. You can manage your properties via the 'Releases' overview. On this overview, you can select the wrench icon on the 'Create phase release' to find the property management overview. For more information about the management of properties and the related features, click on the right-bottom corner on 'Help and check out our documentation.
10 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture to host a MQTT broker in a failover (i.e., double lane) architecture. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
11 -
12 12  =====Minor changes=====
13 13  
14 -* Store - Export: "Store exporter" users can test their exported store items immediately without waiting for approval. (#1001)
15 -* Deploy - Releases: The infographic has been updated.
16 -* Deploy - Release Properties: Required properties are checked if they contain nested properties and are not missing values.
17 -* Deploy - Property release: Names of properties can be created/removed/edited.
18 -* Deploy - History: We deprecated the old page History, which displays the property changes in your model. The properties' history is on the Deploy phase's History page.
19 -* Deploy - Architecture: Changes made to AWS Slot settings are recorded in history. (#966)
20 -* Manage - Monitoring: Improved performance of 3rd generation runtime dashboards.
21 -* Infrastructure: Tightened security policies for a more secure infrastructure.
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.
22 22  
29 +
23 23  ====Bug fixes====
24 24  
25 -* Design - Import: Import into design from the store is possible, even if the integration is not in Create yet.
26 -* Create - Flow Designer: Improved validation on XPath header enricher. (#1005)
27 -* Create - Flow Designer: We fixed an issue that your flow fragment metadata disappeared when you canceled your changes of the existing flow fragment in your new version of the store item. (#989)
28 -* Create - Flow Designer: In some cases, when copying/pasting components into a flow, validation alerts would be displayed that did not belong to a component. This problem is now fixed. (#955)
29 -* Create - Flow Designer: We fixed an issue that prevents dragging and dropping an annotation from the left panel after a search from the search box. The speed of creating the dialog to enter the component’s name is also improved.
30 -* Create - Flow Testing: Properties will not disappear from the list when canceling changes on a default property value. (#913)
31 -* Create - Flow Testing: Users with view rights can edit test case names, descriptions, and property values. (#973)
32 -* Deploy - Architecture: The runtimes will display the number of connected flows, not "Zero."
33 -* Deploy - Architecture (Runtime Settings): Moved the delete button to the right side of the page and fixed the bug in the help text.
34 -* Deploy - Releases: We fixed an issue that prevented you from seeing a comparison message when hovering over an exit gate flow of the API pattern if you compare two release versions in Deploy. (#839)
35 -* Deploy - Releases: We improved the loading buttons of releases on the right pane by Order (Ascending).
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.
36 36  
40 +
41 +=====Infra and image changes=====
42 +
43 +* No infra and/or image changes is this release.