Skip to main content

uip solution new

uip solution new scaffolds an empty UiPath solution on disk. It creates a directory named after the solution and writes a .uipx manifest with an empty Projects array, ready to receive projects via uip solution project add or uip solution project import.

Synopsis​

uip solution new <solutionName>

The command honours the global options and returns the standard exit codes.

Arguments​

  • <solutionName> (required) — Name or path for the new solution. A directory is created at this location; the .uipx file inside it takes the same base name. If the argument ends in .uipx, the extension is used as-is; otherwise .uipx is appended to the base name.

Options​

None beyond the global options.

Examples​

Minimal​

uip solution new my-solution

Creates ./my-solution/my-solution.uipx.

Specify a subdirectory​

uip solution new ./workspace/invoices-solution

Creates ./workspace/invoices-solution/invoices-solution.uipx.

Scripting — capture the generated path​

uip solution new my-solution --output-filter "Data.Path"

Combined with --output json, emits a single JSON string with the absolute path to the new .uipx, suitable for piping into follow-up commands.

Data shape (--output json)​

{
  "Code": "SolutionNew",
  "Data": {
    "Status": "Created successfully",
    "Path": "/workspace/my-solution/my-solution.uipx"
  }
}

The generated .uipx is a JSON file with the following shape:

{
  "DocVersion": "1.0.0",
  "StudioMinVersion": "2025.10.0",
  "SolutionId": "<auto-generated UUID>",
  "Projects": []
}

SolutionId is a freshly generated UUID. It becomes the identity used by uip solution upload to overwrite the solution in Studio Web on subsequent uploads.

See also​