Skip to Content

Changes for page 248 - Smooth Sailing

Last modified by Erik Bakker on 2025/06/30 13:33
From version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
Change comment: There is no comment for this version
To version 273.1
edited by Erik Bakker
on 2025/06/30 13:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +248 - Smooth Sailing
Content
... ... @@ -1,19 +1,25 @@
1 -In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.203 - Fast Paced.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.248 - Smooth Sailing.WebHome||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +==== Major changes ====
6 6  
7 -* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023)
8 -* Manage - Alerting: Identifiers of triggers are now visible in the edit screen.
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. (#1269)
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.
9 9  
10 -====Bug fixes====
12 +==== Minor changes ====
11 11  
12 -* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016)
13 -* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597)
14 -* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release.
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 (Routes): Various help texts have been updated on this pop-up to better clarify what these fields are used for. (#1536)
17 +** Prevent auto-fill on specific fields by renaming labels
18 +** Applied styling to hide the Keeper button in input fields where undesired.
15 15  
16 -=====Infra and image changes=====
20 +==== Bug fixes ====
17 17  
18 -* Infrastructure: Tightened security policies for a more secure infrastructure.
19 -* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower
22 +* Deploy - User Management: For the new screens related to DSH user management, we have fixed some undesired behavior caused by Keeper Password Manager.
23 +* Deploy - Architecture: Previously canceled containers, machines, and connectors in Design → Architecture are no longer shown in the 'Apply to Environment' overview in Deploy. (#1646)
24 +* 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)
25 +* Deploy - Releases: Users can now add every type of flow to their release. (#948)