Skip to Content

Changes for page 248 - Smooth Sailing

Last modified by Erik Bakker on 2025/06/30 13:33
From version 270.1
edited by Erik Bakker
on 2025/06/30 09:43
Change comment: There is no comment for this version
To version 138.1
edited by Carlijn Kokkeler
on 2023/10/23 16:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -248 - Smooth Sailing
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,46 @@
1 -This release introduces a new [[cloud template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of cloud we offer that connects you to our latest carwash. In addition, we have several improvements within the platform that enhance the user experience and improve interaction with the platform. See below for the details.
1 +In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.248 - Smooth Sailing.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -==== Major changes ====
5 +=====New features=====
6 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
6 6  
7 -* General - Cloud Template: A new [[cloud template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]], for every type of cloud we offer, is available that enables connections to be switched to the updated carwash.
8 -* Create - Transformation: Users are allowed to move operations freely, except for Static Input, which must always be the first operation.
9 -** Deleting the Static Input operation is not allowed if there are other operations in the row.
10 -** An error message is presented in the alert tab if there is a mismatch between the input and output of an operation to show that the order is inconsistent. The alerts can be pressed to open the edit or view screen of the operation that is causing the inconsistency.
8 +=====Minor changes=====
11 11  
12 -==== Minor changes ====
10 +* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
11 +* Create - Framework: The framework used in the flow designer has been updated, improving performance.
12 +* Deploy - Architecture: The description users see when adapting the 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. (#1009)
14 +* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
15 +* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 +* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17 +* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18 +* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 +* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 +* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21 +* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
22 +* 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. (#1069)
23 +* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24 +* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
25 +* 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.
26 +* 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.
13 13  
14 -* Permissions - History: The export of a model ‘permissions’ tab now has a logical name. (#857)
15 -* Design - Message Mapping: Users can now refresh their Design message mappings. (#848)
16 -* Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646)
17 -* Deploy - Releases: Users can now add every type of flow to their release. (#948)
18 -* Deploy - Containers: The successful deletion pop-up is prevented from showing when the process is unsuccessful. This action occurred when a user tries to delete an empty container with hidden flows attached. (#1481)
19 -* Deploy - User Management: For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager.
20 -** Prevent auto-fill on specific fields by renaming labels
21 -** Applied styling to hide the Keeper button in input fields where undesired.
28 +
29 +
30 +====Bug fixes====
31 +
32 +* 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.
33 +* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
34 +* 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.
35 +* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
36 +* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
37 +* 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.
38 +* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
39 +* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
40 +* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
41 +
42 +
43 +
44 +=====Infra and image changes=====
45 +
46 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.