Skip to content

fix(uipath-agents): keep IS tools on the catalog activity; route long-document research to Deep RAG - #4868

Merged
astridstaicu merged 3 commits into
mainfrom
fix/uipath-agents-is-catalog-object-deeprag-routing
Nov 18, 2026
Merged

astridstaicu merged 3 commits into
mainfrom
fix/uipath-agents-is-catalog-object-deeprag-routing

Conversation

@astridstaicu

@astridstaicu astridstaicu commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

Why

Two autopilot-sw-ga low-code use-case tasks fail on every Studio Web run (Nov 16 and Nov 17 dailies) and pass on the codex and claude nightlies.

  • helpdesk-jira-triage: the grader finds no Jira create-issue IS tool. The SW agent ran uip is typecache activities and saw Create Issue = curated_create_issue. It then listed issue types from the tenant-wide issuetype object (types 10005 and 10001, which aren't project AB's), and describe -f fields.project.key=AB -f fields.issuetype.id=<that> returned only project, issue type and key. Without summary or description it switched to the raw issue object and hand-wrote the tool on it. Both nightlies listed project/AB/issuetypes (10048), and the second describe then returned summary, description and the rest, so they built on curated_create_issue.
  • vendor-dd-deeprag: the agent added Analyze Files, and the grader wants deep-rag or an attachments context. The routing it read never mentions Deep RAG: the lowcode.md row "Add a built-in tool (Analyze Files)", the built-in-tools.md "When to Use" bullet (file content analysis means analyze-attachments), and analyze-attachments.md. The "Prefer deep-rag" decision exists only in deeprag/planning.md, which it never opened.

What

  • integration-service.md:

    • Build the tool on the catalog activity's ObjectName, never on another object for the same entity.
    • New "Fields that load after a selection" note: list each reference field's options through its own Reference.Path with earlier values filled in (project/AB/issuetypes), describe again with -f, and keep those selections as static parameters. This is how both passing agents built the tool.
  • lowcode.md, built-in-tools.md, analyze-attachments.md, SKILL.md: route research across long or multiple run-time documents with citations to Deep RAG, and keep Analyze Files for one-shot work on a short file.

  • agent-definition.md § Schema Types: a field with a fixed set of values (category, status, a P1–P4 scale) gets an enum, and "Add an Output Field" points there. With the Jira fix in place, helpdesk-jira-triage got past the Jira tool and failed on priority described as "Triage priority from P1 to P4.". Both nightly agents declared enum: [P1..P4]; the SW agents use enums only when the prompt says "one of …".

These are canonical files. The Studio Web flavor overrides none of these passages, so both trees change.

