- Überblick
- Erste Schritte
- Konzepte
- Verwenden der UiPath CLI
- Anleitungen
- CI/CD-Rezepte
- Befehlsreferenz
- Überblick
- Exitcodes
- Globale Optionen
- UIP-codierter Agent
- UIP-Coded
- UIP-Kontextgrundlage
- UIP-Dokumentation
- UIP-Funktion
- UIP-Leitplanken
- uip llm-configuration
- uip llm-gateway
- uip maestro authoring
- uip maestro registry
- UIP-Modellhub
- activities find
- activities get-default-xaml
- Analysieren
- analyzer-rules list
- Erstellen
- Bereinigung
- data-fabric-entities install
- data-fabric-entities list
- files diff
- Get-Library-Object-Repository
- Get-Object-Repository
- Init
- instances list
- Packen
- packages inspect
- packages install
- packages versions
- Veröffentlichen
- Remote
- restore
- Ausführen, Debuggen & Ausführung enthält
- Einstellungen
- studio start
- templates search
- test-data add-entity
- test-data add-queue
- test-data add-variation
- TM
- UIA
- Überprüfen
- workflow-examples get
- workflow-examples list
- UIP-Aufgaben
- Anhang
- benutzerdefiniertes Feld
- defects
- Ausführungen
- export-jobs
- migration
- Objektbeschriftung
- Packen
- perf-szenario
- Perf-Szenario-Lastgruppen
- Ausführungsdaten für perf-szenario
- Perf-Szenario-Bericht
- Projekt
- project-permissions
- prompts
- Melden
- Anforderungen
- Ergebnis
- Ausführen
- schedules
- testcaselog
- Testfälle
- Testsätze
- Testschrittprotokoll
- Benutzer
- Warten
- UIP-Ablaufverfolgungen
- Feedback zu UIP-Ablaufverfolgungen
- Migration
- Referenz und Support
uip maestro authoring commands
Syntax and options for `uip maestro flow`, `case`, and `bpmn` `compile`, `check`, `decompile`, and `merge`, which convert between authored TypeScript and Maestro artifacts.
The authoring commands convert between authored TypeScript source and the artifacts Maestro runs. The same four verbs are registered on each Maestro family:
| Family | Authored source | Artifact |
|---|---|---|
uip maestro flow | <name>.flow.ts | .flow Datei |
uip maestro case | <name>.case.ts | caseplan.json |
uip maestro bpmn | <name>.bpmn.ts | .bpmn Datei |
uip maestro bpmn also registers tidy, which adds diagram layout to a compiled .bpmn file.
The connector library these commands read comes from uip maestro registry.
Anforderungen
@uipath/maestro-builder-sdk6.11.1 or later, installed in the project or globally. The command looks for the package from the current directory first, then in the global npm folder. A project install takes precedence over a global one.- Node.js on
PATH. - For
uip maestro bpmn compile --connectors-local, and foruip maestro bpmn checkwhen a connector library is available,@uipath/maestro-builder-sdk6.15.0 or later.
When the package is missing or older than the required version, the command fails with Result: "ConfigError" and exit code 1. Instructions gives the install command: npm install --save-dev @uipath/maestro-builder-sdk@latest when the outdated copy is installed in the project, otherwise npm install -g @uipath/maestro-builder-sdk@latest.
Zusammenfassung
uip maestro <family> compile <source> [-o, --output <file>] [--library <dir>] [--bindings <file>] [--connectors-local <dir>] [--no-check]
uip maestro <family> check <input> [--source] [--library <dir>] [--connectors-local <dir>] [--graph]
uip maestro <family> decompile <input> [-o, --output <file>] [--import <specifier>] [--strict] [--library <dir>] [--best-effort] [--style <style>] [--no-pipeline]
uip maestro <family> merge <edited> --original <file> [-o, --output <file>] [--baseline <file>]
uip maestro bpmn tidy <input> [-o, --output <file>]
uip maestro <family> compile <source> [-o, --output <file>] [--library <dir>] [--bindings <file>] [--connectors-local <dir>] [--no-check]
uip maestro <family> check <input> [--source] [--library <dir>] [--connectors-local <dir>] [--graph]
uip maestro <family> decompile <input> [-o, --output <file>] [--import <specifier>] [--strict] [--library <dir>] [--best-effort] [--style <style>] [--no-pipeline]
uip maestro <family> merge <edited> --original <file> [-o, --output <file>] [--baseline <file>]
uip maestro bpmn tidy <input> [-o, --output <file>]
<family> is flow, case, or bpmn. Some options apply to specific families only, as listed in each command's options table.
Alle Aufrufe berücksichtigen die globalen Optionen (--output, --output-filter, --log-level, --log-file). Austrittscodes folgen dem Standardvertrag.
Ausgabe
Each command returns Code: "<Family><Verb>", for example FlowCompile, CaseCheck, or BpmnMerge. Data holds the builder SDK's result with PascalCase keys. The SDK's progress messages go to stderr.
When the SDK reports an error, the command returns Result: "Failure" with the SDK's reason in Message, and exits with the SDK's exit code.
Connector library
compile, the flow and bpmn check, and the case decompile read the connector library:
--library <dir>sets the library directory.- Without
--library, the command uses the library thatuip maestro registry pulldownloaded. - When the
FLOW_SDK_LIBRARY_JSONenvironment variable is set and--libraryis not passed, the builder SDK reads the library from the variable.
--connectors-local <dir> points at the connection-resolved overlay that uip maestro registry prepare writes. Default: ./connectors-local.
compile
Compile an authored TypeScript source file to an artifact.
Argumente
<source>(required) — the authored source file.
Optionen
| Option | Families | Beschreibung |
|---|---|---|
-o, --output <file> | Alle | Output artifact path. |
--library <dir> | Alle | Connector library directory. Default: the pulled registry. |
--bindings <file> | Alle | bindings.json path. |
--connectors-local <dir> | Alle | Connection-resolved connector overlay. Default: ./connectors-local. |
--no-check | flow | Skip the source-level check. |
Beispiele
uip maestro flow compile Order.flow.ts --output Order.flow
uip maestro case compile Claims.case.ts --output caseplan.json
uip maestro bpmn compile Approval.bpmn.ts --output Approval.bpmn
uip maestro flow compile Order.flow.ts --output Order.flow
uip maestro case compile Claims.case.ts --output caseplan.json
uip maestro bpmn compile Approval.bpmn.ts --output Approval.bpmn
Datenform (--output json)
{
"Code": "FlowCompile",
"Data": {
"Path": "/work/Order.flow",
"Nodes": 3,
"Edges": 2,
"Sidecars": [],
"Errors": 0,
"Warnings": 0,
"Diagnostics": []
}
}
{
"Code": "FlowCompile",
"Data": {
"Path": "/work/Order.flow",
"Nodes": 3,
"Edges": 2,
"Sidecars": [],
"Errors": 0,
"Warnings": 0,
"Diagnostics": []
}
}
case compile returns { Path, Stages }. bpmn compile returns { Path, Elements }.
check
Check a source file for authoring errors before compiling it. To check a compiled artifact, use uip maestro <family> validate: flow, bpmn, or case.
Argumente
<input>(required) — the authored source file.
Optionen
| Option | Families | Beschreibung |
|---|---|---|
--source | Alle | Check authored TypeScript. |
--library <dir> | flow, bpmn | Connector library directory. Default: FLOW_SDK_LIBRARY_JSON, then the pulled library. |
--connectors-local <dir> | flow, bpmn | Connection-resolved connector overlay. Default: ./connectors-local. |
--graph | bpmn | Also print the resolved wiring: every element with the sequence flows leaving it. Implied flows are marked ~>. |
Beispiel
uip maestro flow check Order.flow.ts --source
uip maestro flow check Order.flow.ts --source
Datenform (--output json)
{
"Code": "FlowCheck",
"Data": { "Errors": 0, "Warnings": 0, "Diagnostics": [] }
}
{
"Code": "FlowCheck",
"Data": { "Errors": 0, "Warnings": 0, "Diagnostics": [] }
}
All three families return the same { Errors, Warnings, Diagnostics } shape.
decompile
Convert an artifact to authored TypeScript.
Argumente
<input>(required) — the artifact: a.flowfile, acaseplan.jsonfile, or a.bpmnfile.
Optionen
| Option | Families | Beschreibung |
|---|---|---|
-o, --output <file> | Alle | Output source path (.flow.ts, .case.ts, or .bpmn.ts). |
--import <specifier> | Alle | SDK import specifier in the generated source. |
--strict | flow | Fail on unsupported constructs. |
--library <dir> | case | Connector library directory. Default: the pulled registry. |
--best-effort | case | Emit a marked repair scaffold for unsupported constructs. |
--style <style> | bpmn | explicit (default) or nested. nested lifts boundary events, gateways, and event subprocesses into nesting constructs where the resulting graph is the same. |
--no-pipeline | flow, case | Do not write the pipeline helper (<name>.pipeline.mjs) next to the source. |
Beispiele
uip maestro flow decompile Order.flow --output Order.flow.ts
uip maestro case decompile caseplan.json --output Claims.case.ts
uip maestro bpmn decompile Approval/Approval.bpmn --output Approval.bpmn.ts --style nested
uip maestro flow decompile Order.flow --output Order.flow.ts
uip maestro case decompile caseplan.json --output Claims.case.ts
uip maestro bpmn decompile Approval/Approval.bpmn --output Approval.bpmn.ts --style nested
Datenform (--output json)
{
"Code": "FlowDecompile",
"Data": {
"Path": "/work/Order.flow.ts",
"Pipeline": "/work/Order.pipeline.mjs"
}
}
{
"Code": "FlowDecompile",
"Data": {
"Path": "/work/Order.flow.ts",
"Pipeline": "/work/Order.pipeline.mjs"
}
}
case decompile also returns Diagnostics. bpmn decompile returns { Path }.
merge
Merge an edited artifact into its original artifact.
Argumente
<edited>(required) — the edited artifact.
Optionen
| Option | Families | Beschreibung |
|---|---|---|
--original <file> | Alle | Original artifact to merge into. Required. |
-o, --output <file> | Alle | Merged output path. |
--baseline <file> | flow, bpmn | The compiled output of the unedited decompiled source. |
Beispiele
uip maestro flow merge Edited.flow --original Original.flow --output Merged.flow --baseline Baseline.flow
uip maestro case merge edited.caseplan.json --original original.caseplan.json --output merged.caseplan.json
# BPMN: elements you did not edit are kept byte for byte
uip maestro bpmn merge Edited.bpmn --original Original.bpmn --output Merged.bpmn --baseline Baseline.bpmn
uip maestro flow merge Edited.flow --original Original.flow --output Merged.flow --baseline Baseline.flow
uip maestro case merge edited.caseplan.json --original original.caseplan.json --output merged.caseplan.json
# BPMN: elements you did not edit are kept byte for byte
uip maestro bpmn merge Edited.bpmn --original Original.bpmn --output Merged.bpmn --baseline Baseline.bpmn
Datenform (--output json)
{
"Code": "BpmnMerge",
"Data": {
"Path": "/work/Merged.bpmn",
"Preserved": 5,
"Authored": 1,
"Removed": 0
}
}
{
"Code": "BpmnMerge",
"Data": {
"Path": "/work/Merged.bpmn",
"Preserved": 5,
"Authored": 1,
"Removed": 0
}
}
flow merge returns { Path, Nodes, Edges }. case merge returns { Path, Stages }.
uip maestro bpmn tidy
Add diagram layout to a compiled .bpmn file. To generate or replace the layout of any .bpmn file without the builder SDK, use uip maestro bpmn format.
Argumente
<input>(required) — the compiled.bpmnfile.
Optionen
| Option | Beschreibung |
|---|---|
-o, --output <file> | Output .bpmn path. |
Beispiel
uip maestro bpmn tidy Approval.bpmn --output Approval.tidied.bpmn
uip maestro bpmn tidy Approval.bpmn --output Approval.tidied.bpmn
Datenform (--output json)
{
"Code": "BpmnTidy",
"Data": { "Path": "/work/Approval.tidied.bpmn", "Shapes": 4 }
}
{
"Code": "BpmnTidy",
"Data": { "Path": "/work/Approval.tidied.bpmn", "Shapes": 4 }
}
Zugehörig
uip maestro registry— download, locate, search, and prepare the connector library.uip maestro flow init—--sdk-sourcewrites the authored source for a new Flow project.uip maestro flow,uip maestro case,uip maestro bpmn
- Anforderungen
- Zusammenfassung
- Ausgabe
- Connector library
- compile
- Argumente
- Optionen
- Beispiele
- Datenform (--output json)
- check
- Argumente
- Optionen
- Beispiel
- Datenform (--output json)
- decompile
- Argumente
- Optionen
- Beispiele
- Datenform (--output json)
- merge
- Argumente
- Optionen
- Beispiele
- Datenform (--output json)
- uip maestro bpmn tidy
- Argumente
- Optionen
- Beispiel
- Datenform (--output json)
- Zugehörig