updatebefore 21

README.md

@@ -154,6 +154,13 @@ banner: 'none',
 
 3. Aller dans i18n\en\code.json, à la fin du fichier : liens de la page Home (vers extensions) à mettre à jour
 
+### Mettre à jour le lien vers les versions Notes précédentes dans notes
+
+Lien main :
+`See [**Release Notes for 4D 20.x LTS**](../../20/Notes/updates)`. <br/>
+à transformer en 
+`See [**Release Notes for 4D 20.x LTS**](../20/Notes/updates)`. 
+
 ### Si problème de traduction avec cmfcmf:
 1. Faire
 `git restore --rebase --autostash` 
@@ -180,11 +187,16 @@ Forcer une synchro globale de main sur Crowdin
 Tester : Faire npm run build
 
 ### Builder
-Sur github, faire une PR de docs4d/docs/main sur 4d/docs/main
+voir ["mise à jour prod"](#mise-a-jour-prod) ci dessous
 
 ### Algolia (4D only)
 Aller dans l'interface Algolia et lancer un reindex de la doc
 
+## Mise à jour 4D NetKit
+1. Synchro avec prod (4D/4DNetKit)
+2. Pull request vers prod : Main pour version en ligne
+3. Pull request vers prod : version qui shippe pour doc embedded
+
 ## Mise à jour prod
 1. Créer une nouvelle branche en local nommée par exemple Tempo
 2. faire git fetch upstream (met à jour la preprod avec la prod)

crowdin.yml

@@ -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%

docs/API/CollectionClass.md

@@ -2230,7 +2230,7 @@ You can also pass a criteria parameter to define how the collection elements mus
 	|Constant|	Type|Value|Comment|
 	|---|---|---|---|
 	|ck ascending|Integer|0|Elements are ordered in ascending order (default)|
-	|ck descending|Integer|1|Elements are ordered in descending order
+	|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).
 
@@ -3421,12 +3421,13 @@ You want to know if at least one collection value is >0.
 
 </details>
 
-<!-- REF #collection.sort().Syntax -->**.sort**() : Collection<br/>**.sort**( *formula* : 4D.Function { ; *...extraParam* : any } ) : Collection<br/>**.sort**( *methodName* : Text { ; *...extraParam* : any } ) : Collection <!-- END REF -->
+<!-- REF #collection.sort().Syntax -->**.sort**() : Collection<br/>**.sort**( *ascOrDesc* : Integer ) : Collection <br/>**.sort**( *formula* : 4D.Function { ; *...extraParam* : any } ) : Collection<br/>**.sort**( *methodName* : Text { ; *...extraParam* : any } ) : Collection<!-- END REF -->
 
 
 <!-- REF #collection.sort().Params -->
 |Parameter|Type||Description|
 |---------|--- |:---:|------|
+|ascOrDesc|Integer|->|`ck ascending` or `ck descending` (scalar values)|
 |formula|4D.Function|->|Formula object|
 |methodName|Text|->|Name of a method|
 |extraParam |any |->|Parameter(s) for the method|
@@ -3440,7 +3441,17 @@ The `.sort()` function <!-- REF #collection.sort().Summary -->sorts the elements
 
 >This function modifies the original collection.
 
-If `.sort()` is called with no parameters, only scalar values (number, text, date, booleans) are sorted. Elements are sorted by default in ascending order, according to their type. If the collection contains elements of different types, they are first grouped by type and sorted afterwards. Types are returned in the following order:
+If `.sort()` is called with no parameters, only scalar values (number, text, date, booleans) are sorted. Elements are sorted by default in ascending order, according to their type. 
+You can also pass one of the following constants in the *ascOrDesc* parameter:
+
+	|Constant|	Type|Value|Comment|
+	|---|---|---|---|
+	|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).
+
+ If the collection contains elements of different types, they are first grouped by type and sorted afterwards. Types are returned in the following order:
 
 1. null
 2. booleans

docs/API/DataClassClass.md

