Skip to content

fix(uipath-solution): use actual UI label "Activate deployment" [CA-233] - #4869

Merged
rockymadden merged 1 commit into
mainfrom
fix/solution-activate-deployment-label
Nov 19, 2026
Merged

rockymadden merged 1 commit into
mainfrom
fix/solution-activate-deployment-label

Conversation

@roberts-cliff

@roberts-cliff roberts-cliff commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • The skill used "Setup activation" (derived from the NeedsSetupToActivate API status) where the actual Orchestrator UI button is Activate deployment. Agents relayed the wrong label to users.
  • Four occurrences across activate-and-manage.md, pack-and-deploy.md, and the studioweb flavor SKILL.md now say "Activate deployment" (the button label) or "activation setup" / "activation wizard" (the concept) where appropriate.
  • Found by PACT golden thread at step 29 (CA-233).

Test plan

  • grep -ri "Setup activation" skills/ skill-flavors/ returns nothing
  • Adversarial review clean (0/0/0/1 — one low observation on pronoun referent)
  • skill-lint CI passes

🤖 Generated with Claude Code

https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q

@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @roberts-cliff's task in 31s —— View job


Summary

Swaps the made-up UI label "Setup activation" (from the NeedsSetupToActivate API status) for the real Orchestrator button Activate deployment. Uses "activation setup" / "activation wizard" where the text means the concept, not the button. 4 lines across 3 files in uipath-solution.

Change-by-Change Review

1. skills/uipath-solution/references/pack-and-deploy.md:167

OK. The new parenthetical "(click Activate deployment on the deployment)" tells the agent what to relay. One small point, Low: the old sentence said "before the deployment can be activated", and the new one says "before it can be activated". The nearest noun is now "the deployment" inside the parenthetical, so the meaning is still right, but writing "before the deployment can be activated" again would be clearer. This is the low observation the PR body already mentions.

2. skills/uipath-solution/references/activate-and-manage.md:150

OK. The button label sits next to the existing Inactive (Needs setup) status text, so an agent can match what the user sees on screen.

3. skills/uipath-solution/references/activate-and-manage.md:153

OK. "An abandoned activation wizard" fits better: the bullet is about the wizard's ActivationSetup / Draft record, not the button.

4. skill-flavors/studioweb/uipath-solution/SKILL.md:23

OK. The edit stays inside the existing solution-lifecycle-steps replacement block. The canonical skills/uipath-solution/SKILL.md version of that block (lines 87–102) never contained the phrase, so the default and studioweb flavors still match each other. No marker boundaries changed.

What's Missing

Nothing identified.

  • grep -rni "setup activation" skills/ skill-flavors/ tests/ now finds nothing. No test task grades on the old string, so no task YAML needs updating.
  • The only other hit for "needs setup" is the real UI status Inactive (Needs setup), which is correct as written. Hits in uipath-genome are unrelated.

Area Ratings

Area Status Notes
Frontmatter OK Not touched
E2E Tests OK No new capability; no task depends on the old label
Skill Body OK Change stays inside the flavor block; canonical block not affected
References & Assets OK Anchor link #open-the-deployment-in-orchestrator not changed
Repo Hygiene OK Limited to uipath-solution; no secrets or paths

Issues for Manual Review

  • I can't check from here that the Orchestrator button really says Activate deployment, or that clicking it opens the activation-setup wizard for a deployment in Inactive (Needs setup). Confirm against the current Orchestrator UI (the CA-233 finding suggests it does).

Conclusion

Approve. The label fix is correct and kept to these 4 lines. The only open point is the optional Low wording change in pack-and-deploy.md:167.

The skill said "Setup activation" — a concept derived from the
NeedsSetupToActivate API status — but Orchestrator's button reads
"Activate deployment". Agents relayed the wrong label; PACT golden
thread caught it at step 29.

Four occurrences across activate-and-manage.md, pack-and-deploy.md,
and the studioweb flavor SKILL.md now say "Activate deployment" where
they instruct the user to click.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q
@roberts-cliff
roberts-cliff force-pushed the fix/solution-activate-deployment-label branch from e98c5ba to b4b2c3f Compare November 18, 2026 16:04

@tmatup tmatup left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. No blocking issues.

I checked that no "Setup activation" string remains anywhere in skills/ or skill-flavors/ at this head (git grep -i returns nothing). I also checked that each rewrite keeps the facts around it unchanged: NeedsSetupToActivate, the 4007 refusal, the Inactive (Needs setup) UI state, and the ActivationSetup / Draft exit.

One non-blocking gap (enabling layer). The CLI itself still tells agents "Setup activation". For example, uipath-cli packages/solution-tool/src/commands/deploy-run.ts:137: Or complete 'Setup activation' for 'my-deployment' in Orchestrator .... The same wording appears in the deploy run help text and the NextSteps examples. An agent that relays NextSteps will keep using the old label, and now the skill and the CLI name the same button differently. A follow-up CLI PR that says "Activate deployment" would fix this at the source. I can file it.

Not verified: that the Orchestrator button reads exactly "Activate deployment". I took that from CA-233 and did not check the live UI.


Review run with Claude Code; each finding was reproduced with a probe at the PR head.

@roberts-cliff

Copy link
Copy Markdown
Contributor Author

Thanks. On the non-blocker: agreed. deploy-run.ts:137, the deploy run help text and the NextSteps examples still say "Setup activation", so an agent that relays NextSteps will use the old label. This PR changes only the skill side. Please file the CLI follow-up as you offered. That change belongs in UiPath/cli, and this PR leaves it alone.

@rockymadden rockymadden left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approved: No remaining findings.

What

  • Uses the actual Activate deployment UI label in solution references and Studio Web guidance.

Axes

Axis Blockers Non-blockers Top finding
Correctness & logic 0 0 none
Code quality & simplicity 0 0 none
Types & contracts 0 0 none
Tests & validation 0 0 none
Security 0 0 none
Architecture & design 0 0 none
Error handling & resilience 0 0 none
Interface, docs & compatibility 0 0 none

Overall findings

  • None.

Validation

  • Checked CA-233, the UI source and all touched canonical/flavor passages. No drift found.
  • Tests and CI reviewed without local execution; current checks pass or skip.

tl;dr: The label matches the UI and both skill variants.

@rockymadden
rockymadden merged commit 2878f01 into main Nov 19, 2026
54 checks passed
@rockymadden
rockymadden deleted the fix/solution-activate-deployment-label branch November 19, 2026 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants