@uipath/flow-tool 1.196.1 → 1.197.0-preview.59

package/dist/services/flow-validate-service.d.ts

@@ -101,6 +101,77 @@ export declare class FlowValidateService {
      * specific reason hydration could not fill the prompt fields.
      */
     private resolveAgentPrompts;
+    /**
+     * Inline-agent input-binding integrity (warning-only).
+     *
+     * The .flow→BPMN converter derives each agent `JobArguments` binding by
+     * structurally decoding the `agent.json` `inputSchema` property keys
+     * (`<node>__output__<field>` → `$vars.<node>.output.<field>`), NOT from
+     * `inputs.agentInputVariables`. So a populated `inputSchema` with an
+     * empty `agentInputVariables` is the canonical, correct shape for a
+     * hand- or AI-authored inline agent — it is never an error, and validate
+     * must not demand a redundant node-side binding. (`agentInputVariables`
+     * exists only to carry a legacy *manual* binding whose key diverges from
+     * the structural encoding; absence of one is normal.)
+     *
+     * The one actionable gap here is the inverse: the agent declares no
+     * inputs (`inputSchema` empty or absent) but the flow node binds some —
+     * typically a trigger wired into `agentInputVariables`. The agent has no
+     * `{{input.<key>}}` placeholders, so the runtime ignores every binding
+     * and the agent silently runs without the flow's inputs. Flagged as a
+     * warning.
+     *
+     * Prompt placeholders that cannot bind (a bare `{{key}}`, or `{{input.K}}`
+     * where `K` is undeclared) are caught separately by
+     * `validateAgentPromptInputRefs`.
+     */
+    private validateAgentInputBindings;
+    /**
+     * Build the warning for an inline agent that declares no inputs in its
+     * `inputSchema` while the flow node binds one or more under
+     * `agentInputVariables` (e.g. a trigger wired in). The runtime maps
+     * bindings to `{{input.<id>}}` placeholders; with none declared, every
+     * binding is dropped and the agent runs without the flow's inputs.
+     */
+    private buildIgnoredAgentInputsWarning;
+    /**
+     * Inline-agent prompt-reference integrity (the prompt-ref → schema
+     * direction).
+     *
+     * The other agent-input checks trust `inputSchema.properties` to know
+     * what the prompt reads. But the runtime only binds a `{{...}}` token
+     * when it is in the canonical `input.<key>` form AND `<key>` is declared
+     * in `inputSchema.properties`. Two ways a prompt token silently stays a
+     * literal string at runtime — even when the flow/JobArguments deliver
+     * the value — and this reads the actual `messages[].content` tokens to
+     * catch both:
+     *  - Missing namespace: a bare `{{key}}` (no `input.` prefix). The
+     *    runtime tokenizer keeps the inner text verbatim, so `{{key}}`
+     *    binds to a `key` variable, not the `input.<key>` the schema
+     *    expects. Always wrong — flagged regardless of the schema.
+     *  - Undeclared key: `{{input.K}}` where `K` is not in
+     *    `inputSchema.properties` (empty or incomplete schema). This is the
+     *    verified failure that schema-trusting validation let through.
+     */
+    private validateAgentPromptInputRefs;
+    /**
+     * Classify one prompt field's `{{...}}` tokens into malformed (not the
+     * canonical `input.<key>` form) and undeclared (`input.<key>` whose key
+     * is absent from `inputSchema.properties`), and build one error per
+     * non-empty bucket. `field` is the prompt field the tokens came from
+     * (`systemPrompt`/`userPrompt`), so the issue path sends the user to the
+     * right place.
+     */
+    private buildPromptInputRefIssues;
+    /**
+     * Return the declared-schema key a prompt variable token maps to, or
+     * `undefined` when the token is not the canonical `input.<key>` form.
+     * The token text must be exactly `input.` + a non-empty key with no
+     * surrounding whitespace (matching what `tokenizeContent` produces and
+     * what the runtime binds). `{{input.x}}` → `x`; bare `{{x}}`,
+     * `{{ input.x }}`, and `{{input.}}` → `undefined`.
+     */
+    private canonicalInputKey;
     /**
      * Decorate `[REQUIRED_FIELD] systemPrompt|userPrompt` validator errors
      * on inline-agent nodes with a diagnostic hint pinpointing why the