@@ -1185,7 +1185,7 @@ In this case, the *value* parameter must be a **comparison vector object** conta
 |Property|Type|Description|
 |---|---|---|
 |vector|[4D.Vector](../API/VectorClass.md)|Mandatory. The vector to be compared|
-|metric|Text|Optional. [Vector computation](../API/VectorClass.md#understanding-the-different-vector-computations) to use for the query. You can use one of the following (Text) constants:<li>`mk cosine` (default if omitted): calculates the cosine distance between vectors.</li><li>`mk dot`: calculates the dot similarity of vectors.</li><li>`mk euclidean`: calculates the Euclidean distance between vectors.|
+|metric|Text|Optional. [Vector computation](../API/VectorClass.md#understanding-the-different-vector-computations) to use for the query. You can use one of the following (Text) constants:<li>`mk cosine` (default if omitted): calculates the cosine similarity between vectors.</li><li>`mk dot`: calculates the dot similarity of vectors.</li><li>`mk euclidean`: calculates the Euclidean distance between vectors.|
 |threshold|Real|Optional (default: 0.5). A threshold value used to filter vector comparisons based on their cosine, dot or euclidean similarity score according to the selected "metric". It is highly recommended to choose a similarity that best fits your specific use case for optimal results.|
 
 Only a subset of **comparator** symbols are supported. Note that they compare results to the threshold value: 
@@ -1223,7 +1223,7 @@ The formula must have been created using the [`Formula`](../commands/formula.md)
 
 * the *formula* is evaluated for each entity and must return true or false. During the execution of the query, if the formula's result is not a boolean, it is considered as false.
 * within the *formula*, the entity is available through the `This` object.  
-* if the `Formula` object is **null**, the error 1626 ("Expecting a text or formula") is generated, that you call intercept using a method installed with [`ON ERR CALL`](../commands-legacy/on-err-call.md).
+* if the `Formula` object is **null**, the error 1626 ("Expecting a text or formula") is generated, that you can intercept using a method installed with [`ON ERR CALL`](../commands-legacy/on-err-call.md).
 
  >For security reasons, formula calls within `query()` functions can be disallowed. See *querySettings* parameter description.
 

docs/API/EntityClass.md

@@ -334,6 +334,7 @@ vCompareResult3 (only differences on $e1 touched attributes are returned)
 
 |Release|Changes|
 |---|---|
+|21|Added status 7 and 8|
 |17|Added|
 
 </details>
@@ -360,7 +361,7 @@ Otherwise, you can pass the `dk force drop if stamp changed` option in the *mode
 
 **Result**
 
-The object returned by `.drop( )` contains the following properties:
+The object returned by `.drop()` contains the following properties:
 
 |Property| | Type |Description|
 |---|---|--- |---|
@@ -387,10 +388,12 @@ The object returned by `.drop( )` contains the following properties:
 
 |Constant| Value| Comment|
 |---|---|---|
-|`dk status entity does not exist anymore`|5|The entity no longer exists in the data. This error can occur in the following cases:<br/><li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using entity.drop( ), this error can be returned when dk force drop if stamp changed option is used. When using entity.lock(), this error can be returned when dk reload if stamp changed option is used</li> **Associated statusText**: "Entity does not exist anymore"|
+|`dk status entity does not exist anymore`|5|The entity no longer exists in the data. This error can occur in the following cases:<br/><li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using entity.drop(), this error can be returned when dk force drop if stamp changed option is used. When using entity.lock(), this error can be returned when dk reload if stamp changed option is used.</li> **Associated statusText**: "Entity does not exist anymore"|
 |`dk status locked`|3|The entity is locked by a pessimistic lock.<br/> **Associated statusText**: "Already locked"|
+|`dk status validation failed`| 7| Non fatal error sent by the developer for a [validate event](../ORDA/orda-events.md). **Associated statusText**: "Mild Validation Error"|
 |`dk status serious error`| 4| A serious error is a low-level database error (e.g. duplicated key), a hardware error, etc.<br/>**Associated statusText**: "Other error"
-|`dk status stamp has changed`| 2|The internal stamp value of the entity does not match the one of the entity stored in the data (optimistic lock).<br/><li>with `.save( )`: error only if the `dk auto merge` option is not used</li><li>with `.drop( )`: error only if the `dk force drop if stamp changed` option is not used</li><li>with `.lock()`: error only if the `dk reload if stamp changed` option is not used</li><li>**Associated statusText**: "Stamp has changed"</li>|
+|`dk status serious validation error`| 8| Fatal error sent by the developer for a [validate event](../ORDA/orda-events.md). **Associated statusText**: "Serious Validation Error"|
+|`dk status stamp has changed`| 2|The internal stamp value of the entity does not match the one of the entity stored in the data (optimistic lock).<br/><li>with `.save()`: error only if the `dk auto merge` option is not used</li><li>with `.drop()`: error only if the `dk force drop if stamp changed` option is not used</li><li>with `.lock()`: error only if the `dk reload if stamp changed` option is not used</li><li>**Associated statusText**: "Stamp has changed"</li>|
 |`dk status wrong permission`|1|The current privileges do not allow the drop of the entity. **Associated statusText**: "Permission Error"|
 
 #### Example 1  
@@ -987,10 +990,10 @@ The object returned by `.lock()` contains the following properties:
 
 |Constant |Value| Comment|
 |---|---|---|
-|`dk status entity does not exist anymore`| 5 |The entity no longer exists in the data. This error can occur in the following cases:<li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using `.drop( )`, this error can be returned when dk force drop if stamp changed option is used. When using `.lock()`, this error can be returned when `dk reload if stamp changed` option is used</li><br/>**Associated statusText**: "Entity does not exist anymore"|
+|`dk status entity does not exist anymore`| 5 |The entity no longer exists in the data. This error can occur in the following cases:<li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using `.drop()`, this error can be returned when dk force drop if stamp changed option is used. When using `.lock()`, this error can be returned when `dk reload if stamp changed` option is used</li><br/>**Associated statusText**: "Entity does not exist anymore"|
 |`dk status locked`| 3 |The entity is locked by a pessimistic lock.**Associated statusText**: "Already locked"
-|`dk status serious error`| 4 |A serious error is a low-level database error (e.g. duplicated key), a hardware error, etc.**Associated statusText**: "Other error"|
-|`dk status stamp has changed`|2|The internal stamp value of the entity does not match the one of the entity stored in the data (optimistic lock).<li>with `.save( )`: error only if the `dk auto merge` option is not used</li><li>with `.drop( )`: error only if the `dk force drop if stamp changed` option is not used</li><li>with `.lock()`: error only if the `dk reload if stamp changed` option is not used</li><br/>**Associated statusText**: "Stamp has changed"|
+|`dk status serious error`| 4 |A serious error is a low-level database error (e.g. duplicated key), a hardware error, etc.<br/>**Associated statusText**: "Other error"|
+|`dk status stamp has changed`|2|The internal stamp value of the entity does not match the one of the entity stored in the data (optimistic lock).<li>with `.save()`: error only if the `dk auto merge` option is not used</li><li>with `.drop()`: error only if the `dk force drop if stamp changed` option is not used</li><li>with `.lock()`: error only if the `dk reload if stamp changed` option is not used</li><br/>**Associated statusText**: "Stamp has changed"|
 
 #### Example 1
 
@@ -1149,7 +1152,7 @@ The object returned by `.reload( )` contains the following properties:
 
 |Constant| Value| Comment|
 |---|---|---|
-|`dk status entity does not exist anymore`|5|The entity no longer exists in the data. This error can occur in the following cases:<br/><li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using `.drop( )`, this error can be returned when `dk force drop if stamp changed` option is used. When using `.lock()`, this error can be returned when `dk reload if stamp changed` option is used</li><br/>***Associated statusText***: "Entity does not exist anymore"|
+|`dk status entity does not exist anymore`|5|The entity no longer exists in the data. This error can occur in the following cases:<br/><li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using `.drop()`, this error can be returned when `dk force drop if stamp changed` option is used. When using `.lock()`, this error can be returned when `dk reload if stamp changed` option is used</li><br/>***Associated statusText***: "Entity does not exist anymore"|
 |`dk status serious error`|4| A serious error is a low-level database error (e.g. duplicated key), a hardware error, etc.<br/>***Associated statusText***: "Other error"|
 
 #### Example
@@ -1180,6 +1183,7 @@ The object returned by `.reload( )` contains the following properties:
 
 |Release|Changes|
 |---|---|
+|21|Added status 7 and 8|
 |17|Added|
 
 </details>
@@ -1241,11 +1245,13 @@ The following values can be returned in the `status` and `statusText` properties
 
 |Constant| Value |Comment|
 |---|---|---|
-|`dk status automerge failed`| 6| (Only if the `dk auto merge` option is used) The automatic merge option failed when saving the entity.**Associated statusText**: "Auto merge failed"|
-|`dk status entity does not exist anymore`| 5| The entity no longer exists in the data. This error can occur in the following cases:<br/><li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using `.drop( )`, this error can be returned when `dk force drop if stamp changed` option is used. When using `.lock()`, this error can be returned when `dk reload if stamp changed` option is used</li><br/>**Associated statusText**: "Entity does not exist anymore"|
-|`dk status locked`| 3| The entity is locked by a pessimistic lock.**Associated statusText**: "Already locked"
-|`dk status serious error`|4|A serious error is a low-level database error (e.g. duplicated key), a hardware error, etc.**Associated statusText**: "Other error"|
-|`dk status stamp has changed`|2|The internal stamp value of the entity does not match the one of the entity stored in the data (optimistic lock).<br/><li>with `.save( )`: error only if the `dk auto merge` option is not used</li><li>with `.drop( )`: error only if the `dk force drop if stamp changed` option is not used</li><li>with `.lock()`: error only if the `dk reload if stamp changed` option is not used</li><br/>**Associated statusText**: "Stamp has changed"|
+|`dk status automerge failed`| 6| (Only if the `dk auto merge` option is used) The automatic merge option failed when saving the entity. **Associated statusText**: "Auto merge failed"|
+|`dk status entity does not exist anymore`| 5| The entity no longer exists in the data. This error can occur in the following cases:<br/><li>the entity has been dropped (the stamp has changed and the memory space is now free)</li><li>the entity has been dropped and replaced by another one with another primary key (the stamp has changed and a new entity now uses the memory space). When using `.drop()`, this error can be returned when `dk force drop if stamp changed` option is used. When using `.lock()`, this error can be returned when `dk reload if stamp changed` option is used</li><br/>**Associated statusText**: "Entity does not exist anymore"|
+|`dk status locked`| 3| The entity is locked by a pessimistic lock. **Associated statusText**: "Already locked"|
+|`dk status validation failed`| 7| Non fatal error sent by the developer for a [validate event](../ORDA/orda-events.md). **Associated statusText**: "Mild Validation Error"|
+|`dk status serious error`|4|A serious error is a low-level database error (e.g. duplicated key), a hardware error, etc. **Associated statusText**: "Other error"|
+|`dk status serious validation error`| 8| Fatal error sent by the developer for a [validate event](../ORDA/orda-events.md). **Associated statusText**: "Serious Validation Error"|
+|`dk status stamp has changed`|2|The internal stamp value of the entity does not match the one of the entity stored in the data (optimistic lock).<br/><li>with `.save()`: error only if the `dk auto merge` option is not used</li><li>with `.drop()`: error only if the `dk force drop if stamp changed` option is not used</li><li>with `.lock()`: error only if the `dk reload if stamp changed` option is not used</li><br/>**Associated statusText**: "Stamp has changed"|
 |`dk status wrong permission`|1|The current privileges do not allow the save of the entity. **Associated statusText**: "Permission Error"|
 
 #### Example 1