4d
diff --git a/‎.github/workflows/build.yml‎
Lines changed: 3 additions & 0 deletions b/‎.github/workflows/build.yml‎
Lines changed: 3 additions & 0 deletions
diff --git a/‎.github/workflows/workflow-build.yml‎
Lines changed: 1 addition & 0 deletions b/‎.github/workflows/workflow-build.yml‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎commandList.json‎
Lines changed: 1351 additions & 29 deletions b/‎commandList.json‎
Lines changed: 1351 additions & 29 deletions
diff --git a/‎docs/API/CollectionClass.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/API/CollectionClass.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/API/CryptoKeyClass.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/API/CryptoKeyClass.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/API/DataClassClass.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/API/DataClassClass.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/API/EntityClass.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/API/EntityClass.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/API/EntitySelectionClass.md‎
Lines changed: 8 additions & 2 deletions b/‎docs/API/EntitySelectionClass.md‎
Lines changed: 8 additions & 2 deletions
diff --git a/‎docs/API/HTTPRequestClass.md‎
Lines changed: 3 additions & 0 deletions b/‎docs/API/HTTPRequestClass.md‎
Lines changed: 3 additions & 0 deletions
diff --git a/‎docs/API/SessionClass.md‎
Lines changed: 25 additions & 16 deletions b/‎docs/API/SessionClass.md‎
Lines changed: 25 additions & 16 deletions
@@ -11,3 +11,6 @@ on:
 jobs:
   workflow-build:
     uses: ./.github/workflows/workflow-build.yml
+    concurrency:
+      group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+      cancel-in-progress:  true
@@ -9,6 +9,7 @@ jobs:
     steps:
       - name: Get disk space
         run: |
+          df -h /
           sudo rm -rf \
           "$AGENT_TOOLSDIRECTORY" \
           /opt/google/chrome \
 
@@ -2229,8 +2229,8 @@ You can also pass a criteria parameter to define how the collection elements mus
 
 	|Constant|	Type|Value|Comment|
 	|---|---|---|---|
-	|ck ascending|Longint|0|Elements are ordered in ascending order (default)|
-	|ck descending|Longint|1|Elements are ordered in descending order
+	|ck ascending|Integer|0|Elements are ordered in ascending order (default)|
+	|ck descending|Integer|1|Elements are ordered in descending order
 
 	This syntax orders scalar values in the collection only (other element types such as objects or collections are returned unordered).
 
 
@@ -385,7 +385,7 @@ Contains the <!-- REF #CryptoKey.type.Summary -->name of the key type - "RSA", "
 |18 R4|Added
 </details>
 
-<!-- REF #CryptoKey.verify().Syntax -->**.verify**( *message* : Text ; *signature* : Text ; *options* : Object) : object<!-- END REF -->
+<!-- REF #CryptoKey.verify().Syntax -->**.verify**( *message* : Text ; *signature* : Text ; *options* : Object) : Object<!-- END REF -->
 
 
 <!-- REF #CryptoKey.verify().Params -->
 
@@ -726,9 +726,9 @@ The `data` object in each entry contains the following properties:
 
 |Property|Type|Description|
 |---|---|---|
-|__KEY|String|Primary key of the entity|
-|__STAMP|Longint|Timestamp of the entity in the database|
-|__TIMESTAMP|String|Stamp of the entity in the database (format is YYYY-MM-DDTHH:MM:SS:ms:Z)|
+|__KEY|Text|Primary key of the entity|
+|__STAMP|Integer|Timestamp of the entity in the database|
+|__TIMESTAMP|Text|Stamp of the entity in the database (format is YYYY-MM-DDTHH:MM:SS:ms:Z)|
 |dataClassAttributeName|Variant|If there is data in the cache for a dataclass attribute, it is returned in a property with the same type as in the database.|
 
 Data concerning related entities is stored in the cache of the data object.
 
@@ -148,7 +148,7 @@ The differences are returned as a collection of objects whose properties are:
 
 |Property name| Type| Description|
 |---|---|---|
-|attributeName| String| Name of the attribute
+|attributeName| Text| Name of the attribute
 |value|any - Depends on attribute type |Value of the attribute in the entity|
 |otherValue|any - Depends on attribute type|Value of the attribute in *entityToCompare*|
 
 
