Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 84.1
edited by Erik Bakker
on 2023/05/26 08:40
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 -198 - Great Migration
1 +206 - Situational Deployment
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -1,23 +1,44 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
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.198 - Great Migration.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 +
5 5  =====Minor changes=====
6 6  
7 -* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8 -* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9 -* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10 -* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11 -* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12 -* Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
13 -* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14 -* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
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.
15 15  
29 +
16 16  ====Bug fixes====
17 17  
18 -* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
19 -* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
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.
20 20  
21 -====Remarks====
22 22  
23 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
41 +
42 +=====Infra and image changes=====
43 +
44 +* No infra and/or image changes is this release.