- Vue d'ensemble (Overview)
- Démarrer
- Concepts
- Utilisation de la UiPath CLI
- Guides pratiques
- Revenus CI/CD
- Référence de commande
- Vue d'ensemble (Overview)
- Codes de sortie
- Options globales
- agent codé uip
- encodeur UIP
- uip ancrage dans le contexte
- UiPath Docsai
- Fonction UiP
- garde-fous UiP
- configuration llm uip
- uip llm-passerelle
- uip maestro authoring
- uip maestro registry
- uip model-hub
- Tâches (Jobs)
- Dossiers
- Processus
- process-roi
- Paquets
- Machines
- Utilisateurs
- Rôles
- Licences
- Flux
- Pièces jointes (Attachments)
- Sessions
- Calendriers
- magasins d'informations d’identification
- journaux-audit
- paramètres
- Actifs
- Compartiments
- Compartiment-fichiers
- Bibliothèques
- Files d'attente (Queues)
- queue-roi
- éléments de la file d'attente
- Déclencheurs (Triggers)
- Webhooks
- activities find
- activities get-default-xaml
- Analyser
- analyzer-rules list
- Construire
- Nettoyage
- data-fabric-entities install
- data-fabric-entities list
- files diff
- Get-Library-Object-Repository
- Récupérer le référentiel d'objets
- Init
- instances list
- Créer un package
- packages inspect
- packages install
- packages versions
- Publier
- Distant
- restore
- exécuter, déboguer et amp; Exécution
- paramètres
- studio start
- templates search
- test-data add-entity
- test-data add-queue
- test-data add-variation
- TM
- UIA
- Valider
- workflow-examples get
- workflow-examples list
- tâches UIP
- pièce jointe
- Champ personnalisé
- defects
- Exécutions
- export-jobs
- migration
- Libellé Objet
- Créer un package
- scénarios-perf
- groupes-de-charge-scénarios-perf
- données d’exécution de perf-scenario
- rapport de scénarios de performances
- Projet
- project-permissions
- prompts
- Rapport
- Prérequis
- Résultat
- Exécuter
- schedules
- testcaselog
- Cas de test
- Ensembles de tests
- Journal des étapes de test
- Utilisateur (User)
- Attendre
- Traçages UIP
- Commentaires sur les traces UIP
- Migration
- Référence et assistance
uip rules validate
Syntax and options for `uip rules validate`, which checks a Business Rules project for the errors Studio Web blocks publish and debug on.
uip rules validate checks a Business Rules project for what Studio Web blocks publish and debug on. It reports two kinds of diagnostics:
- The Studio Web designer's diagnostics for each
.dmnfile at the top level of the project. Their codes start withDMN_. RULES_ENTRY_POINTS_STALEwhenentry-points.jsondoes not match the.dmnfiles. Runuip rules refreshto fix it.
Diagnostics with severity error fail the command. Diagnostics with severity warning are reported only. The command does not write any file.
Synthèse
uip rules validate <project-path>
uip rules validate <project-path>
Arguments
| Nom | Requis | Objectif |
|---|---|---|
<project-path> | oui | Path to the Business Rules project directory. The directory must contain project.uiproj. |
Exemple
uip rules validate ./LoanEligibilitySolution/LoanEligibility
uip rules validate ./LoanEligibilitySolution/LoanEligibility
Format des données (--sortie json)
{
"Code": "RulesValidate",
"Data": {
"Status": "Valid",
"ProjectPath": "/workspace/LoanEligibilitySolution/LoanEligibility",
"DmnFiles": ["Business rule.dmn"],
"Diagnostics": []
}
}
{
"Code": "RulesValidate",
"Data": {
"Status": "Valid",
"ProjectPath": "/workspace/LoanEligibilitySolution/LoanEligibility",
"DmnFiles": ["Business rule.dmn"],
"Diagnostics": []
}
}
When the project has at least one error, the command returns a failure envelope with Code: "RulesValidate", ErrorCode: "invalid_argument", and Data.Status: "Invalid". Instructions lists each diagnostic on its own line.
Each entry in Diagnostics has these fields:
| Champ | Description |
|---|---|
File | The file the diagnostic applies to: a .dmn file, or entry-points.json. |
Code | The diagnostic code, for example RULES_ENTRY_POINTS_STALE. |
Severity | error ou warning. |
Message | The diagnostic message. |
Instructions | How to fix the issue, when available. |
Target | The element of the document the diagnostic points to. |
Codes de sortie
Refer to Exit codes for the shared contract. The command exits 1 when any diagnostic has severity error, or when the project has no .dmn file at its top level (ErrorCode: "not_found").
Commandes associées
uip rules refreshfixesRULES_ENTRY_POINTS_STALE.uip rules debugevaluates the rule with sample inputs.
Voir également
uip rulesfor the tool overview and project layout.