Repository navigation
fix(uipath-agents): keep IS tools on the catalog activity; route long-document research to Deep RAG - #4868
Conversation
…-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>
|
Claude finished @astridstaicu's task in 1m 7s —— View job SummaryThis PR fixes two Change-by-Change Review1.
|
| 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 describeaccepts the repeatable-f <field>=<value>flag. The verb snapshot only confirms thatis resources describeandis resources run listexist, 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
staticparameter JSON the passing nightlies produced forfields.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.
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>
Why
Two
autopilot-sw-galow-code use-case tasks fail on every Studio Web run (Nov 16 and Nov 17 dailies) and pass on the codex and claude nightlies.uip is typecache activitiesand saw Create Issue =curated_create_issue. It then listed issue types from the tenant-wideissuetypeobject (types 10005 and 10001, which aren't project AB's), anddescribe -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 rawissueobject and hand-wrote the tool on it. Both nightlies listedproject/AB/issuetypes(10048), and the second describe then returned summary, description and the rest, so they built oncurated_create_issue.deep-ragor an attachments context. The routing it read never mentions Deep RAG: thelowcode.mdrow "Add a built-in tool (Analyze Files)", thebuilt-in-tools.md"When to Use" bullet (file content analysis means analyze-attachments), andanalyze-attachments.md. The "Preferdeep-rag" decision exists only indeeprag/planning.md, which it never opened.What
integration-service.md:ObjectName, never on another object for the same entity.Reference.Pathwith earlier values filled in (project/AB/issuetypes), describe again with-f, and keep those selections asstaticparameters. 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 anenum, and "Add an Output Field" points there. With the Jira fix in place, helpdesk-jira-triage got past the Jira tool and failed onprioritydescribed as "Triage priority from P1 to P4.". Both nightly agents declaredenum: [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-linksandskills:buildpass. Both new passages are in the built studioweb tree.check-sensitive-content.pyis clean.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 oncurated_create_issue/ project AB, the connection and memory checks, then failed on the priority enum, which the commit above addresses. A re-run with613c05d9is build 14317433.🤖 Generated with Claude Code