Skip to content

Commit f61500d

Browse files
committed
Remove deprecated Microflows.RemoveVariableOnDeleteObjectsActivity runtime setting
1 parent ab3c4f8 commit f61500d

File tree

1 file changed

+0
-1
lines changed
  • content/en/docs/refguide/runtime/custom-settings

1 file changed

+0
-1
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,6 @@ The following custom settings can be configured:
6868
| <a id="httpclientMaxConnectionsTotal" href="#httpclientMaxConnectionsTotal">http.<wbr>client.<wbr>MaxConnectionsTotal</a> | The [maximum number of connections allowed across all routes](https://hc.apache.org/httpcomponents-client-4.5.x/current/httpclient/apidocs/org/apache/http/impl/client/HttpClientBuilder.html#setMaxConnTotal(int)) for the call REST service and call web service activities.<br/>{{% alert color="warning" %}}If you change the value of `http.client. MaxConnectionsPerRoute`, you will need to increase this value in line with that, up to a maximum of 250.{{% /alert %}} | 20 |
6969
| <a id="JavaKeyStorePassword" href="#JavaKeyStorePassword">JavaKeyStorePassword</a> | Password for the default Java keystore. | changeit |
7070
| <a id="LongLivedSessionTimeout" href="#LongLivedSessionTimeout">LongLivedSessionTimeout</a> | This setting is the same as `SessionTimeout`, but specific to offline-first progressive web apps. | 604800000 (7 days) |
71-
| <a id="MicroflowsRemoveVariableOnDeleteObjectsActivity" href="#MicroflowsRemoveVariableOnDeleteObjectsActivity">Microflows.<wbr>RemoveVariableOnDeleteObjectsActivity</a> | Defines if the pre-Mendix 10.17 behavior should be enabled where list references were removed after execution of a **Delete object(s)** microflow activity in a loop.<br/><br/>Before Mendix 10.17 list references were silently unusable after a **Delete object(s)** microflow activity in a loop. Newly added items were not propagated to activities using these variables. That is fixed in Mendix 10.17. If this setting is 'true' it temporarily brings back the old behavior. | `false` |
7271
| <a id="MyScheduledEvents" href="#MyScheduledEvents">MyScheduledEvents</a> | A comma-separated string with the names of the events. Please don't forget the name of the module (a name can be, for example, `CRM.UpdateCustomerStatistics`). | |
7372
| <a id="ScheduledEventExecution" href="#ScheduledEventExecution">ScheduledEventExecution</a> | Specify which scheduled events should be executed. Choices are `ALL`, `NONE`, or `SPECIFIED`. In the case of `SPECIFIED`, enumerate the scheduled events using the `MyScheduledEvents` configuration option described below. {{% alert color="warning" %}}This setting cannot be configured when running locally. To enable and disable scheduled events when running locally, please use the 'Enabled' setting on the [Scheduled Events execution properties](/refguide/scheduled-events/) in Studio Pro.{{% /alert %}} | NONE |
7473
| <a id="SessionKeepAliveUpdatesInterval" href="#SessionKeepAliveUpdatesInterval">SessionKeepAliveUpdatesInterval</a> | Defines how often a runtime writes session LastActive dates in its memory back to 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) |

0 commit comments

Comments
 (0)