Merge pull request #11232 from mendix/MvM-AdvancedCustomSettings

Move offline sync settings to Web Client Settings section

Author: MarkvanMents

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) |