- Überblick
- Erste Schritte
- Konzepte
- Verwenden der UiPath CLI
- Anleitungen
- CI/CD-Rezepte
- Befehlsreferenz
- Überblick
- Exitcodes
- Globale Optionen
- UIP-codierter Agent
- uip coder
- uip context-grounding
- UIP-Dokumentation
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- Add-Test-Data-Entität
- Add-Test-Data-Queue
- Add-Test-Data-Variation
- Analysieren
- Erstellen
- Ein Projekt erstellen
- Diff
- Suchaktivitäten
- Get-Analyse-Regeln
- get-standard-aktivität-xaml
- Fehler abrufen
- Manuelle-Testfälle erhalten
- Manuelle-Testschritte erhalten
- get-library-object-repository
- get-object-repository
- Get-Versionen
- Beispiel für einen Workflow abrufen
- Anwendung anzeigen
- Anzeigeelement
- Inspektionspaket
- install-data-fabric-entities
- Pakete installieren oder aktualisieren
- list-data-fabric-entities
- list-instances
- Beispiele für Listenworkflows
- Packen
- Veröffentlichen
- remote
- restore
- run, debug & execution
- Ausführungsdatei installieren
- Suchvorlagen
- Studio starten
- Ausführung anhalten
- tm
- UIA
- uip tasks
- UIP-Ablaufverfolgungen
- uip traces feedback
- Migration
- Referenz und Support
Syntax and options for `uip maestro case task-entry-conditions get`, which reads the rules that gate when a task becomes runnable in a case management definition JSON file, plus the JSON field reference for hand-editing one.
A task entry condition is a named rule set attached to a task that determines when the task becomes eligible to run — for example, only after every other task in the stage has completed, or only after specific named tasks finish. uip maestro case task-entry-conditions reads these conditions from a case-definition JSON file.
For the tasks these conditions gate, see uip maestro case tasks. For the overall Case Management concept model, see uip maestro case.
Konzepte
- Rule type — the real, source-validated set is
current-stage-entered,selected-tasks-completed,wait-for-connector,adhoc,runs-sequentially.selected-tasks-completedadditionally requires a list of task IDs. Note: this command's own built-in--helpexample demonstrates--rule-type all-previous-tasks-completed, which is not in the validated list above — treat that specific value as a bug in the source's own example, not a valid rule type.
Zusammenfassung
uip maestro case task-entry-conditions get <file> <stage-id> <task-id> <condition-id>
uip maestro case task-entry-conditions get <file> <stage-id> <task-id> <condition-id>
uip maestro case task-entry-conditions get
Print an entry condition by ID.
Argumente
| Name | Erforderlich | Zweck |
|---|---|---|
<file> | ja | Path to the case management JSON file. |
<stage-id> | ja | ID of the stage node. |
<task-id> | ja | ID of the task. |
<condition-id> | ja | ID of the entry condition to retrieve. |
Beispiel
uip maestro case task-entry-conditions get case.json Stage_1 Task_1 Condition_a1b2c3d4
uip maestro case task-entry-conditions get case.json Stage_1 Task_1 Condition_a1b2c3d4
Datenform (--output json)
{
"Code": "TaskEntryConditionFound",
"Data": {
"Condition": { "id": "Condition_a1b2c3d4", "displayName": "Start", "rules": [[{ "id": "Rule_e5f6a7b8", "type": "current-stage-entered" }]] }
}
}
{
"Code": "TaskEntryConditionFound",
"Data": {
"Condition": { "id": "Condition_a1b2c3d4", "displayName": "Start", "rules": [[{ "id": "Rule_e5f6a7b8", "type": "current-stage-entered" }]] }
}
}
Condition is the raw node object as stored on disk — use this shape as a reference when hand-editing caseplan.json. rules is a nested array — one inner array per OR-branch rule group.
Task-entry-condition JSON fields
Conditions are added, edited, and removed by hand in caseplan.json's task-entry-conditions array. Field reference:
| Feld | Wert | Hinweise |
|---|---|---|
displayName | string | Display name for the condition. |
Regel type | current-stage-entered|selected-tasks-completed|wait-for-connector|adhoc|runs-sequentially | Goes inside a rules[][] entry. |
| condition expression | string | Free-form expression on a rule, when the rule type supports one. |
selectedTasksIds | array of strings | Required alongside a selected-tasks-completed rule. |
After editing caseplan.json's task-entry-conditions array directly, run uip maestro case validate.
Zugehörig
- uip maestro case — concepts and the full subsystem directory.
- uip maestro case tasks — the tasks these conditions gate.
- uip maestro case cases & stages — the stage a task lives inside.
- uip maestro case conditions — the case-level and stage-level equivalents.