4d
diff --git a/‎docs/API/FileClass.md‎
Lines changed: 7 additions & 5 deletions b/‎docs/API/FileClass.md‎
Lines changed: 7 additions & 5 deletions
diff --git a/‎docs/API/FunctionClass.md‎
Lines changed: 4 additions & 4 deletions b/‎docs/API/FunctionClass.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/API/SessionClass.md‎
Lines changed: 15 additions & 3 deletions b/‎docs/API/SessionClass.md‎
Lines changed: 15 additions & 3 deletions
diff --git a/‎docs/API/WebFormClass.md‎
Lines changed: 3 additions & 3 deletions b/‎docs/API/WebFormClass.md‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/Admin/data-collect.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/Admin/data-collect.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/Admin/webAdmin.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Admin/webAdmin.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Concepts/quick-tour.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/Concepts/quick-tour.md‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/Debugging/debugging-remote.md‎
Lines changed: 1 addition & 1 deletion b/‎docs/Debugging/debugging-remote.md‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎docs/Desktop/building.md‎
Lines changed: 1 addition & 5 deletions b/‎docs/Desktop/building.md‎
Lines changed: 1 addition & 5 deletions
diff --git a/‎docs/Desktop/sessions.md‎
Lines changed: 7 additions & 7 deletions b/‎docs/Desktop/sessions.md‎
Lines changed: 7 additions & 7 deletions
@@ -554,6 +554,7 @@ You want to rename "ReadMe.txt" in "ReadMe_new.txt":
 
 |Release|Changes|
 |---|---|
+|21 R2|support of removeFluentUI|
 |20 R9|Read UUIDs in macOS executables|
 |20|Support of WinIcon|
 |19|Added|
@@ -570,7 +571,7 @@ You want to rename "ReadMe.txt" in "ReadMe_new.txt":
 
 #### Description
 
-The `.setAppInfo()` function <!-- REF #FileClass.setAppInfo().Summary -->writes the *info* properties as information contents of an application file<!-- END REF -->.
+The `.setAppInfo()` function <!-- REF #FileClass.setAppInfo().Summary -->writes the *info* properties as information contents of an application file<!-- END REF -->. It is designed for developers who want to customize their 4D application building chain.  
 
 The function can only be used with the following file types: **.plist** (all platforms), existing **.exe**/**.dll** (Windows), or **macOS executable**. If used with another file type or with a **.exe**/**.dll** file that does not already exist on disk, the function does nothing (no error is generated). 
 
@@ -600,14 +601,15 @@ Each valid property set in the *info* object parameter is written in the version
 
 |Property|Type|Comment|
 |---|---|---|
-|InternalName|Text||
-|ProductName|Text||
 |CompanyName|Text||
-|LegalCopyright|Text||
-|ProductVersion|Text||
 |FileDescription|Text||
 |FileVersion|Text||
+|InternalName|Text||
+|LegalCopyright|Text||
 |OriginalFilename|Text||
