4d
diff --git a/‎crowdin.yml‎
Lines changed: 2 additions & 2 deletions b/‎crowdin.yml‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/API/HTTPAgentClass.md‎
Lines changed: 17 additions & 8 deletions b/‎docs/API/HTTPAgentClass.md‎
Lines changed: 17 additions & 8 deletions
diff --git a/‎docs/API/HTTPRequestClass.md‎
Lines changed: 5 additions & 4 deletions b/‎docs/API/HTTPRequestClass.md‎
Lines changed: 5 additions & 4 deletions
diff --git a/‎docs/API/SessionClass.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/API/SessionClass.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/API/overview.md‎
Lines changed: 0 additions & 22 deletions b/‎docs/API/overview.md‎
Lines changed: 0 additions & 22 deletions
diff --git a/‎docs/Backup/log.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Backup/log.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Concepts/operators.md‎
Lines changed: 3 additions & 1 deletion b/‎docs/Concepts/operators.md‎
Lines changed: 3 additions & 1 deletion
diff --git a/‎docs/Concepts/quick-tour.md‎
Lines changed: 9 additions & 0 deletions b/‎docs/Concepts/quick-tour.md‎
Lines changed: 9 additions & 0 deletions
diff --git a/‎docs/Desktop/building.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Desktop/building.md‎
Lines changed: 1 addition & 1 deletion
@@ -3,8 +3,8 @@ files:
     ignore:
       - /docs/preprocessing.conf
       - /docs/commands-legacy/*.*
-      - /docs/WritePro/commands-legacy/*.*
       - /docs/*-legacy/*.*
+      - /docs/WritePro/*-legacy/*.*
     translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%
   - source: /i18n/en/docusaurus-plugin-content-docs/*.json
     ignore:
@@ -14,7 +14,7 @@ files:
     ignore:
       - /versioned_docs/**/preprocessing.conf
       - /versioned_docs/**/commands-legacy/*.*
-      - /versioned_docs/**/WritePro/commands-legacy/*.*
+      - /versioned_docs/**/WritePro/*-legacy/*.*
       - /versioned_docs/version-18/
       - /versioned_docs/**/*-legacy/*.*
     translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/**/%original_file_name%
 
@@ -41,6 +41,14 @@ Since HTTPAgent is a shareable object, you can add one to a singleton class so y
 
 <!-- REF #4D.HTTPAgent.new().Syntax -->**4D.HTTPAgent.new**( { *options* : Object } ) : 4D.HTTPAgent<!-- END REF -->
 
+<details><summary>History</summary>
+
+|Release|Changes|
+|---|---|
+|21|Support of *storeCertificateName* property|
+
+</details>
+
 
 <!-- REF #4D.HTTPAgent.new().Params -->
 |Parameter|Type||Description|
