uipath-cli
latest
false
- Überblick
- Erste Schritte
- Konzepte
- Using UiPath CLI
- Anleitungen
- CI/CD recipes
- Befehlsreferenz
- Überblick
- Exitcodes
- Global options
- uip codedagent
- uip docsai
- add-test-data-entity
- add-test-data-queue
- add-test-data-variation
- analyze
- build
- Ein Projekt erstellen
- diff
- find-activities
- get-analyzer-rules
- get-default-activity-xaml
- get-errors
- get-manual-test-cases
- get-manual-test-steps
- get-versions
- get-workflow-example
- indicate-application
- indicate-element
- inspect-package
- install-data-fabric-entities
- install-or-update-packages
- list-data-fabric-entities
- list-workflow-examples
- pack
- restore
- run-file
- search-templates
- start-studio
- stop-execution
- uia
- uip traces
- Migration
- Reference & support
UiPath CLI user guide
Letzte Aktualisierung 7. Mai 2026
uip maestro init scaffolds a new Maestro project directory with a valid BPMN 2.0 starter and the metadata files Orchestrator expects for process-orchestration packages.
Synopsis
uip maestro init <name> [--force]
uip maestro init <name> [--force]
Honors global options. Exit codes follow the standard contract.
Argumente
<name>(required) — project folder name. Validated againstVALID_PROJECT_NAME_REGEX: letters, numbers, underscores (_), and hyphens (-) only.
Optionen
--force— initialize even if the target directory exists and is non-empty. Existing files are not cleared — files are written alongside; this is useful for reinitializing inside a pre-created folder.
Verhalten
Creates <name>/ in the current working directory and writes six files:
| Datei | Zweck |
|---|---|
project.uiproj | { "Name": "<name>", "ProjectType": "ProcessOrchestration" } |
operate.json | Runtime metadata — targetFramework: "Portable", contentType: "processOrchestration", runtimeOptions.isAttended: false. |
entry-points.json | One entry point pointing at Event_start inside the starter BPMN, with empty input/output schemas. |
bindings_v2.json | { "version": "2.0", "resources": [] }. |
package-descriptor.json | File manifest consumed by the packer. |
<name>.bpmn | Starter BPMN containing Event_start → _Implicit_EndEvent, wired with a uipath:entryPointId extension. |
The starter BPMN is parsed through bpmn-moddle before writing; if structural (non-UiPath-extension) warnings appear, the command fails with BPMN validation failed: ….
If <name> already exists and is non-empty and --force is not set, the command fails with an error.
Beispiele
# Create a new project in ./invoice-orchestration
uip maestro init invoice-orchestration
# Reinitialize into an existing non-empty folder
uip maestro init invoice-orchestration --force
# Create a new project in ./invoice-orchestration
uip maestro init invoice-orchestration
# Reinitialize into an existing non-empty folder
uip maestro init invoice-orchestration --force
Data shape (--output json)
{
"Code": "MaestroInit",
"Data": {
"Status": "Created successfully",
"Path": "/workspace/invoice-orchestration"
}
}
{
"Code": "MaestroInit",
"Data": {
"Status": "Created successfully",
"Path": "/workspace/invoice-orchestration"
}
}
On failure the response carries Result: "Failure", Message, and Instructions.
Siehe auch
uip maestro pack— pack the scaffolded projectuip maestro debug— run it via Studio Web- Maestro overview