Merge branch 'development' into production

Author: katarzyna-koltun-mx

content/en/docs/refguide/runtime/custom-settings/_index.md

@@ -146,7 +146,6 @@ The settings below influence the behavior of the log files. These settings can o
 | <a id="DataStorageEnableDiagnostics" href="#DataStorageEnableDiagnostics">DataStorage.EnableDiagnostics</a> | This setting can be used to generate a uniqueness constraint violation report. | false |
 | <a id="UseNetworkTimeout" href="#UseNetworkTimeout">UseNetworkTimeout</a> | This setting is applied to PostgreSQL. It affects the timeout mechanism used when reserving new ids for Mendix objects. If set to true, the socket level request timeout is used. In that case, the request timeout is handled within the operating system. If set to false, the timeout is handled by Mendix runtime. For other databases, timeouts are always handled by Mendix runtime. | true |
 | <a id="JdbcLoginTimeout" href="#JdbcLoginTimeout">JdbcLoginTimeout</a> | This setting defines the database connection establishment time in milliseconds. | 5000 (5 seconds) |
-| <a id="SynchronizationCleanupInterval" href="#SynchronizationCleanupInterval">com.mendix.offline.SynchronizationCleanupInterval</a> | This setting defines how often objects of type `System.OfflineSynchronizationHistory` are cleaned up. | 90 (90 days) |
 | <a id="DataStorageOptimizeSecurityColumns" href="#DataStorageOptimizeSecurityColumns">DataStorage.OptimizeSecurityColumns</a> | When true, query columns generated to evaluate XPath constraints in access rules are optimized to `true` if the runtime can determine that the value will always be true for the objects that the query returns. This is almost always an improvement, but we have seen cases where the PostgreSQL query planner has worse performance for the simpler query. | true |
 
 ### Connection Pooling {#connection-pooling}
@@ -286,6 +285,8 @@ The settings below influence the behavior of the Mendix web client.
 | Name | Description | Default Value |
 | --- | --- | --- |
 | <a id="EnableKeepAlive" href="#EnableKeepAlive">EnableKeepAlive</a> | Defines whether the web client sends a keep alive request every `SessionTimeout`/2 milliseconds in order to prevent a session timeout. Each click in the browser also acts as `KeepAlive`. Disabling this property will result in the user being logged out automatically after `SessionTimeout` milliseconds of inactivity (default 10 minutes), even if the browser remains open. See `SessionTimeout` in the next section for more information. | true |