@@ -68,13 +76,14 @@ HTTPAgent options will be merged with [HTTPRequest options](HTTPRequestClass.md#
 
 |Property|Type|Default|Description|
 |---|---|---|---|
-| keepAlive              |Boolean | true      |Activates keep alive for the agent                                            |
-| maxSockets             |Integer| 65535     |Maximum number of sockets per server                                                 |
-| maxTotalSockets        |Integer| 65535     |Maximum number of sockets for the agent                                     |
-| timeout                |Real| undefined |If defined, timeout after which an unused socket is closed                   |
-| certificatesFolder     |Folder| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) |Sets the active client certificates folder for the requests using the agent |
-| minTLSVersion          |Text| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) |Sets the minimum version of TLS for the requests using this agent            |
-| protocol               |Text| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) |Protocol used for the requests using the agent                              |
+| certificatesFolder|Folder| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) |Sets the active client certificates folder for the requests using the agent. Can be overriden by "storeCertificateName" (see below)|
+| keepAlive  |Boolean | true      |Activates keep alive for the agent  |
+| maxSockets  |Integer| 65535     |Maximum number of sockets per server |
+| maxTotalSockets  |Integer| 65535     |Maximum number of sockets for the agent |
+| minTLSVersion  |Text| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) |Sets the minimum version of TLS for the requests using this agent|
+| protocol |Text| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) |Protocol used for the requests using the agent |
+|storeCertificateName|Text|undefined|(Windows only) Name of the OS certificate store (e.g. "LocalMachine") from where to use certificates instead of those in the certificates folder for the requests using the agent. If the certificate store is not found, an error is returned. For more information, see [this blog post](https://blog.4d.com/https-requests-now-support-windows-certificate-store).|
+| timeout |Real| undefined |If defined, timeout after which an unused socket is closed  |
 | validateTLSCertificate |Boolean| undefined (see default value in [HTTPRequest.new()](HTTPRequestClass.md#options-parameter)) | validateTLSCertificate for the requests using the agent|
 
 :::note
@@ -91,7 +100,7 @@ Creating the HTTPAgent:
 var $options:={}
 $options.maxSockets:=5 //5 is the maximum number of sockets per server
 $options.maxTotalSockets:=10 //10 is the maximum number of sockets for the agent
-$options.validateTLSCertificate:=True //To validate the sever's certificate
+$options.validateTLSCertificate:=True //To validate the server's certificate
 
 var $myAgent:=4D.HTTPAgent.new($options)
 
 
@@ -81,6 +81,7 @@ HTTPRequest objects provide the following properties and functions:
 
 |Release|Changes|
 |---|---|
+|21|Support of *storeCertificateName* property|
 |20|TLS validation by default |
 |19 R7|Support of *automaticRedirections* and *decodeData* properties |
 
@@ -134,7 +135,7 @@ In the *options* parameter, pass an object that can contain the following proper
 |agent|[4D.HTTPAgent](HTTPAgentClass.md)|HTTPAgent to use for the HTTPRequest. Agent options will be merged with request options (request options take precedence). If no specific agent is defined, a global agent with default values is used.|Global agent object|
 |automaticRedirections|Boolean|If true, redirections are performed automatically (up to 5 redirections are handled, the 6th redirection response is returned if any)|True|
 |body|Variant|Body of the request (required in case of `post` or `put` requests). Can be a text, a blob, or an object. The content-type is determined from the type of this property unless it is set inside the headers|undefined|
-|certificatesFolder|[Folder](FolderClass.md)|Sets the active client certificates folder|undefined|
+|certificatesFolder|[Folder](FolderClass.md)|Sets the active client certificates folder. Can be overriden by "storeCertificateName" (see below).|undefined|
 |dataType|Text|Type of the response body attribute. Values: "text", "blob", "object", or "auto". If "auto", the type of the body content will be deduced from its MIME type (object for JSON, text for text, javascript, xml, http message and url encoded form, blob otherwise)|"auto"|
 |decodeData|Boolean|If true, the data received in the `onData` callback is uncompressed|False|
 |encoding|Text|Used only in case of requests with a `body` (`post` or `put` methods). Encoding of the request body content if it's a text, ignored if content-type is set inside the headers|"UTF-8"|
@@ -148,9 +149,10 @@ In the *options* parameter, pass an object that can contain the following proper
 |onTerminate|[Function](FunctionClass.md)|Callback when the request is over. It receives two objects as parameters (see below)|undefined|
 |protocol|Text|"auto" or "HTTP1". "auto" means HTTP1 in the current implementation|"auto"|
 |proxyAuthentication|[authentication object](#authentication-object)|Object handling proxy authentication|undefined|
-|serverAuthentication|[authentication object](#authentication-object)|Object handling server authentication|undefined|
 |returnResponseBody|Boolean|If false, the response body is not returned in the [`response` object](#response). Returns an error if false and `onData` is undefined|True|
-|timeout|Real|Timeout in seconds. Undefined = no timeout|Undefined|
+|serverAuthentication|[authentication object](#authentication-object)|Object handling server authentication|undefined|
+|storeCertificateName|Text|(Windows only) Name of the OS certificate store (e.g. "LocalMachine") from where to use certificates instead of those in the certificates folder. If the certificate store is not found, an error is returned. For more information, see [this blog post](https://blog.4d.com/https-requests-now-support-windows-certificate-store).|undefined|
+|timeout|Real|Timeout in seconds. undefined = no timeout|undefined|
 |validateTLSCertificate|Boolean|If false, 4D does not validate the TLS certificate and does not return an error if it is invalid (i.e. expired, self-signed...). Important: In the current implementation, the Certification Authority itself is not verified.|True|
 
 
@@ -167,7 +169,6 @@ Here is the sequence of callback calls:
 
 1. `onHeaders` is always called once
 2. `onData` is called zero or several times (not called if the request does not have a body)
-
 3. If no error occured, `onResponse` is always called once
 4. If an error occurs, `onError` is executed once (and terminates the request)
 5. `onTerminate` is always executed once
 
@@ -146,7 +146,7 @@ The `.createOTP()` function <!-- REF #SessionClass.createOTP().Summary -->create
 
 For more information about the OTP tokens, please refer to [this section](../WebServer/sessions.md#session-token-otp).
 
-By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan* (the minimum value is 10 seconds, *lifespan* is reset to 10 if a smaller value is passed). If an expired token is used to restore a web user session, it is ignored. 
+By default, if the *lifespan* parameter is omitted, the token is created with the same lifespan as the [`.idleTimeOut`](#idletimeout) of the session. You can set a custom timeout by passing a value in seconds in *lifespan*. If an expired token is used to restore a web user session, it is ignored. 
 
 The returned token can then be used in exchanges with third-party applications or websites to securely identify the session. For example, the session OTP token can be used with a payment application. 
 
 
@@ -71,7 +71,7 @@ You must create another log file if you create a new data file. You must set or
 
 The [log file settings](settings.md#log-management) are based on two pieces of information: a boolean value and a path.
 
-1. **Boolean Value**: indicating whether the "Use Log File" feature is enabled or disabled within the application. By default, the boolean value is stored in *catalog.4DCatalog*. However, when the [user settings](../Desktop/user-settings.md) are activated, the *catalog.4DCatalog* file configuration is overriden, and the boolean value can then be set either in the *Backup.4DSettings* file [next to the data file](../Project/architecture.md#settings-user-data) or the *Backup.4DSettings* file [in the project folder](../Project/architecture.md#settings-user) (see also the `JournalFileEnabled` xml backup key documentation on [doc.4d.com](https://doc.4d.com)).
+1. **Boolean Value**: indicating whether the "Use Log File" feature is enabled or disabled within the application. By default, the boolean value is stored in *catalog.4DCatalog*. However, when the [user settings](../settings/overview.md#user-settings) are activated, the *catalog.4DCatalog* file configuration is overriden, and the boolean value can then be set either in the *Backup.4DSettings* file [next to the data file](../Project/architecture.md#settings-user-data) or the *Backup.4DSettings* file [in the project folder](../Project/architecture.md#settings-user) (see also the `JournalFileEnabled` xml backup key documentation on [doc.4d.com](https://doc.4d.com)).
 
 2. **Path**: a string pointing to where the log file is located. The log file path is always stored in the linked data file.
 
 
@@ -95,7 +95,9 @@ The following compound assignment operators are supported:
 ||Time *= Number |Number |`$t1*=5 //$t1:=$t1*5`|
 ||Picture *= Number|Picture|`$p1*=5 //$p1:=$p1*5 (resize $p1 by 5)`|
 
-These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) (except pictures as object properties or collection elements).
+These operators apply on any [assignable expressions](quick-tour.md#assignable-vs-non-assignable-expressions) except:
+- pictures as object properties or collection elements,
+- array index variables.
 
 The operation "source `operator` value" is not strictly equivalent to "source := source `operator` value" because the expression designating the source (variable, field, object property, collection element) is only evaluated once. For example, in such expression as `getPointer()->+=1` the `getPointer` method is called only once.
 
 
@@ -431,3 +431,12 @@ In 4D, the following escape sequences can be used:
 In the following example, the **Carriage return** character (escape sequence `\r`) is inserted in a statement in order to obtain a dialog box:
 
 `ALERT("The operation has been completed successfully.\rYou may now disconnect.")`
+
+
+## Writing conventions
+
+The following conventions are used in the 4D language documentation:
+
+- the `{ }` characters (braces) indicate optional parameters. For example, `.delete( { option : Integer } )` means that the *option* parameter may be omitted when calling the function.
+- the `{ ; ...param }` notation indicates an unlimited number of parameters. For example, `.concat( value : any { ;...valueN } ) : Collection` means that an unlimited number of values of any type can be passed to the function.
+- the `any` keyword is used for parameters that can be of any type (number, text, boolean, date, time, object, collection...).
@@ -1,6 +1,6 @@
 ---
 id: building
-title: Build Application
+title: Application Builder
 ---
 
 4D includes an application builder to create a project package (final build). This builder simplifies the finalization and deployment process for 4D compiled applications. It automatically handles the specific features of different operating systems and facilitates the deployment of client-server applications.