@uipath/maestro-builder-sdk 6.22.0 → 6.23.0

package/dist/nodes/ai-patterns/flow/spec.d.ts

@@ -0,0 +1,75 @@
+/**
+ * The AI-pattern family's authoring types (`uipath.pattern.deep-rag`,
+ * `uipath.pattern.batch-transform`), and their kinds' entries in
+ * `FlowActionSpecs`. Moved from core/actions.ts in Phase 4 of
+ * docs/NODE_TYPE_ARCHITECTURE_DESIGN.md.
+ */
+import type { Expr } from '../../../core/expr.js';
+export interface SummarizeInputs {
+    /**
+     * The document to summarize — a whole **Flow Attachment** object
+     * (`{ ID, FullName, MimeType, Metadata }`), not a path, id or URL.
+     *
+     * In practice that is a `file`-typed flow input:
+     *
+     * ```ts
+     * flow('SummarizeDemo')
+     *   .input({ documentFile: types.file })
+     *   .step('summarizeContract', summarize({ attachment: input('documentFile'), … }))
+     * ```
+     *
+     * `out('start', 'documentFile')` is the same value written the way the CANVAS
+     * writes it (`$vars.start.output.documentFile`, resolved through the input's
+     * `triggerNodeId` binding). Both forms run — measured on the real service —
+     * so prefer whichever the task asks for; `out('start', …)` is what a
+     * designer-made flow looks like.
+     *
+     * The service reads the file's CONTENT, and refuses one it cannot treat as a
+     * document: a PDF summarizes, a plain `.txt` comes back
+     * `[460005] … "No valid files to use for Summarization."`
+     */
+    attachment: Expr;
+    /** What the summary should cover, e.g. `'Write a 5-bullet executive summary…'`. */
+    prompt: string | Expr;
+    /**
+     * Ask the service for per-claim citations. Each is
+     * `{ Ordinal, PageNumber, Source, Reference }` and lands in
+     * `out('<step>', 'content.Citations')`. Defaults to `false`.
+     */
+    returnCitations?: boolean;
+}
+/** One column Batch Transform appends to the CSV. */
+export interface OutputColumn {
+    /** The new column's header, e.g. `'Category'`. */
+    name: string;
+    /** What the model should put in it, e.g. `'One of: Utility, Software, Travel, Other'`. */
+    description: string;
+}
+export interface BatchTransformInputs {
+    /**
+     * The CSV to enrich — a whole **Flow Attachment** object, same shape and same
+     * two ways of referencing it as {@link SummarizeInputs.attachment}.
+     */
+    attachment: Expr;
+    /** How to process each row, e.g. `'Classify each row and write a one-line summary.'`. */
+    prompt: string | Expr;
+    /**
+     * The columns to add, in order. The node's own field name — an array of
+     * `{ name, description }`, one per new column.
+     */
+    outputColumns: OutputColumn[];
+    /** Let the model use web search while transforming. Defaults to `false`. */
+    enableWebSearchGrounding?: boolean;
+}
+declare module '../../../core/actions.js' {
+    interface FlowActionSpecs {
+        /** The spec {@link summarize} builds. */
+        summarize: {
+            inputs: SummarizeInputs;
+        };
+        /** The spec {@link batchTransform} builds. */
+        batchTransform: {
+            inputs: BatchTransformInputs;
+        };
+    }
+}

package/dist/nodes/ai-patterns/flow/spec.js

@@ -0,0 +1 @@
+export {};

package/dist/serialize.js

@@ -119,11 +119,6 @@ const NODE_TYPE = {
     doWhile: 'core.logic.dowhile',
     subflow: 'core.subflow',
     terminate: 'core.logic.terminate',
-    // The two AI patterns. `summarize()` emits `deep-rag`: the canvas name is
-    // "Summarize", the wire type is the backend's (`ECS.DeepRag`), and there is
-    // no `uipath.pattern.summarize` node type at all.
-    summarize: 'uipath.pattern.deep-rag',
-    batchTransform: 'uipath.pattern.batch-transform',
     end: 'core.control.end',
 };
 /**
@@ -3640,8 +3635,6 @@ export function bundledActionNodeType(spec) {
         case 'hitl': return hitlNodeType(spec.inputs);
         case 'inlineAgent': return INLINE_AGENT_TYPE;
         case 'subflow':
-        case 'summarize':
-        case 'batchTransform':
         case 'sendMessage':
         case 'waitForMessage':
         case 'conversationContext':
@@ -6069,39 +6062,6 @@ export function serialize(built, opts = {}) {
                 addEdge(scope, t, id);
             return [{ node: id, port: successPort(type) }];
         }
-        if (spec.kind === 'summarize' || spec.kind === 'batchTransform') {
-            // One emit path for both AI patterns: they differ in their definition and
-            // in which input fields they carry, and in nothing else. Each field is
-            // written under the NODE's own name, so the surface and the emitted file
-            // read alike.
-            const type = spec.kind === 'summarize' ? NODE_TYPE.summarize : NODE_TYPE.batchTransform;
-            const id = stepUid(scope, step.name);
-            const node = makeNode(type, id, step.name, { parentId, requestedVersion: step.options?.version });
-            // The resource model stays on the DEFINITION only. Both node types are
-            // `bpmn:ServiceTask`s whose `serviceType` the platform resolves from
-            // `definitions[]`, and every deployed instance of either carries no
-            // node-level `model` — v1's own structural checker fails a flow that has
-            // one. Same reason the three process-resource families delete theirs.
-            delete node.model;
-            node.inputs = spec.kind === 'summarize'
-                ? {
-                    attachment: renderValue(spec.inputs.attachment, scope.rename),
-                    prompt: renderValue(spec.inputs.prompt, scope.rename),
-                    returnCitations: spec.inputs.returnCitations ?? false,
-                }
-                : {
-                    attachment: renderValue(spec.inputs.attachment, scope.rename),
-                    prompt: renderValue(spec.inputs.prompt, scope.rename),
-                    enableWebSearchGrounding: spec.inputs.enableWebSearchGrounding ?? false,
-                    // Written through renderMap per column so an expression in a
-                    // description renders like every other input.
-                    outputColumns: spec.inputs.outputColumns.map((c) => renderMap(c, scope.rename)),
-                };
-            scope.nodes.push(node);
-            for (const t of tails)
-                addEdge(scope, t, id);
-            return [{ node: id, port: successPort(type) }];
-        }
         if (spec.kind === 'ixpExtract') {
             const s = spec.inputs;
             const def = perCallDefinition(spec); // ixpExtractDef: throws on an unparseable project

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/maestro-builder-sdk",
-  "version": "6.22.0",
+  "version": "6.23.0",
   "description": "Build UiPath Flow, Case, and BPMN artifacts by writing TypeScript.",
   "license": "MIT",
   "homepage": "https://docs.uipath.com/maestro",
@@ -92,5 +92,5 @@
     "@types/node": "^22.7.0",
     "esbuild": "^0.28.1"
   },
-  "gitref": "b090b1119c411ed2ffdefab1d258d629ff624a1f"
+  "gitref": "4e81a94f4009b646e93353cd0043286f725a4507"
 }