Changes for page 248 - Smooth Sailing
Last modified by Erik Bakker on 2025/06/30 13:33
From version 266.1
edited by Erik Bakker
on 2025/06/17 09:16
on 2025/06/17 09:16
Change comment:
There is no comment for this version
To version 270.1
edited by Erik Bakker
on 2025/06/30 09:43
on 2025/06/30 09:43
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -24 7-Help Out1 +248 - Smooth Sailing - Content
-
... ... @@ -1,12 +1,21 @@ 1 -This release focusesonhelpingourcommunity byimproving variousaspects ofourplatformin anticipationofsomeofthe larger featuresthat arejustaroundthecorner. So,withoutfurtherado,let's takealook atwhat'sonthemenutoday!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.24 7-Help Out.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 -==== Bugfixes ====5 +==== Major changes ==== 6 6 7 -* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614) 8 -* Design - System: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413) 9 -* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463) 10 -* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow are corrected so that the flow is deployed with the correct flow version and component list. (#1618) 11 -* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358) 12 -* Manage - Explore: The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524) 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. 11 + 12 +==== Minor changes ==== 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.