Verification

  • npm run skills:validate, skills:check-links and skills:build pass. Both new passages are in the built studioweb tree. check-sensitive-content.py is clean.
  • The Jira behaviour is taken from the eval transcripts: SW 2026-11-17_09-24-49, and nightlies 2026-11-17_04-23-30 and _04-23-38. I couldn't re-run it live: my tenant's Jira connection answers 401 from the provider.
  • SW eval run 14307930 (skills 90acfc2a, bridge 0.2.0-preview.20261117175908 with Autopilot#9524): vendor-dd-deeprag passed (0.95) and support-case-triage passed (0.98). helpdesk-jira-triage passed the Jira tool on curated_create_issue / project AB, the connection and memory checks, then failed on the priority enum, which the commit above addresses. A re-run with 613c05d9 is build 14317433.

🤖 Generated with Claude Code

…-document research to Deep RAG

Two Studio Web low-code use-case tasks failed on choices the skill steered:

- helpdesk-jira-triage: the agent left Jira's catalog activity
  (curated_create_issue) for the raw `issue` object, because the curated
  describe showed no summary/description. Those fields load only after the
  project and issue type are set, and the agent had picked issue types from
  the tenant-wide list instead of the project's own. The IS walkthrough now
  says to build on the activity's ObjectName and how to load dependent
  fields: list each reference field's options through its Reference.Path,
  describe again with -f, and keep the selections as static parameters.
- vendor-dd-deeprag: the routing the agent read (lowcode.md, built-in-tools
  "When to Use", analyze-attachments) named only Analyze Files; the
  "prefer deep-rag" rule sat in deeprag/planning.md. The routing now sends
  research across long or multiple documents with citations to Deep RAG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Claude finished @astridstaicu's task in 1m 7s —— View job


Summary

This PR fixes two autopilot-sw-ga routing failures in uipath-agents. (1) Integration Service tools now stay on the catalog activity's ObjectName, and the PR documents how fields that only load after a reference selection get discovered (Jira Create Issue). (2) Research across long or multiple run-time documents now routes to Deep RAG from SKILL.md, lowcode.md, built-in-tools.md and analyze-attachments.md.

Change-by-Change Review

1. references/lowcode/capabilities/integration-service/integration-service.md:280 — stay on catalog ObjectName

OK. The prohibition is clear, the reason ("Agent Builder offers only the catalog activity") is stated, and it forward-links to the Step 6 note.

2. references/lowcode/capabilities/integration-service/integration-service.md:305-309 — "Fields that load after a selection"

Medium: step 3 says to set the reference fields as static parameters, but the parameter rules this file already has (lines 160-167) only describe static for enum fields: value = an enum value, and enumValues = the {name, value} array. Line 161 also says reference fields keep their reference object and loadReferenceOptionsByDefault: true. For a static reference field such as fields.project.key=AB, an agent can't tell:

  • whether enumValues is null, [], or [{name:"AB", value:"AB"}]
  • whether reference / loadReferenceOptionsByDefault is kept or dropped
  • whether dynamic: false alone is enough

That file notes elsewhere that a wrong enumValues shape "passes uip agent validate but makes Studio Web silently drop the tool", so the same failure can happen here. Fix: add one bullet under "Parameter fieldVariant values" (or a short jsonc snippet in step 3) showing the exact shape of a static reference parameter, copied from the passing nightly transcripts' resource.json. Fix this →

Low: step 1 says "Pick each such reference field's value", but it doesn't say who picks. Step 3 and Step 4 have the agent present choices to the user. Say whether to present the run list options to the user or to choose from the task's stated project key or type.

3. references/lowcode/capabilities/built-in-tools/built-in-tools.md:9-13 — When to Use + new paragraph

Medium (Reference Pointer Discipline): the new paragraph at line 13 ("it handles larger files and returns citations, while analyze-attachments is a single synthesis pass with lower page limits. Enable only one of the two…") restates the deep-rag vs analyze-attachments row of deeprag/planning.md § Critical Decisions. The two copies already disagree. planning.md says "Do not enable deep-rag AND analyze-attachments if a single research pass suffices", which is a condition, while this paragraph says "Enable only one of the two for the same documents", which is unconditional. The updated When to Use bullets (lines 9-10) already do the routing and link to planning.md. Fix: delete line 13, or cut it to one bridging sentence that links to deeprag/planning.md § Critical Decisions.

4. references/lowcode/capabilities/built-in-tools/analyze-attachments.md:12

OK. It's a single bridging redirect with a link, and the link resolves.

5. references/lowcode/lowcode.md:101-102

OK. All links resolve (deeprag/planning.md, deeprag/impl-json.md). The "Batch Transform, Create File" list matches the Tool Registry. "the tool's walkthrough from its Tool Registry" as the secondary column is a bit vague, but it's acceptable.

6. SKILL.md:64

OK. The row and the new deeprag/planning.md link resolve, and the frontmatter is untouched.

What's Missing

  • No coder_eval task changes. That's fine: the existing autopilot-sw-ga tasks (helpdesk-jira-triage, vendor-dd-deeprag) are the regression tests. The PR's own "Next" step, an SW eval run with skillsRef set to this branch, is still the evidence needed before merge.
  • No example of the static reference parameter shape (see feat: new coded agent skills #2).

Area Ratings

Area Status Notes
Frontmatter OK Unchanged
E2E Tests OK Covered by existing SW use-case tasks; eval run pending
Skill Body OK One routing row updated
References & Assets Issue Static reference parameter shape is undefined (#2); duplicated deep-rag vs analyze-attachments rationale (#3)
Repo Hygiene OK Scoped to uipath-agents, no secrets or personal paths, no cross-skill links, no CODEOWNERS change needed

Issues for Manual Review

  • Check that uip is resources describe accepts the repeatable -f <field>=<value> flag. The verb snapshot only confirms that is resources describe and is resources run list exist, not their flags.
  • Check that uip is resources run list "<connector-key>" "project/AB/issuetypes" takes a slash path as its object argument, with no leading slash.
  • Check the exact static parameter JSON the passing nightlies produced for fields.project.key / fields.issuetype.id.

Conclusion

The direction is right and the change is tightly scoped. Approve once #2 is addressed with an explicit static-reference parameter shape, since without it the new instructions can produce a tool that Studio Web silently drops. #3 is a small dedupe.

astridstaicu and others added 2 commits November 18, 2026 09:56
helpdesk-jira-triage on Studio Web described `priority` as "Triage priority
from P1 to P4." and failed the output-contract check; both nightly agents
declared `enum: [P1, P2, P3, P4]`. The SW agents already use enums when a
prompt says "one of ...", but nothing in the skill says a closed set belongs
in `enum`. agent-definition.md § Schema Types now does, with an example, and
"Add an Output Field" points at it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s add instead of refresh

`uip solution resources refresh` always fails in Studio Web (no .uipx on
disk), so agents that followed the refresh step never declared their
Integration Service connection or memory space in the solution. The Studio
Web flavor now replaces those steps with `uip solution resources add
--source remote` (connections by --cloud-key) and a local list check.
Canonical text is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@astridstaicu
astridstaicu merged commit f394860 into main Nov 18, 2026
48 checks passed
@astridstaicu
astridstaicu deleted the fix/uipath-agents-is-catalog-object-deeprag-routing branch November 18, 2026 10:53
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.

1 participant