Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 62.1
edited by Erik Bakker
on 2023/04/11 08:29
Change comment: There is no comment for this version
To version 114.1
edited by Eva Torken
on 2023/10/11 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -1,34 +1,44 @@
1 -As a quarter has come to a close we went silent for a couple of weeks to plan ahead for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with good spirit after solving several smaller feedback items and bugs reported by you. In this and the upcoming release several of those stories will be included. On top of that we introduce various improvements to our API Gateway pattern and to our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the various improvements.
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.195 - Easter Party.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 -* 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)
9 -
10 10  =====Minor changes=====
11 11  
12 -* Design - Architecture: New calculation for topic size is applied and the feedback on topic retentions bytes has more information.
13 -* 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 use custom error handling on your event processors.
14 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
15 -* Deploy - User Management: Roles are sorted alphabetically. (#806)
16 -* 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.
17 -* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and chart, and made minor visual improvements.
18 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
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 on 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.
19 19  
29 +
20 20  ====Bug fixes====
21 21  
22 -* Generic: We fixed an issue in that you may see a screen with a broken styling when switching among phases.
23 -* Create - Flow Designer: Removed the option to create a new resource on the resource selection popup of a simple XSD schema support object.
24 -* 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)
25 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filenames (>100 characters).
26 -* Deploy - Releases: You need edit rights in the test environment of the deploy phase to execute the “Update flows to latest versions” action.
27 -* Manage - Dashboard: We update the view to visualize the split entries after you migrate combined entries.
28 -* 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 it occurred (#825)
29 -* Manage - Logging: Reduced the occurrence of 'Failed to send to Elastic' log messages which trigger alerts. (#898)
30 -* Manage - Alerting: Editable column shows the correct value.
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 - 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.
38 +* Manage - Monitoring: It is now possible to search on messages partially in Manage Monitoring.
31 31  
32 -====Remarks====
33 33  
34 -* 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 incompatible with the selected feature until the migration is finished.
41 +
42 +=====Infra and image changes=====
43 +
44 +* No infra and/or image changes is this release.