Skip to content

Commit cd16754

Browse files
roberts-cliffclaude
andcommitted
fix(uipath-maestro-case): add check caveat for expression recipient
The =vars. expression syntax on the recipient field is unverified by any existing example or test. Add a verification step (case check) and a fallback path in case the compiler treats it as a literal. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tiDkBvodTad2Je4FVfz4q
1 parent 962f13b commit cd16754

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

‎skills/uipath-maestro-case/references/case-runtime.md‎

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,14 +43,19 @@ make from syntax alone. Exact signatures remain in the generated API.
4343
recipient in the source and republishing the case.
4444

4545
When a request names a person or test mailbox as the recipient, wire it
46-
through a case **input** with a placeholder default instead of a literal:
46+
through a case **input** with a placeholder default instead of a literal.
47+
Declare the input, reference it in the `recipient` field, and verify with
48+
`case check --source` that the expression resolves:
4749

4850
```ts
49-
.input({ approver: types.string }) // caller supplies the real address
51+
.input({ approver: types.string })
5052
// ...
5153
.action({ ..., recipient: '=vars.start.output.approver' })
5254
```
5355

56+
If `check` reports the expression as a literal, use a script task to read
57+
the input into a variable and pass that variable's value instead.
58+
5459
Tell the user before publishing:
5560
1. The input default is a **test** value. It routes every action to that
5661
address until someone edits the case input defaults and republishes.

0 commit comments

Comments
 (0)