Repository navigation
🍒 [v1.207] fix(uipath-maestro-bpmn): fetch a record by a run-time key with an operation that needs no design-time lookups - #4996
Merged
rockymadden merged 1 commit intoNov 19, 2026
Conversation
…eration that needs no design-time lookups (#4897) * fix(uipath-maestro-bpmn): fetch a record by a run-time key with an operation that needs no design-time lookups A curated get (Jira Get Issue) also asks for lookups the caller never supplies (project, issue type). Agents filled them from inputs (LOOKUP_RUNTIME_VALUE, rejected at run time) or pinned one project (works for that project only). Point them at the object's generic Retrieve, which reads the record by its key. Adds an eval grading the outcome on the compiled BPMN. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * review round 1: find the right object, fallback, grader multi-node and jql, accurate LOOKUP_RUNTIME_VALUE wording Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * review round 2: cut the Needs fallback, general search hint, field reference, --limit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * review round 3: list every Retrieve on the connector, plain required inputs, ask when none Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * review round 4: headless default for the no-Retrieve case, read Data.Total Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * review round 5: say which value and where it is reported Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * review: grader requires a process-input key, a GET read and no literal project in jql A literal key wrapped in an expression, a project-pinned jql and a non-read operation all passed. Negative fixtures guard each. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
requested review from
a team,
astridstaicu,
dmetzgar and
tmatup
as code owners
November 19, 2026 15:30
dmetzgar
approved these changes
Nov 19, 2026
rockymadden
deleted the
claude-fix-bpmn-connections-dec910-CP-to-release-v1-207
branch
November 19, 2026 20:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
connectors.md: two lines after theLOOKUP_RUNTIME_VALUEnote. When a step reads a record by a key the process is given and the operation also needs lookups nobody supplies, never derive them from the key, and never pin one while a generic Retrieve whose required inputs are all plain can read the record; list the connector's Retrieves (registry search retrieve --connector <KEY> --limit 50 --output json, re-run with--limit <TOTAL>whenData.Totalis higher) and read each field reference; with none, ask the user, or, when nobody will answer, pick a listed value and name it onAssumed:. Studio Web flavor:registry describeneeds--objectfor a generic operation.New eval
connector_features/runtime_record_key+_shared/check_runtime_record_key.py: a Jira issue looked up by an input key, graded on the compiled BPMN (no node sendsproject/issuetype, run-time or pinned; some node reads by a run-time key, path parameter orjql).Why
Dogfood row 17 (Confluence 91373076800). Autopilot (stock skills ≈ main on these lines, Haiku 5.5, row-17 prompt verbatim; one clarifying question, answered "Slack: Send Message to Channel") built Jira curated
get-issuewithproject: =vars.projectKey,issuetype: =vars.issueType→checkwarningLOOKUP_RUNTIME_VALUE. The skill said "fix it in your source" without saying how; terminal agents on main derivedprojectfrom the key, or pinned one project.Row-19 lessons: what a repro showed
solution resources list --source remotebefore bindingresources add --cloud-keysucceeds; row 18's refused key is itself in the remote list, so the check would not have caught it. Refusal comes from Studio Web's ManageSolutionResources, not the CLIcheckEVENT_BYOA_UNVERIFIED.input(). How inputs are read is #6 (#4892)Evidence
Terminal coder-eval (claude-code, popoc; the preflight criterion fails locally only because popoc has no
Shared/uipath-maestro-flow):project/issuetypederived from the key.get-recordoncurated_issue,issueId: =vars.issueKey. An early, looser wording let the agent pin one project; the grader and the line were tightened after that run.get-recordonlists::members,checkclean; an earlier wording kept curatedget-subscriber, alsocheckclean. Shows no harm on another connector, not the rule firing. Not run on main.Autopilot after-run (branch build at 3b646b2, Haiku 5.5, row-17 prompt verbatim, new chat, Solution 73
a42ea244-b4cf-4687-f6f5-08df455df8a5):getBundledPluginReleases()=1.0.0-f2ff718ecaf8, equal to sha256(dist/index.json)f2ff718e…5ea. Serveduipath-maestro-bpmn/references/connectors.mdandSKILL.mdfrom :5052 match the build (sha13c30e6f0…,fb5e629d…).search-issues-by-jqlwithjql: "project = " + vars.projKey + " AND key = " + vars.issKey. Noproject/issuetypelookups, andcheckreports noLOOKUP_RUNTIME_VALUEon Jira. The new eval's grader passes on this output (OK: searchIssue reads the record by run-time ['jql'] alone)..input("projectKey"),.input("issueKey"),.input("channel").check/validatefindings:CONNECTION_BINDING_NOT_GUID×2 andMISSING_BINDING×2: both connections were left unbound by answer.LOOKUP_RUNTIME_VALUEon the Slackchannel: Autopilot warned about this before building, and the answer chose the runtime input.LOOKUP_LITERAL_IDonsend_as: bot: informational.1.0.0-a8b15ef850db.Unverified: a live debug run of
get-record(no own Jira connection on the test tenant).🤖 Generated with Claude Code
Automatically cherry-picked from #4897 to
release/v1.207by @rockymadden.