Merge pull request #429 from doc4d/main

20.7

Author: arnaud4d

docs/API/OutgoingMessageClass.md

@@ -6,7 +6,7 @@ title: OutgoingMessage
 
 The `4D.OutgoingMessage` class allows you to build messages to be returned by your application functions in response to [REST requests](../REST/REST_requests.md). If the response is of type `4D.OutgoingMessage`, the REST server does not return an object but the object instance of the `OutgoingMessage` class.
 
-Typically, this class can be used in custom [HTTP request handler functions](../WebServer/http-request-handler.md#function-configuration) or in functions declared with the [`onHttpGet`](../ORDA/ordaClasses.md#onhttpget-keyword) keyword and designed to handle HTTP GET requests. Such requests are used, for example, to implement features such as download file, generate and download picture as well as receiving any content-type via a browser. 
+Typically, this class can be used in custom [HTTP request handler functions](../WebServer/http-request-handler.md#function-configuration) or in functions declared with the [`onHTTPGet`](../ORDA/ordaClasses.md#onhttpget-keyword) keyword and designed to handle HTTP GET requests. Such requests are used, for example, to implement features such as download file, generate and download picture as well as receiving any content-type via a browser. 
 
 An instance of this class is built on 4D Server and can be sent to the browser by the [4D REST Server](../REST/gettingStarted.md) only. This class allows to use other technologies than HTTP (e.g. mobile).
 

docs/Concepts/classes.md

@@ -785,7 +785,7 @@ You declare singleton classes by adding appropriate keyword(s) before the [`Clas
 :::note
 
 - Session singletons are automatically shared singletons (there's no need to use the `shared` keyword in the class constructor). 
-- Singleton shared functions support [`onHttpGet` keyword](../ORDA/ordaClasses.md#onhttpget-keyword).
+- Singleton shared functions support [`onHTTPGet` keyword](../ORDA/ordaClasses.md#onhttpget-keyword).
 
 :::
 

docs/Concepts/error-handling.md

@@ -26,7 +26,7 @@ It is highly recommended to install a global error-handling method on 4D Server,
 
 Many 4D class functions, such as `entity.save()` or `transporter.send()`, return a *status* object. This object is used to store "predictable" errors in the runtime context, e.g. invalid password, locked entity, etc., that do not stop program execution. This category of errors can be handled by regular code.
 
-Other "unpredictable" errors include disk write error, network failure, or in general any unexpected interruption. This category of errors generates exceptions and needs to be handled through an error-handling method or a `Try()` keyword.  
+Other "unpredictable" errors include disk write error, network failure, or in general any unexpected interruption. This category of errors generates exceptions defined by [a *code*, a *message* and a *signature*](#error-codes) and needs to be handled through an error-handling method or a `Try()` keyword.  
 
 
 ## Installing an error-handling method
@@ -295,3 +295,62 @@ Function createInvoice($customer : cs.customerEntity; $items : Collection; $invo
 	return $newInvoice
 
 ```
+
+
+## Error codes
+
+Exceptions that interrupt code execution are returned by 4D but can have different origins such as the OS, a device, the 4D kernel, a [`throw`](../commands-legacy/throw.md) in your code, etc. A returned error is therefore defined by three elements:
+
+- a **component signature**, which is the origin of the error
+- a **message**, wich explains why the error occurred 
+- a **code**, which is an arbitrary number returned by the component
+
+These information are returned for every error (when available) by the [4D error dialog box](../Debugging/basics.md) and the [`Last errors`](../commands-legacy/last-errors.md) command. Keep in mind that, if you intercept and handle errors using a [error-handling method](#installing-an-error-handling-method), you need to process all information since a simple error code could not be correctly interpreted. 
+
+#### 4D component signatures
+
+|Component Signature|Component|
+|--|---|
+|4DCM|4D Compiler runtime|
+|4DRT|4D runtime|
+|bkrs|4D backup & restore manager|
+|brdg|SQL 4D bridge|
+|cecm|4D code Editor|
+|CZip|zip 4D apis|
+|dbmg|4D database manager|
+|FCGI|fast cgi 4D bridge|
+|FiFo|4D file objects|
+|HTCL|http client 4D apis|
+|HTTP|4D http server|
+|IMAP|IMAP 4D apis|
+|JFEM|Form Macro apis|
+|LD4D|LDAP 4D apis|
+|lscm|4D language syntax manager|
+|MIME|MIME 4D apis|
+|mobi|4D Mobile|
+|pdf1|4D pdf apis|
+|PHP_|php 4D bridge|
+|POP3|POP3 4D apis|
+|SMTP|SMTP 4D apis|
+|SQLS|4D SQL server|
+|srvr|4D network layer apis|
+|svg1|SVG 4D apis|
+|ugmg|4D users and groups manager|
+|UP4D|4D updater|
+|VSS |4D VSS support (Windows Volume Snapshot Service) |
+|webc|4D Web view|
+|xmlc|XML 4D apis|
+|wri1|4D Write Pro|
+
+
+#### System component signatures
+
+|Component Signature|Component|
+|--|---|
+|CARB|Carbon subsystem|
+|COCO|Cocoa subsystem|
+|MACH|macOS Mach subsystem|
+|POSX|posix/bsd subsystem (mac, linux, win)|
+|PW32|Pre-Win32 subsystem|
+|WI32|Win32 subsystem|
+

docs/Notes/updates.md

@@ -12,6 +12,10 @@ Read [**What’s new in 4D 20 R10**](https://blog.4d.com/en-whats-new-in-4d-20-R
 
 - New `connectionTimeout` option in the [`options`](../API/TCPConnectionClass.md#options-parameter) parameter of the [`4D.TCPConnection.new()`](../API/TCPConnectionClass.md#4dtcpconnectionnew) function.
 
+- 4D Language:
+	- For consistency, [`Create entity selection`](../commands/create-entity-selection.md) and [`USE ENTITY SELECTION`](../commands/use-entity-selection.md) commands have been moved from the ["4D Environment"](../commands/theme/4D_Environment.md) to the ["Selection"](../commands/theme/Selection.md) themes.
+
+
 ## 4D 20 R9
 
 Read [**What’s new in 4D 20 R9**](https://blog.4d.com/en-whats-new-in-4d-20-R9/), the blog post that lists all new features and enhancements in 4D 20 R9.
@@ -74,7 +78,7 @@ Read [**What’s new in 4D 20 R7**](https://blog.4d.com/en-whats-new-in-4d-20-R7
 - You can now [add and remove components using the Component manager interface](../Project/components.md#monitoring-project-dependencies).
 - New [**direct typing mode**](../Project/compiler.md#enabling-direct-typing) in which you declare all variables and parameters in your code using `var` and `#DECLARE`/`Function` keywords (only mode supported in new projects). [Syntax checking feature](../Project/compiler.md#check-syntax) has been enhanced accordingly. 
 - Support of [Session singletons](../Concepts/classes.md#singleton-classes) and new [`.isSessionSingleton`](../API/ClassClass.md#issessionsingleton) Class property. 
-- New [`onHttpGet` function keyword](../ORDA/ordaClasses.md#onhttpget-keyword) to define singleton or ORDA functions that can be called through [HTTP REST GET requests](../REST/ClassFunctions.md#function-calls). 
+- New [`onHTTPGet` function keyword](../ORDA/ordaClasses.md#onhttpget-keyword) to define singleton or ORDA functions that can be called through [HTTP REST GET requests](../REST/ClassFunctions.md#function-calls). 
 - New [`4D.OutgoingMessage`](../API/OutgoingMessageClass.md) class for the REST server to return any web contents.
 - Qodly Studio: You can now [attach the Qodly debugger to 4D Server](../WebServer/qodly-studio.md#using-qodly-debugger-on-4d-server).
 - New Build Application keys for remote 4D applications to validate the server certificate authority [signatures](https://doc.4d.com/4Dv20R7/4D/20-R7/CertificateAuthoritiesCertificates.300-7425900.en.html) and/or [domain](https://doc.4d.com/4Dv20R7/4D/20-R7/CertificateDomainName.300-7425906.en.html).

docs/ORDA/ordaClasses.md

@@ -859,20 +859,20 @@ $status:=$remoteDS.Schools.registerNewStudent($student) // OK
 $id:=$remoteDS.Schools.computeIDNumber() // Error "Unknown member method"
 ```
 
-## onHttpGet keyword
+## onHTTPGet keyword
 
-Use the `onHttpGet` keyword to declare functions that can be called through HTTP requests using the `GET` verb. Such functions can return any web contents, for example using the [`4D.OutgoingMessage`](../API/OutgoingMessageClass.md) class. 
+Use the `onHTTPGet` keyword to declare functions that can be called through HTTP requests using the `GET` verb. Such functions can return any web contents, for example using the [`4D.OutgoingMessage`](../API/OutgoingMessageClass.md) class. 
 
-The `onHttpGet` keyword is available with:
+The `onHTTPGet` keyword is available with:
 
 - ORDA Data model class functions
 - [Singletons class functions](../Concepts/classes.md#singleton-classes)
 
 The formal syntax is:
 
 ```4d  
-// declare an onHttpGet function
-exposed onHttpGet Function <functionName>(params) : result
+// declare an onHTTPGet function
+exposed onHTTPGet Function <functionName>(params) : result
 ```
 
 :::info
@@ -889,7 +889,7 @@ As this type of call is an easy offered action, the developer must ensure no sen
 
 ### params
 
-A function with `onHttpGet` keyword accepts [parameters](../Concepts/parameters.md).
+A function with `onHTTPGet` keyword accepts [parameters](../Concepts/parameters.md).
 
 In the HTTP GET request, parameters must be passed directly in the URL and declared using the `$params` keyword (they must be enclosed in a collection). 
 
@@ -903,7 +903,7 @@ See the [Parameters](../REST/classFunctions#parameters) section in the REST serv
 
 ### result
 
-A function with `onHttpGet` keyword can return any value of a supported type (same as for REST [parameters](../REST/classFunctions#parameters)).
+A function with `onHTTPGet` keyword can return any value of a supported type (same as for REST [parameters](../REST/classFunctions#parameters)).
 
 :::info
 

docs/REST/$singleton.md

@@ -47,7 +47,7 @@ with data in the body of the POST request: `["myparam"]`
 
 :::note
 
-The `SingletonClassFunction()` function must have been declared with the `onHttpGet` keyword to be callable with `GET` (see [Function configuration](ClassFunctions#function-configuration)). 
+The `SingletonClassFunction()` function must have been declared with the `onHTTPGet` keyword to be callable with `GET` (see [Function configuration](ClassFunctions#function-configuration)). 
 
 :::
 

docs/REST/ClassFunctions.md

@@ -55,7 +55,7 @@ with data in the body of the POST request: `["Aguada"]`
 
 :::note
 
-The `getCity()` function must have been declared with the `onHttpGet` keyword (see [Function configuration](#function-configuration) below). 
+The `getCity()` function must have been declared with the `onHTTPGet` keyword (see [Function configuration](#function-configuration) below). 
 
 :::
 
@@ -80,13 +80,13 @@ exposed Function getSomeInfo() : 4D.OutgoingMessage
 See [Exposed vs non-exposed functions](../ORDA/ordaClasses.md#exposed-vs-non-exposed-functions) section.
 
 
-### `onHttpGet`
+### `onHTTPGet`
 
-Functions allowed to be called from HTTP `GET` requests must also be specifically declared with the [`onHttpGet` keyword](../ORDA/ordaClasses.md#onhttpget-keyword). For example:
+Functions allowed to be called from HTTP `GET` requests must also be specifically declared with the [`onHTTPGet` keyword](../ORDA/ordaClasses.md#onhttpget-keyword). For example:
 
 ```4d
 //allowing GET requests
-exposed onHttpGet Function getSomeInfo() : 4D.OutgoingMessage
+exposed onHTTPGet Function getSomeInfo() : 4D.OutgoingMessage
 ```
 
 

docs/WebServer/http-request-handler.md

@@ -252,7 +252,7 @@ Request handler functions are not necessarily shared, unless some request handle
 
 :::note
 
-It is **not recommended** to expose request handler functions to external REST calls using [`exposed`](../ORDA/ordaClasses.md#exposed-vs-non-exposed-functions) or [`onHttpGet`](../ORDA/ordaClasses.md#onhttpget-keyword) keywords.
+It is **not recommended** to expose request handler functions to external REST calls using [`exposed`](../ORDA/ordaClasses.md#exposed-vs-non-exposed-functions) or [`onHTTPGet`](../ORDA/ordaClasses.md#onhttpget-keyword) keywords.
 
 :::
 

docs/commands-legacy/last-errors.md

@@ -25,13 +25,22 @@ Each error object contains the following attributes:
 | message            | text     | Description of the error                                     |
 | componentSignature | text     | Signature of the internal component which returned the error |
 
+:::note
+
+For a description of component signatures, please refer to the [Error codes](../Concepts/error-handling.md#error-codes) section.
+ 
+:::
+
+
+
 This command must be called from an on error call method installed by the [ON ERR CALL](on-err-call.md) command.
 
 
 ## See also 
 
 [ON ERR CALL](on-err-call.md)  
 [throw](throw.md)  
+[Error handling](../Concepts/error-handling.md)
 
 ## Properties
 

docs/commands/theme/4D_Environment.md

@@ -15,7 +15,6 @@ slug: /commands/theme/4D-Environment
 |[<!-- INCLUDE #_command_.Compact data file.Syntax -->](../../commands-legacy/compact-data-file.md)<br/>|
 |[<!-- INCLUDE #_command_.COMPONENT LIST.Syntax -->](../../commands-legacy/component-list.md)<br/>|
 |[<!-- INCLUDE #_command_.CREATE DATA FILE.Syntax -->](../../commands-legacy/create-data-file.md)<br/>|
-|[<!-- INCLUDE #_command_.Create entity selection.Syntax -->](../../commands/create-entity-selection.md)<br/>|
 |[<!-- INCLUDE #_command_.Data file.Syntax -->](../../commands-legacy/data-file.md)<br/>|
 |[<!-- INCLUDE #_command_.Database measures.Syntax -->](../../commands-legacy/database-measures.md)<br/>|
 |[<!-- INCLUDE #_command_.DROP REMOTE USER.Syntax -->](../../commands-legacy/drop-remote-user.md)<br/>|
@@ -47,7 +46,6 @@ slug: /commands/theme/4D-Environment
 |[<!-- INCLUDE #_command_.SET UPDATE FOLDER.Syntax -->](../../commands-legacy/set-update-folder.md)<br/>|
 |[<!-- INCLUDE #_command_.Structure file.Syntax -->](../../commands-legacy/structure-file.md)<br/>|
 |[<!-- INCLUDE #_command_.Table fragmentation.Syntax -->](../../commands-legacy/table-fragmentation.md)<br/>|
-|[<!-- INCLUDE #_command_.USE ENTITY SELECTION.Syntax -->](../../commands/use-entity-selection.md)<br/>|
 |[<!-- INCLUDE #_command_.VERIFY CURRENT DATA FILE.Syntax -->](../../commands-legacy/verify-current-data-file.md)<br/>|
 |[<!-- INCLUDE #_command_.VERIFY DATA FILE.Syntax -->](../../commands-legacy/verify-data-file.md)<br/>|
 |[<!-- INCLUDE #_command_.Version type.Syntax -->](../../commands-legacy/version-type.md)<br/>|