Outils pour utilisateurs

Différences

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

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
Prochaine révision		Révision précédente
en:identifier_les_etapes_en_echec [2025/08/07 15:23] – adminen:identifier_les_etapes_en_echec [2026/01/16 17:10] (Version actuelle) – admin
Ligne 1: Ligne 1:
 [[:identifier_les_etapes_en_echec|Français]] | [[:en:identifier_les_etapes_en_echec|English]] [[:identifier_les_etapes_en_echec|Français]] | [[:en:identifier_les_etapes_en_echec|English]]
 ---- ----
-====== How to Identify Failed Steps in an ID360 JSON Report ======+===== 🔗 DOCUMENTATION URL CHANGE =====
  
-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.+The ID360 documentation URL has been updated.
  
-===== 1. 📄 Validation Details: ''validations'' ===== +👉 **New address:**   
- +https://id360.doca-id.com/?id=en:start
-**JSON Path**: ''finalizer_reports > validator_report > validations'' +
- +
-Each validation represents a business rule applied to a data field. +
- +
-Check for: +
-  * ''is_valid: false'' → indicates a failed validation   +
-  * ''ref'': rule identifier (e.g., ''IDENTITY.FIRST_NAME.first_name'')   +
-  * ''fields'': affected data +
- +
-**Example**: +
-<code json> +
-{ +
-  "ref": "IDENTITY.FIRST_NAME.first_name", +
-  "is_valid": false, +
-  "fields": [...] +
-} +
-</code> +
- +
-**🎯 Use Case**: Identify which user data failed the controls. +
- +
-⚠️ **Note**: For last name comparisons, two checks are performed: one on the **preferred name**, the other on the **birth name**.   +
-Therefore, you may see the field "ref": "IDENTITY.NAME.name" appear twice.   +
-If either check is successful, the name comparison should be considered **passed**. +
- +
------ +
- +
-===== 2. 🆚 Cross-Source Comparisons: ''comparisons'' ===== +
- +
-**JSON Path**: ''finalizer_reports > validator_report > comparisons'' +
- +
-These blocks compare values from multiple sources (e.g., user input vs. documents, or between documents). +
- +
-Check for: +
-  * ''is_equivalent: false'' → comparison failed   +
-  * ''ref'': rule identifier   +
-  * ''field1'' and ''field2'': the values being compared +
- +
-**Example**: +
-<code json> +
-{ +
-  "ref": "KBIS.SIREN.siren", +
-  "is_equivalent": false, +
-  "field1": {...}, +
-  "field2": {...} +
-} +
-</code> +
- +
-**🎯 Use Case**: Detect inconsistencies between documents or between documents and user input. +
- +
------ +
- +
-===== 3. ⚙️ Custom Rules: ''customs'' ===== +
- +
-**JSON Path**: ''finalizer_reports > validator_report > customs'' +
- +
-These checks are client-specific or related to particular document types. +
- +
-Check for: +
-  * ''is_valid: false'' → custom rule failed   +
-  * ''ref'': rule name   +
-  * ''fields'': data fields being evaluated +
- +
-**Example**: +
-<code json> +
-{ +
-  "ref": "IDENTITY_DOCUMENT.document_number", +
-  "is_valid": false, +
-  "fields": [...] +
-} +
-</code> +
- +
-**🎯 Use Case**: Understand failures on custom rules defined for a specific client. +
- +
------ +
- +
-===== 4. 🔢 Step-Level Analysis: ''steps'' ===== +
- +
-**JSON Path**: ''steps'' +
- +
-The ''steps'' block contains the various steps of the process.   +
-For each step, you should: +
- +
-  * Read the ''status'' field   +
-  * If the value is ''KO'', review the ''status_codes'' list within that step to understand the causes +
- +
-**Example**: +
-<code json> +
-"steps": { +
-  "id_document": { +
-    "status": "KO", +
-    "status_codes": [ +
-      { +
-        "code": "MDL_INPUT_INVALID", +
-        "message": "No MRZ could be read on the uploaded image(s)" +
-      } +
-    ] +
-  } +
-} +
-</code> +
- +
-**🎯 Use Case**: Helps isolate which steps failed and provides contextual details on the encountered issues. +
- +
------ +
- +
-===== ✅ Summary ===== +
- +
-^ Element          ^ JSON Path                                                  ^ Check Criteria                                                  ^                          +
-| Validations      | ''finalizer_reports > validator_report > validations''     | ''is_valid: false''                                             | +
-| Comparisons      | ''finalizer_reports > validator_report > comparisons''     | ''is_equivalent: false''                                         | +
-| Customs          | ''finalizer_reports > validator_report > customs''         | ''is_valid: false''                                             | +
-| Steps            | ''steps > [step_name] > status'' + ''status_codes''        | If ''status: KO'', review associated ''status_codes'' entries     +
-|+
  
 +Please update your bookmarks and internal links accordingly.  
 +Feel free to reach out if you have any questions 😊

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

Plus d’informations