Différences

Ci-dessous, les différences entre deux révisions de la page.

--- en:identifier_les_etapes_en_echec [2025/08/05 09:31] – [✅ Summary] admin
+++ en:identifier_les_etapes_en_echec [2026/01/12 16:39] (Version actuelle) – modification externe 127.0.0.1
@@ Ligne 1: / Ligne 1: @@
-====== How to Identify Failed Steps in an ID360 JSON Report ======
+[[:identifier_les_etapes_en_echec|Français]] | [[:en:identifier_les_etapes_en_echec|English]]
+----
+====== 📄 How to Identify Failed Steps in an ID360 JSON Report ======
-When an ID360 verification returns a **KO** status, it is possible to analyze the cause using the JSON file structure. Below are the paths to follow to locate useful information.
+When an ID360 verification returns a **KO** ❌ status, it is possible to analyze the cause by checking the structure of the JSON file 📂.
+Here are the paths to follow to find the relevant information 🔍.
-===== 1. 📄 Validation Details: ''validations'' =====
+⚠️ **Important:** You must review **all the steps described in this guide** 🗂️, even if certain **keys** or **sections** of the JSON file are not present **at the current moment** in your workflow.\\
+Each JSON key corresponds to a **specific configuration of the workflow** 🛠️.\\
+\\
+🔄 If your process configuration changes (adding ➕, removing ➖, or modifying ✏️ steps or checks), the list of possible errors will also change.\\
+**Therefore, the absence of a key in today’s JSON does not guarantee it will be absent tomorrow.**\\
+\\
+✅ For this reason, it is essential to review **all the steps mentioned in this guide** in order to anticipate and properly handle future changes 🚀.
+===== 1. 📌 Major Errors: ''all_status_codes'' =====
+**JSON Path**: ''all_status_codes''
+This array contains the major errors detected during verification.
+Each status_code element contains:
+  * ''code'': the error code (e.g., VLD_VALIDATION_KO, exhaustive list [[https://id360docaposte.com/fr/documentation/status-codes|here]]))
+  * ''message'': a description of the failed validations
+**Example**:
+<code json>
+{
+  "all_status_codes": [{
+     "status_code": {
+        "code": "VLD_VALIDATION_KO",
+        "message": "1 validations failed: . Max allowed: 0"
+        },
+        "where": "ID360"
+      },{
+     "status_code": {
+        "code": "MDL_INPUT_INVALID",
+        "message": "No MRZ could be read on the uploaded image(s)"
+       },
+       "where": "id_document"
+      },{
+      "status_code": {
+        "code": "VLD_ID_INVALID",
+        "message": "Id from id_document_result is ignored because the format is not recognized"
+        },
+        "where": "validation"
+      }]
+}
+</code>
+**🎯 Purpose**: Identification of major errors.
+⚠️ As part of the use of an Electronic Identification Means (such as Identité Numérique La Poste, FranceConnect+ or PVID), when the identification result is KO, the returned code is EIM_RESPONSE_KO.
+===== 2. 📄 Validation Details: ''validations'' =====
 **JSON Path**: ''finalizer_reports > validator_report > validations''
@@ Ligne 31: / Ligne 81: @@
 -----
-===== 2. 🆚 Cross-Source Comparisons: ''comparisons'' =====
+===== 3. 🆚 Cross-Source Comparisons: ''comparisons'' =====
 **JSON Path**: ''finalizer_reports > validator_report > comparisons''
@@ Ligne 56: / Ligne 106: @@
 -----
-===== 3. ⚙️ Custom Rules: ''customs'' =====
+===== 4. ⚙️ Custom Rules: ''customs'' =====
 **JSON Path**: ''finalizer_reports > validator_report > customs''
@@ Ligne 80: / Ligne 130: @@
 -----
-===== 4. 🔢 Step-Level Analysis: ''steps'' =====
+===== 5. 🔢 Step-Level Analysis: ''steps'' =====
 **JSON Path**: ''steps''
@@ Ligne 111: / Ligne 161: @@
 ===== ✅ Summary =====
-^ Element          ^ JSON Path                                                  ^ Check Criteria                                                  ^                         |
+^ Element          ^ JSON Path                                                  ^ Check Criteria                                                  ^
-| Validations      | ''finalizer_reports > validator_report > validations''     | ''is_valid: false''                                             |
+| All Status Code  | ''all_status_code''         | at least one ''status_code'' exists|
-| Comparisons      | ''finalizer_reports > validator_report > comparisons''     | ''is_equivalent: false''                                         |
+| Validations      | ''finalizer_reports > validator_report > validations''     | ''is_valid: false''|
-| Customs          | ''finalizer_reports > validator_report > customs''         | ''is_valid: false''                                             |
+| Comparisons      | ''finalizer_reports > validator_report > comparisons''     | ''is_equivalent: false''|
-| Steps            | ''steps > [step_name] > status'' + ''status_codes''        | If ''status: KO'', review associated ''status_codes'' entries
+| Customs          | ''finalizer_reports > validator_report > customs''         | ''is_valid: false''   |
-|
+| Steps            | ''steps > [step_name] > status'' + ''status_codes''        | If ''status: KO'', review associated ''status_codes'' entries    |
+\\
+For example, to check that an identity document is not expired, you should look for the ''IDENTITY_DOCUMENT.expired'' reference across the different blocks and then verify the value of the ''is_valid'' field (true or false).
+The references remain stable and are not expected to change.