/uipath-vertical-solutions

name: uipath-vertical-solutions
description: "UiPath Vertical Solutions via `uip vss deploy` — guided deploy of an industry solution package such as FINS (Financial Services) Loan Setup (`fins.loan-setup`) or Lending QA/QC (`fins.qaqc-uipath`): fresh install, upgrade/downgrade, deploy job status/resume/cancel, Data Fabric seeding (`uip vss deploy seed`), setting up a deployed solution (such as the FINS role groups), and checking the deploying user's tenant and folder access. Diagnoses refused or paused deploy jobs. For packing/deploying your own `.uipx` with `uip solution`→uipath-solution; Orchestrator folders/queues/roles or Data Fabric records outside a deploy→uipath-platform; other Identity users/groups/external apps→uipath-admin; faulted runtime jobs→uipath-troubleshoot."
when_to_use: "User says 'deploy a vertical solution', 'deploy FINS Loan Setup', 'deploy LoanQAQC', 'uip vss deploy', 'upgrade the vertical solution', 'deploy job paused', 'resume the deploy', 'cancel the deploy job', 'seed the deployed solution', 'help me set up QA/QC', 'set up Loan Setup roles', 'what access do I need to deploy FINS', or shows a deploy error such as 'User doesn't have permissions SolutionDeployments.Create granted' or 'Seems like you don't have access on Orchestrator'."

UiPath Vertical Solutions Deploy

Guided `uip vss deploy` for a Vertical Solution: an industry solution package (such as FINS Loan Setup) that the Vertical Solutions service installs on a tenant. `uip vss deploy` submits a deploy job and watches it. The service runs the deploy in UiPath Cloud **as the identity that ran `uip login`**, with that identity's permissions.

Assume the user has never deployed a solution. You do the work: run the commands, read their output, and work out the options. The user only answers plain questions, one or two at a time, and says yes before anything changes. Explain terms the first time you use them: a *folder* is where Orchestrator keeps the solution's processes and apps; a *deployment* is one installed copy of a package.

> **Use the CLI. Don't hand-roll REST for deploy jobs.** `uip vss deploy` handles the deploy job's submit, polling, pauses, checkpoints and resume. A REST call to the Vertical Solutions service misses them, and a resubmit makes a second job (Critical Rule 2).

<!--skill-flavor:host-availability-extra:start-->

<!--skill-flavor:host-availability-extra:end-->

When to Use This Skill

• User wants to deploy a Vertical Solution package (FINS Loan Setup, Lending QA/QC, or another vertical's package), or says "uip vss deploy"
• User wants to upgrade or downgrade an installed Vertical Solution
• User asks for the status of a deploy job, or wants to resume or cancel one ("deploy job paused", "resume the deploy")
• User wants to seed a deployed solution's Data Fabric data with `uip vss deploy seed`
• User wants to set up a deployed solution, such as who may use its app ("help me set up QA/QC", "set up Loan Setup roles")
• User asks what access a deploy needs, or whether a user can deploy a package into a folder
• User shows a deploy refusal, such as `User doesn't have permissions SolutionDeployments.Create granted` or `Seems like you don't have access on Orchestrator`

Critical Rules

1. **Check the login first.** A deploy goes to the tenant of the current login, as that identity. `uip login` with a different account replaces the saved session, so check `uip login status` again after any login. 2. **Never run `uip vss deploy --yes` again to retry.** A second submit makes a separate job. Once a job exists, continue it with `uip vss deploy resume <JOB_ID>`. It restarts from the last checkpoint, and completed steps are not re-run. 3. **Fix access, then resume.** When a step is refused for a missing permission, have it granted (see rule 6), then resume the same job. A role change applies without a new login. An external application that was missing a scope must run `uip login` again before the resume. 4. **`cancel` does not roll back.** `uip vss deploy cancel <JOB_ID> --yes` stops the job. Steps already applied stay applied. 5. **Copy filled-in seed CSVs out first.** Every watched deploy or resume that succeeds writes the seed templates again, also with `--no-seed`, and replaces the CSVs in `./seeding/<PACKAGE_NAME>`. 6. **Do not change access without being asked.** Reading roles and permissions is fine. Assigning roles or editing a role or user changes the tenant: say what you would change and wait for the user to agree. 7. **Find answers with commands, not by digging.** Do not read the CLI source, call the service's API by hand, or search the disk for solution zips. The service deploys from its own feed. The vertical files and the dry run (step 5) give you everything else. 8. **Never pass `--yes` before the user says yes.** Run the deploy without `--yes` first: it checks everything and stops before it sends anything. Show the summary from step 6 and pass `--yes` only after the user agrees. The same holds for `seed --yes`. 9. **Pass `--no-interactive` and `--output json` to every `uip vss deploy` command you run.** `--no-interactive` keeps it from waiting on a prompt you cannot answer. Read `Result`, `Code`, `Data` and, on a failure, `Message` and `Instructions`.

The Guided Deploy

Work through these steps in order. Keep a short list of the answers so far, and show it again before the final yes.

1. Get ready

uip --version
uip vss deploy --help
uip login status --output json

<!--skill-flavor:cli-ready:start-->

• `command not found` / `uip: not found` / `'uip' is not recognized` → CLI not installed. Tell the user to run the official installer (`curl -fsSL https://download.uipath.com/uipath-cli/install.sh | bash` on macOS/Linux; `irm https://download.uipath.com/uipath-cli/install.ps1 | iex` in Windows PowerShell), then `uip login`, and stop until those succeed.
• `uip vss deploy --help` fails or does not list `cancel`, `resume`, `seed` and `status` → the CL