@@ -6,7 +6,10 @@ title: EntitySelection
 
 An entity selection is an object containing one or more reference(s) to [entities](ORDA/dsMapping.md#entity) belonging to the same [Dataclass](ORDA/dsMapping.md#dataclass). An entity selection can contain 0, 1 or X entities from the dataclass -- where X can represent the total number of entities contained in the dataclass.
 
-Entity selections can be created from existing selections using various functions of the [`DataClass` class](DataClassClass.md) such as [`.all()`](DataClassClass.md#all) or [`.query()`](DataClassClass.md#query), or functions of the `EntityClass` class itself, such as [`.and()`](#and) or [`orderBy()`](#orderby). You can also create blank entity selections using the [`dataClass.newSelection()`](DataClassClass.md#newselection) function or the [`Create new selection`](../commands/create-entity-selection.md) command.
+Entity selections can be created from existing selections using various functions of the [`DataClass` class](DataClassClass.md) such as [`.all()`](DataClassClass.md#all) or [`.query()`](DataClassClass.md#query), or functions of the `EntityClass` class itself, such as [`.and()`](#and) or [`orderBy()`](#orderby). You can also create blank entity selections using the [`dataClass.newSelection()`](DataClassClass.md#newselection) function or the [`Create entity selection`](../commands/create-entity-selection.md) command.
+
+
+
 
 ### Summary
 
@@ -49,6 +52,9 @@ Entity selections can be created from existing selections using various function
 |[<!-- INCLUDE #EntitySelectionClass.toCollection().Syntax -->](#tocollection)<br/><!-- INCLUDE #EntitySelectionClass.toCollection().Summary -->|
 
 
+#### See also
+
+[`USE ENTITY SELECTION`](../commands/use-entity-selection.md)
 
 
 <!-- REF EntitySelectionClass.index.Desc -->
@@ -2183,7 +2189,7 @@ $sum:=$sel.sum("salary")
 
 </details>
 
-<!-- REF #EntitySelectionClass.toCollection().Syntax -->**.toCollection**( { *options* : Integer { ; *begin* : Integer { ; *howMany* : Integer } } ) : *Collection*<br/>**.toCollection**( *filterString* : Text {; *options* : Integer { ; *begin* : Integer { ; *howMany* : Integer }}} ) : *Collection*<br/>**.toCollection**( *filterCol* : Collection {; *options* : Integer { ; *begin* : Integer { ; *howMany* : Integer }}} ) : *Collection*<!-- END REF -->
+<!-- REF #EntitySelectionClass.toCollection().Syntax -->**.toCollection**( { *options* : Integer { ; *begin* : Integer { ; *howMany* : Integer } } ) : Collection<br/>**.toCollection**( *filterString* : Text {; *options* : Integer { ; *begin* : Integer { ; *howMany* : Integer }}} ) : Collection<br/>**.toCollection**( *filterCol* : Collection {; *options* : Integer { ; *begin* : Integer { ; *howMany* : Integer }}} ) : Collection<!-- END REF -->
 
 
 <!-- REF #EntitySelectionClass.toCollection().Params -->
 
@@ -486,4 +486,7 @@ The `wait()` function <!-- REF #HTTPRequestClass.wait().Summary -->waits for the
 If a *time* parameter is passed, the function will wait at most the defined number of seconds.
 
 If the response from the server has already arrived, the function returns immediately.
+
+During a `.wait()` execution, callback functions are executed, whether from other `HTTPRequest` or [`SystemWorker`](SystemWorkerClass.md) instances, or other [`CALL WORKER`](../commands-legacy/call-worker.md) calls. You can exit from a `.wait()` by calling [`terminate()`](#terminate) from a callback.
+
 <!-- END REF -->
@@ -8,11 +8,13 @@ Session objects are returned by the [`Session`](../commands/session.md) command.
 
 ### Session types
 
-Three types of sessions are supported by this class:
+The following types of sessions are supported by this class:
 
 - [**Web user sessions**](WebServer/sessions.md): Web user sessions are available when [scalable sessions are enabled in your project](WebServer/sessions.md#enabling-sessions). They are used for Web and REST connections, and can be assigned privileges.
 - [**Remote client user sessions**](../Desktop/clientServer.md#remote-user-sessions): In client/server applications, remote users have their own sessions managed on the server.
 - [**Stored procedures session**](https://doc.4d.com/4Dv20R5/4D/20-R5/4D-Server-and-the-4D-Language.300-6932726.en.html): All stored procedures executed on the server share the same virtual user session.
+- [**Standalone session**](../Project/overview.md#development): Local session object returned in single-user application (useful in development and test phases of client/server applications). 
+
 
 :::note
 
@@ -67,7 +69,7 @@ The availability of properties and functions in the `Session` object depends on
 
 :::note
 
-This function does nothing and always returns **True** with remote client and stored procedure sessions.
+This function does nothing and always returns **True** with remote client, stored procedure, and standalone sessions.
 
 :::
 
@@ -148,7 +150,7 @@ $expiration:=Session.expirationDate //eg "2021-11-05T17:10:42Z"
 
 The `.getPrivileges()` function <!-- REF #SessionClass.getPrivileges().Summary -->returns a collection of all the privilege names associated to the session<!-- END REF -->.
 
-With remote client and stored procedure sessions, this function returns a collection only containing "WebAdmin".
+With remote client, stored procedure and standalone sessions, this function returns a collection only containing "WebAdmin".
 
 
 :::info
@@ -252,7 +254,7 @@ $privileges := Session.getPrivileges()
 
 The `.hasPrivilege()` function <!-- REF #SessionClass.hasPrivilege().Summary -->returns True if the *privilege* is associated to the session, and False otherwise<!-- END REF -->.
 
-With remote client and stored procedure sessions, this function always returns True, whatever the *privilege*.
+With remote client, stored procedure and standalone sessions, this function always returns True, whatever the *privilege*.
 
 
 #### Example
@@ -286,12 +288,12 @@ End if
 
 #### Description
 
-The `.id` property contains <!-- REF #SessionClass.id.Summary -->the unique identifier (UUID) of the session on the server<!-- END REF -->. This unique string is automatically assigned by the server for each session and allows you to identify its processes.
+The `.id` property contains <!-- REF #SessionClass.id.Summary -->the unique identifier (UUID) of the user session<!-- END REF -->. With 4D Server, this unique string is automatically assigned by the server for each session and allows you to identify its processes.
 
 
 :::tip
 
-You can use this property to get the [`.storage`](#storage) object of a session thanks to the [`Session storage`](../commands-legacy/session-storage.md) command.  
+You can use this property to get the [`.storage`](#storage) object of a session thanks to the [`Session storage`](../commands/session-storage.md) command.  
 
 :::
 
@@ -366,28 +368,34 @@ End if
 
 :::note
 
-This property is only available with remote client and stored procedure sessions.
+This property is only available with remote client, stored procedure, and standalone sessions.
 
 :::
 
-The `.info` property <!-- REF #SessionClass.info.Summary -->describes the remote client or stored procedure session on the server<!-- END REF -->.
+The `.info` property <!-- REF #SessionClass.info.Summary -->describes the remote client or stored procedure session on the server, or the standalone session<!-- END REF -->.
+
+:::note
+
+- The `.info` object is the same object as the one returned in the "session" property by the [`Process activity`](../commands/process-activity.md) command for remote client and stored procedure sessions.
+- The `.info` object is the same object as the one returned by the [`Session info`](../commands/session-info.md) command for a standalone session.
+
 
-The `.info` object is the same object as the one returned by the [`Get process activity`](https://doc.4d.com/4dv20/help/command/en/page1495.html) command for remote client and stored procedure sessions.
+:::
 
 The `.info` object contains the following properties:
 
 |Property|Type|Description|
 |---|---|---|
-|type|Text|Session type: "remote" or "storedProcedure"|
+|type|Text|Session type: "remote", "storedProcedure", "standalone"|
 |userName|Text|4D user name (same value as [`.userName`](#username))|
-|machineName|Text|Remote sessions: name of the remote machine. Stored procedures session: name of the server machine|
+|machineName|Text|Remote sessions: name of the remote machine. Stored procedures session: name of the server machine. Standalone session: name of the machine|
 |systemUserName|Text|Remote sessions: name of the system session opened on the remote machine.  |
 |IPAddress|Text|IP address of the remote machine|
 |hostType|Text|Host type: "windows" or "mac"|
-|creationDateTime|Date ISO 8601|Date and time of session creation|
+|creationDateTime|Date ISO 8601|Date and time of session creation. Standalone session: date and time of application startup|
 |state|Text|Session state: "active", "postponed", "sleeping"|
 |ID|Text|Session UUID (same value as [`.id`](#id))|
-|persistentID|Text|Session's persistent ID|
+|persistentID|Text|Remote sessions: Session's persistent ID|
 
 :::note
 
@@ -423,7 +431,7 @@ Since `.info` is a computed property, it is recommended to call it once and then
 
 :::note
 
-This function always returns **False** with remote client and stored procedure sessions.
+This function always returns **False** with remote client, stored procedure, and standalone sessions.
 
 :::
 
@@ -472,7 +480,7 @@ End if
 
 :::note
 
-This function does nothing and always returns **False** with remote client and stored procedure sessions.
+This function does nothing and always returns **False** with remote client, stored procedure, and standalone sessions.
 
 :::
 
@@ -552,7 +560,7 @@ This property is **read only** itself but it returns a read-write object.
 
 :::tip
 
-You can get the `.storage` property of a session using the [`Session storage`](../commands-legacy/session-storage.md) command.  
+You can get the `.storage` property of a session using the [`Session storage`](../commands/session-storage.md) command.  
 
 :::
 
@@ -608,6 +616,7 @@ The `.userName` property contains <!-- REF #SessionClass.userName.Summary -->the
 
 - With web sessions, this property is an empty string by default. It can be set using the `privileges` property of the [`setPrivileges()`](#setprivileges) function.
 - With remote and stored procedure sessions, this property returns the same user name as the [`Current user`](../commands-legacy/current-user.md) command.
+- With standalone sessions, this property contains "designer" or the name set with the [`SET USER ALIAS`](../commands-legacy/set-user-alias.md) command. 
 
 This property is **read only**.