+|ProductName|Text||
+|ProductVersion|Text||
+|removeFluentUI|Boolean|Can only be used with a merged 4D application (.exe file). Pass True to replace the *manifest* referencing the embedded Windows App SDK (required for [Fluent UI rendering](../FormEditor/forms.md#fluent-ui-rendering)) and the *.pri* file with versions allowing the use of a Windows App SDK installed in the OS. Using a local SDK allows to reduce the size of the generated application (you also need remove the default embedded files). Passing False or omitting the property does nothing.|
 |WinIcon|Text|Posix path of .ico file. This property applies only to 4D generated executable files.|
 
 For all properties except `WinIcon`, if you pass a null or empty text as value, an empty string is written in the property. If you pass a value type different from text, it is stringified.
 
@@ -50,13 +50,13 @@ You can also execute a function using the [`apply()`](#apply) and [`call()`](#ca
 
 #### Passing parameters
 
-You can pass parameters to your formulas using a sequential parameter syntax based upon $1, $2...$n. For example, you can write:
+You can pass parameters to your formulas using a sequential parameter syntax based upon `$1, $2,...,$n`. The numbering of the $ parameters represents the order in which they will be passed to the formula. For example, you can write:
 
 ```4d
  var $f : Object
  $f:=New object
- $f.message:=Formula(ALERT("Hello "+$1))
- $f.message("John") //displays "Hello John"
+ $f.message:=Formula(ALERT("Hello "+$2+", "+$1))
+ $f.message("John";"Smith") //displays "Hello Smith, John"
 ```
 
 Or using the [.call()](#call) function:
@@ -65,7 +65,7 @@ Or using the [.call()](#call) function:
  var $f : Object
  $f:=Formula($1+" "+$2)
  $text:=$f.call(Null;"Hello";"World") //returns "Hello World"
- $text:=$f.call(Null;"Welcome to";String(Year of(Current date))) //returns "Welcome to 2019" (for example)
+ $text:=$f.call(Null;"Welcome to";String(Year of(Current date))) //returns "Welcome to 2026" (for example)
 ```
 
 #### Parameters to a single method
 
@@ -4,7 +4,7 @@ title: Session
 ---
 
 
-Session objects are returned by the [`Session`](../commands/session.md) command. These objects provide the developer with an interface allowing to manage the current user session and execute actions such as store contextual data, share information between session processes, launch session-related preemptive processes, or (web only) manage [privileges](../ORDA/privileges.md).
+Session objects are returned by the [`Session`](../commands/session.md) command. These objects provide the developer with an interface allowing to manage the current user session and execute actions such as store contextual data, share information between session processes, launch session-related preemptive processes, or (web context only) manage [privileges](../ORDA/privileges.md).
 
 
 :::tip Related blog posts
@@ -22,7 +22,7 @@ Session objects are returned by the [`Session`](../commands/session.md) command.
 
 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-web-sessions). They are used for Web connections (including and REST access), and are controlled by assigned [privileges](../ORDA/privileges.md).
+- [**Web user sessions**](WebServer/sessions.md): Web user sessions are available when [scalable sessions are enabled in your project](WebServer/sessions.md#enabling-web-sessions). They are used for Web connections (including REST access), and are controlled by assigned [privileges](../ORDA/privileges.md).
 - [**Desktop sessions**](../Desktop/sessions.md), which include: 
    - [**Remote user sessions**](../Desktop/sessions.md#remote-user-sessions): In client/server applications, remote users have their own sessions managed on the server.
    - [**Stored procedures sessions**](../Desktop/sessions.md#stored-procedure-sessions): Virtual user session for all stored procedures executed on the server.
@@ -98,6 +98,7 @@ This function does not remove **promoted privileges** from the web process, whet
 :::note
 
 Keep in mind that privileges only apply to the code executed through web accesses, whatever the [session type](#session-types) on which this function is executed.
+
 :::
 
 
@@ -192,6 +193,11 @@ If no privilege with *promoteId* was promoted using [`.promote()`](#promote) in
 
 If several privileges have been added to the web process, the `demote()` function must be called for each one with the appropriate *promoteId*. Privileges are stacked in the order they have been added to the process, it is recommended to unstack privileges in a LIFO (*Last In, First Out*) order.
 
+:::note
+
+Keep in mind that privileges only apply to the code executed through web accesses, whatever the [session type](#session-types) on which this function is executed.
+
+:::
 
 #### Example
 
@@ -526,6 +532,7 @@ The `.info` property <!-- REF #SessionClass.info.Summary -->describes the deskto
 
 - **Remote sessions** and **Stored procedure sessions**: The `.info` object is the same object as the one returned in the "session" property by the [`Process activity`](../commands/process-activity.md) command.
 - **Standalone sessions**: The `.info` object is the same object as the one returned by the [`Session info`](../commands/session-info.md) command.
+- **Web user sessions**: The `.info` object contains properties available for web user sessions. 
 
 
 The `.info` object contains the following properties:
@@ -586,7 +593,7 @@ The `.isGuest()` function <!-- REF #SessionClass.isGuest().Summary -->returns Tr
 
 :::note Compatibility
 
-With legacy sessions, `.isGuest()` returns True if the session has no privileges. 
+When the [*forcelogin* mode](../REST/authUsers.md#force-login-mode) is disabled, `.isGuest()` returns True if the session has no privileges. 
 
 :::
 
@@ -727,6 +734,11 @@ The function returns `false` if:
 In this case, the current web user session is left untouched (no session is restored). 
 
 
+:::note
+
+Keep in mind that privileges only apply to the code executed through web accesses, whatever the [session type](#session-types) on which this function is executed.
+
+:::
 
 
 #### Example
 
@@ -20,7 +20,7 @@ The `WebForm` class contains functions and properties allowing to handle your Qo
 
 ||
 |---|
-|[<!-- INCLUDE WebFormClass.componentName.Syntax -->](#componentname)<br/><!-- INCLUDE #WebFormClass.componentName.Summary -->|
+|[<!-- INCLUDE WebFormClass.componentName.Syntax -->](#componentname)<br/><!-- INCLUDE WebFormClass.componentName.Summary -->|
 |[<!-- INCLUDE #WebFormClass.disableState().Syntax -->](#disablestate)<br/><!-- INCLUDE #WebFormClass.disableState().Summary -->|
 |[<!-- INCLUDE #WebFormClass.enableState().Syntax -->](#enablestate)<br/><!-- INCLUDE #WebFormClass.enableState().Summary -->|
 |[<!-- INCLUDE #WebFormClass.setError().Syntax -->](#seterror)<br/><!-- INCLUDE #WebFormClass.setError().Summary -->|
@@ -30,11 +30,11 @@ The `WebForm` class contains functions and properties allowing to handle your Qo
 
 ### *.componentName*
 
-<!-- REF #WebFormClass.componentName.Syntax -->***.componentName*** : [4D.WebFormItem](WebFormItemClass.md)<!-- END REF -->
+<!-- REF WebFormClass.componentName.Syntax -->***.componentName*** : [4D.WebFormItem](WebFormItemClass.md)<!-- END REF -->
 
 #### Description
 
-The components of web pages are <!-- REF #WebFormClass.componentName.Summary -->objects that are available directly as properties<!-- END REF --> of these web pages.
+The components of web pages are <!-- REF WebFormClass.componentName.Summary -->objects that are available directly as properties<!-- END REF --> of these web pages.
 
 The returned objects are of the [`4D.WebFormItem`](WebFormItemClass.md) class. These objects have functions that you can use to manage your components dynamically.
 
 
@@ -3,9 +3,9 @@ id: data-collect
 title: Data Collection
 ---
 
-To help us make our products always better, we automatically collect data regarding usage statistics on running 4D Server applications. Collected data is completely anonymous and data is transferred with no impact on the user experience. 
+To help us make our products always better, we automatically collect data regarding usage statistics on running 4D Server applications. Collected data is transferred with no impact on the user experience. No personal data is collected. For more information on 4D policy regarding personal data protection, please got to [this page](https://us.4d.com/privacy-policy).
 
-This page explains:
+The section below explains:
 
 - what information is collected,
 - where information is stored and when it is sent to 4D,
 
@@ -139,7 +139,7 @@ This option only appears if the Qodly Studio license is activated.
 
 ::: 
 
-This option enables user access to [Qodly Studio](../WebServer/qodly-studio.md) at the 4D application level. Note that you also need to [enable the access at every project level](../settings/web.md#enable-access-to-qodly-studio).
+This option enables user access to [Qodly Studio](developer.4d.com/qodly/) at the 4D application level. Note that you also need to [enable the access at every project level](../settings/web.md#enable-access-to-qodly-studio).
 
 :::note
 
 
@@ -438,6 +438,6 @@ In the following example, the **Carriage return** character (escape sequence `\r
 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* : Type}` notation indicates an unlimited number of parameters of the same type. For example, `.concat( value : any { ;...valueN : Text } ) : Collection` means that an unlimited number of values of any type can be passed to the function.
-- the `{; ...(*param* : Type ; *param2* : Type) }` notation indicates an unlimited number of groups of parameters. For example, `COLLECTION TO ARRAY ( collection : Collection ; array : Array {; propertyName : Text}{; ...(array : Array ; propertyName : Text) } )` means that an unlimited number of couple values or type array/text can be passed to the command.
 - the `any` keyword is used for parameters that can be of any type (number, text, boolean, date, time, object, collection...).
+- the `{; ...*param* : Type}` notation indicates an unlimited number of parameters of the same type. For example, `.concat( value : any { ;...valueN : any } ) : Collection` means that an unlimited number of values of any type can be passed to the function.
+- the `{; ...(*param* : Type ; *param2* : Type) }` notation indicates an unlimited number of groups of parameters. For example, `COLLECTION TO ARRAY ( collection : Collection ; array : Array {; propertyName : Text}{; ...(array : Array ; propertyName : Text) } )` means that an unlimited number of couple values of type array/text can be passed to the command.
@@ -20,7 +20,7 @@ Only one debugger can debug a 4D Server application at a given time. It is calle
 
 * the local 4D Server debugger (default) - if the server is not running headless.
 * the debugger of a remote 4D client - if the remote session has access to Design mode.
-* the [Qodly debugger](../WebServer/qodly-studio.md#using-qodly-debugger-on-4d-server) on 4D Server - if the server allows access to Qodly Studio. 
+* the [Qodly debugger](developer.4d.com/qodly/4DQodlyPro/debugging#using-qodly-debugger-on-4d-server) on 4D Server - if the server allows access to Qodly Studio. 
 * the **VS Code** debugger, provided you installed the [4D-Debugger](https://github.com/4d/4D-Debugger-VSCode) extension. 
 
 
 
@@ -494,14 +494,10 @@ A module is a built-in code library used by 4D to control specific features. If
 The following optional modules can be deselected:
 
 * **CEF**: Chromium embedded library. It is necessary to run [Web areas](../FormObjects/webArea_overview.md) that use the embedded rendering engine and [4D View Pro areas](../FormObjects/viewProArea_overview.md). Calling such areas when CEF is deselected will display blank areas and/or generate errors.
-* **MeCab**: Library used for text indexing in Japanese language (see this [settings paragraph](../settings/database.md#support-of-mecab-japanese-version)). Deselecting this module will force text indexes to be rebuilt in Japanese language.
-
-> If you deselect MeCab for an application in Japanese language used on heterogeneous platforms, make sure to deselect it on both client/server build and [client application build](#build-client-application) (for the concurrent platform), otherwise major malfunctions will occur in the application.
-
 * **SpellChecker**: Used for built-in [spellchecking features](../FormObjects/properties_Entry.md#auto-spellcheck) and commands available for input areas and 4D Write Pro areas.
 * **4D Updater**: Controls the [automatic update](#what-is-a-clientserver-application) of client parts and is used by the `SET UPDATE FOLDER` command for [automated server updates](#automatic-updating-of-server-or-single-user-applications).
 * **4D Qodly Pro and Data Explorer**: Includes [Qodly Studio and its web renderering features](https://developer.4d.com/qodly/) as well as the [Data Explorer](../Admin/dataExplorer.md). 
-
+* **Windows App Runtime**: Required for [Fluent UI rendering](../FormEditor/forms.md#fluent-ui-rendering) on Windows.
 
 ## Licenses & Certificate page
 
 
@@ -12,7 +12,7 @@ However, unlike the code executed in web user sessions, the code executed in des
 
 You can nevertheless [**share** a desktop session with a web session](#sharing-a-desktop-session-for-web-accesses) so that a desktop user can access your 4D application through a web interface, using for example Qodly pages and Web areas. 
 
-## Session types
+## Session types {#session-types}
 
 Desktop sessions include:
 
@@ -35,13 +35,13 @@ The following diagram shows the different session types and how they interact:
 
 
 
-## Remote user sessions
+## Remote user sessions {#remote-user-sessions}
 
 On the server, in "user processes" (i.e. processes related to remote users), the [`Session`](../commands/session.md) command returns a `session` object describing the current user session. This object is handled through the functions and properties of the [`Session` class](../API/SessionClass.md).
 
 :::note
 
-On a remote 4D, the `session` object always returns null.
+On a remote 4D, the [`Session`](../commands/session) command always returns null.
 
 :::
 
@@ -71,13 +71,13 @@ The remote user `session` object is available from:
 - Database methods such as [`On Server Open Connection`](../commands/on-server-open-connection-database-method) and [`On Server Close Connection`](../commands/on-server-close-connection-database-method).
 
 
-## Stored procedure sessions
+## Stored procedure sessions {#stored-procedure-sessions}
 
 On the server, all [stored procedures](https://doc.4d.com/4Dv20/4D/20/Stored-Procedures.300-6330553.en.html) share the same virtual user session. 
 
 ### Usage
 
-You can share data between all processes of a store procedure session using the [`session.storage`](../API/SessionClass.md#storage) shared object.
+You can share data between all processes of a stored procedure session using the [`session.storage`](../API/SessionClass.md#storage) shared object.
 
 ### Availability
 
@@ -88,7 +88,7 @@ The `session` object of stored procedures is available from:
 - Database methods such as [`On Server Startup`](../commands/on-server-startup-database-method) and [`On Server Shutdown`](../commands/on-server-shutdown-database-method).
 
 
-## Standalone sessions
+## Standalone sessions {#standalone-sessions}
 
 A standalone session is the single-user session running when you work locally with 4D.  
 
@@ -102,7 +102,7 @@ The `session` object of a standalone is available from all methods and code exec
 
 
 
-## Sharing a desktop session for web accesses
+## Sharing a desktop session for web accesses {#sharing-a-desktop-session-for-web-accesses}
 
 Desktop sessions can be used to handle web accesses to the application by the same user and thus, manage their [privileges](../ORDA/privileges.md). This possibility is particularly useful for Client/Server applications where [Qodly pages](https://developer.4d.com/qodly/4DQodlyPro/pageLoaders/pageLoaderOverview) are used for the interface, running on remote machines. With this configuration, your applications have modern CSS-based web interfaces but still benefit from the power and simplicity of integrated client/server development. In such applications, Qodly pages are executed within standard 4D [Web areas](../FormObjects/webArea_overview.md).