Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
| en:identifier_les_etapes_en_echec [2025/08/05 09:31] – [✅ Summary] admin | en:identifier_les_etapes_en_echec [2026/01/16 17:10] (Version actuelle) – admin | ||
|---|---|---|---|
| Ligne 1: | Ligne 1: | ||
| - | ====== 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: '' | + | 👉 **New address:** |
| - | + | https://id360.doca-id.com/?id=en:start | |
| - | **JSON Path**: '' | + | |
| - | + | ||
| - | Each validation represents a business rule applied to a data field. | + | |
| - | + | ||
| - | Check for: | + | |
| - | | + | |
| - | | + | |
| - | * '' | + | |
| - | + | ||
| - | **Example**: | + | |
| - | <code json> | + | |
| - | { | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | } | + | |
| - | </code> | + | |
| - | + | ||
| - | **🎯 Use Case**: Identify which user data failed the controls. | + | |
| - | + | ||
| - | ⚠️ **Note**: For last name comparisons, | + | |
| - | Therefore, you may see the field " | + | |
| - | If either check is successful, the name comparison should be considered **passed**. | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ===== 2. 🆚 Cross-Source Comparisons: | + | |
| - | + | ||
| - | **JSON Path**: '' | + | |
| - | + | ||
| - | These blocks compare values from multiple sources (e.g., user input vs. documents, or between documents). | + | |
| - | + | ||
| - | Check for: | + | |
| - | * '' | + | |
| - | * '' | + | |
| - | * '' | + | |
| - | + | ||
| - | **Example**: | + | |
| - | <code json> | + | |
| - | { | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | } | + | |
| - | </code> | + | |
| - | + | ||
| - | **🎯 Use Case**: Detect inconsistencies between documents or between documents and user input. | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ===== 3. ⚙️ Custom Rules: '' | + | |
| - | + | ||
| - | **JSON Path**: '' | + | |
| - | + | ||
| - | These checks are client-specific or related to particular document types. | + | |
| - | + | ||
| - | Check for: | + | |
| - | * '' | + | |
| - | * '' | + | |
| - | * '' | + | |
| - | + | ||
| - | **Example**: | + | |
| - | <code json> | + | |
| - | { | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | } | + | |
| - | </code> | + | |
| - | + | ||
| - | **🎯 Use Case**: Understand failures on custom rules defined for a specific client. | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ===== 4. 🔢 Step-Level Analysis: '' | + | |
| - | + | ||
| - | **JSON Path**: '' | + | |
| - | + | ||
| - | The '' | + | |
| - | For each step, you should: | + | |
| - | + | ||
| - | * Read the '' | + | |
| - | * If the value is '' | + | |
| - | + | ||
| - | **Example**: | + | |
| - | <code json> | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | { | + | |
| - | " | + | |
| - | " | + | |
| - | } | + | |
| - | ] | + | |
| - | } | + | |
| - | } | + | |
| - | </ | + | |
| - | + | ||
| - | **🎯 Use Case**: Helps isolate which steps failed and provides contextual details on the encountered issues. | + | |
| - | + | ||
| - | ----- | + | |
| - | + | ||
| - | ===== ✅ Summary ===== | + | |
| - | + | ||
| - | ^ Element | + | |
| - | | Validations | + | |
| - | | Comparisons | + | |
| - | | Customs | + | |
| - | | Steps | '' | + | |
| - | | | + | |
| + | Please update your bookmarks and internal links accordingly. | ||
| + | Feel free to reach out if you have any questions 😊 | ||