+| <a id="DeleteAutoCommittedObjectsAfterSync" href="#DeleteAutoCommittedObjectsAfterSync">com.mendix.offline.DeleteAutoCommittedObjectsAfterSync</a> | Defines if auto-committed created during offline synchronization will be deleted from the database immediately.<br/>*Deprecated – should only be changed if you have compatibility issues upgrading from Mendix version 9.* | true |
+| <a id="SynchronizationCleanupInterval" href="#SynchronizationCleanupInterval">com.mendix.offline.SynchronizationCleanupInterval</a> | This setting defines how often objects of type `System.OfflineSynchronizationHistory` are cleaned up. | 90 (90 days) |
 | <a id="commendixwebuiAuthTokenTimeout" href="#commendixwebuiAuthTokenTimeout">com.<wbr>mendix.<wbr>webui.<wbr>AuthTokenTimeout</a> | Determines how many minutes your token will remain valid before re-authenticating using your full credentials.  If no value is set, the token will expire after One year. | Introduced in Mendix 11.3. Use [com.<wbr>mendix.<wbr>webui.<wbr>HybridAppLoginTimeOut](#commendixwebuiHybridAppLoginTimeOut) in earlier versions. |
 | <a id="commendixwebuiHybridAppLoginTimeOut" href="#commendixwebuiHybridAppLoginTimeOut">com.<wbr>mendix.<wbr>webui.<wbr>HybridAppLoginTimeOut</a> | Legacy alias of <a id="commendixwebuiAuthTokenTimeout" href="#commendixwebuiAuthTokenTimeout">com.<wbr>mendix.<wbr>webui.<wbr>AuthTokenTimeout</a> | |
 | <a id="commendixwebuiFeedbackSizeWarningThreshold" href="#commendixwebuiFeedbackSizeWarningThreshold">com.<wbr>mendix.<wbr>webui.<wbr>FeedbackSizeWarningThreshold</a> | A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as "instructions" in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. | 5000 |

content/en/docs/refguide/runtime/custom-settings/tricky-custom-runtime-settings.md

@@ -28,7 +28,6 @@ The following custom settings can be configured:
 | Name | Description | Default value |
 | --- | --- | --- |
 | `SessionTimeout` | Defines after how much time the session becomes invalid (in milliseconds). After that timeout, a session becomes applicable for removal. The session won't be destroyed until the next time the cluster manager evaluates the active sessions. | 600000 (10 minutes) |
-| `com.mendix.offline.DeleteAutoCommittedObjectsAfterSync` | Defines if auto-committed created during offline synchronization will be deleted from the database immediately. | true |
 | `ClusterManagerActionInterval` | The interval (in milliseconds) used for performing all cluster manager actions. These actions include unblocking users and removing invalid sessions. If nothing is specified, the interval is half the `SessionTimeout`. | 300000 (5 minutes) |
 | `SessionKeepAliveUpdatesInterval` | Defines after how much time expired sessions can be removed from the database. | one sixth of the value configured for the `SessionTimeout` setting; if the `SessionTimeout` is not set, this value defaults to 100000 (100 seconds) |
 

content/en/docs/releasenotes/workstation/_index.md

@@ -10,6 +10,37 @@ cascade:
 
 These release notes cover changes made to the [Mendix Workstation](/mendix-workstation/).
 
+## 3.7.0
+
+### Release date: May 21, 2026
+
+### Workstation Management
+
+#### New features
+
+* Smart configuration updates (auto-refresh) - You can now choose if your workstation configurations should automatically update when changes are made, or if you prefer to trigger updates manually. This gives you more control and ensures your workstations always have the correct settings with less effort.
+* Real-time workstation status - The Workstation Management UI now shows the live configuration status of each Workstation Client, letting you quickly see if a workstation is **Up to Date** or **Outdated**. This provides immediate insight into your deployment's health.
+* Enhanced Serial Device detection settings - You can now configure Workstation Management to identify your serial devices using more reliable information like their Friendly Name, Serial Number, or Manufacturer. This helps your Workstation Clients reliably find and connect to the correct serial device, even if its port number changes.
+
+#### Improvements
+
+* Configurable auto-refresh behavior - We have provided options for how auto-refresh works, including default settings for workspaces and how clients respond in both automatic and manual modes. This allows for flexible management of your workstation configurations.
+
+#### Bug Fixes
+
+* UI inconsistencies - We have fixed several visual inconsistencies in the Management UI, particularly improving the display and user experience when using dark mode. This makes the interface cleaner and more consistent for everyone.
+
+### Workstation Client
+
+#### New Features
+
+* Automatic Client startup - The Workstation Client application now automatically launches silently in the background when your system starts up. This ensures your workstations are always ready to go without needing manual intervention after a reboot.
+* Smart Serial Device finder - The client can now use the Friendly Name, Serial Number, or Manufacturer to find and connect to serial devices. This means your client can reliably connect to the right device even if its assigned port changes.
+
+#### Improvements
+
+* Granular configuration change response - The client now handles configuration changes more smoothly and with less downtime. This means your stations will experience fewer interruptions and apply new settings more efficiently.
+
 ## 3.6.1
 
 ### Release date: April 28, 2026
@@ -64,7 +95,7 @@ If more than one station is found for a given computer name during bulk registra
 
 For more information, see [Nanoflows](/mendix-workstation/build-app/#javascript-actions) and [Widgets](/mendix-workstation/build-app/#widgets).
 
-#### Improvement
+#### Improvements
 
 * The **Model Peripheral** entity is now a specialization of the **Device** entity and no longer requires association.
 * Calling `GetStation` is no longer required to initiate the Workstation Connector. It is only required to read the station configuration.

content/en/docs/workstation/wks-batch-registration.md

@@ -13,6 +13,10 @@ The registration process is a necessary first step when enabling this crucial fu
 
 Mendix Workstation supports both individual registration of local Workstation clients, and bulk rollouts for large production environments.
 
+{{% alert color="info" %}}
+After a Workstation Client is registered, any changes that you make in Workstation Management (such as adding new devices, or setting the **Detect Card Readers** toggle to **Off**) will be immediately synchronized with the Client. To change this behavior, see [Client's Auto-Refresh](/mendix-workstation/installation/#auto-refresh).
+{{% /alert %}}
+
 ## Registering a Single Workstation Client
 
 If you are developing or testing Workstation configurations, you can register a single Workstation Client for your local computer by performing the following steps:

content/en/docs/workstation/wks-installation.md

@@ -96,14 +96,16 @@ The **Stations** page now shows your station's status as **Computer Registered**
 
     {{< figure src="/attachments/workstation/wks-install10.png" class="no-border" >}}
 
+Any changes that you make in Workstation Management (such as adding new devices, or setting the **Detect Card Readers** toggle to **Off**) will be immediately synchronized with the Workstation Client. To change this behavior, see [Client's Auto-Refresh](#auto-refresh).
+
 ### Configuring and Testing Virtual Devices
 
 After registering your computer, test your connectivity by creating a pair of virtual devices: a TCP/IP server that will emulate a device, and a TCP/IP client that will connect to the emulated device.
 
 #### Creating a TCP/IP Server
 
 1. Go to [Mendix Workstation Management](https://workstation.home.mendix.com/).
-2. In the **Station** page, click **Add Device**.
+2. In the **Station Details** page, click **Add Device**.
 3. Select **TCP/IP Server** as the **Device Type**, and then click **Next**.
 4. In the **Device Name** field, enter **Test Server**
 5. In the **Device Class** field, select or create a class (for example, *Virtual*), and then click **Next**.
@@ -119,7 +121,7 @@ The emulated device, a local TCP/IP server listening on port 1705, is added to t
 #### Creating a TCP/IP Client
 
 1. Go to [Mendix Workstation Management](https://workstation.home.mendix.com/).
-2. In the **Station** page, click **Add Device**.
+2. In the **Station Details** page, click **Add Device**.
 3. Select **TCP/IP Client** as the **Device Type**, and then click **Next**.
 4. In the **Device Name** field, enter **Test Client**, and then click **Next**.
 5. In the **Device Class** field, select or create a class (for example, *Virtual*), and then click **Next**.
@@ -153,7 +155,7 @@ Different device types have different requirements for the message syntax. For m
 
 ### Quitting the Workstation Client
 
-The **Close** button closes the Client window but does not terminate the application; it continues to run in the background. To completely quit the Client, right-click its icon in the Windows systray and select **Quit**. This action is only available if [Developer Mode](#developer-mode) is enabled. Alternatively, the Workstation Client process can always be stopped via Windows Task Manager.
+The Workstation Client runs automatically at system startup. The **Close** button closes the Client window but does not terminate the application; it continues to run in the background. To completely quit the Client, right-click its icon in the Windows systray and select **Quit**. This action is only available if [Developer Mode](#developer-mode) is enabled. Alternatively, the Workstation Client process can always be stopped via Windows Task Manager.
 
 ## Advanced Configurations
 
@@ -167,6 +169,8 @@ Navigate to the **Settings** page in a workspace to configure settings that are
 
 #### Log Settings
 
+Log settings are available in Workstation Management at **Settings > Log Settings**.
+
 The Workstation Client always stores logs to the file system it is installed on (c.f. [Troubleshooting - Workstation Client](/mendix-workstation/troubleshooting/#workstation-client)). No logs are send to the Workstation Management. However, you can configure the log level and retention policy of all the Workstation Clients that are registered to stations in the workspace.
 
 ##### Log Level
@@ -186,9 +190,21 @@ Verbosity and thus log file size increases with each log level. To constrain thi
 
 Modify these settings to the needs of your logging policy, especially if you require to keep debug level logs in production for retrospective troubleshooting.
 
+#### Client's Auto-Refresh {#auto-refresh}
+
+Auto-refresh settings are available in Workstation Management at **Settings > Client's Auto-Refresh**.
+
+By default, the Workstation Client operates in auto-refresh mode. That is, any changes made to the configuration in Workstation Management are immediately reflected in the Client. 
+
+To change this behavior, set the **Auto-Refresh Mode** toggle to **Off**. You can then force the configuration to refresh by clicking **Refresh on Computer** in Workstation Management, or by clicking **Refresh** in the Workstation Client.
+
+The **Check Interval** setting is only available when the auto-refresh mode is enabled. It specifies how often a Workstation Client that is disconnected due to a web socket failure should automatically refresh its configuration by polling Workstation Management. By default, this happens every 60 minutes.
+
 #### Local Device Testing
 
-By default, the Workstation Management is pre-configured as an allowed app to connect to the Workstation Client on the **Test your Station** page in a workspace. To disable this, navigate to the tab "Local Device Testing" on the **Settings** page and toggle it off. 
+Local device testing settings are available in Workstation Management at **Settings > Local Device Testing**.
+
+By default, the Workstation Management is pre-configured as an allowed app to connect to the Workstation Client on the **Test your Station** page in a workspace. To disable this setting, toggle it off. 
 
 ### Workspace Team and Collaboration {#collaboration}