@uipath/skills 1.195.0 → 1.196.0

package/skills/uipath-rpa/SKILL.md

@@ -122,7 +122,7 @@ When the request is "automate this dialog/form" or "build a UI test from these m
 3. **Capture all targets** screen by screen via `uia-configure-target` and screen advancement ([§ Multi-Step UI Flows](references/uia-configure-target-workflows.md)).
 4. **Then enter authoring phase:** project-context discovery (the precondition above), analyzer rules (Critical Rule 3 — Authoring-phase start), write code, validate.
 
-Skip this path when the task has no UI surface (data transforms, IS connector calls, headless file/email automation). Also skip it when the task HAS a UI surface but **no live app to capture against** (app not installed, no GUI, capture deferred to a developer) — there is nothing to capture, so use the § Placeholder-Selector Stub Pattern above instead.
+Skip this path when the task has no UI surface (data transforms, IS connector calls, headless file/email automation). Also skip it when the task HAS a UI surface but **no live app to capture against** (app not installed, no GUI, capture deferred to a developer) — there is nothing to capture, so use the § Placeholder-Selector Stub Pattern above instead. The Window Baseline does not tell you if the app is installed and has a GUI — validate that separately (e.g. look for the executable on disk) or ask the user.
 
 ## Session Pre-warm
 
@@ -167,7 +167,7 @@ uip rpa activities find --query log --output json > /dev/null 2>&1 &
 7a. **[UIA] Verify UIA prerequisites before invoking `uia-configure-target`.** The minimum version and the prerequisite check live in [uia-prerequisites.md](references/uia-prerequisites.md) — read it and run that check first (do not hardcode the version from memory; that file is the only source of truth). If `UiPath.UIAutomation.Activities` is below the minimum or `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/skills/uia-configure-target/SKILL.md` is absent, the `uip rpa uia` CLI is unavailable — and **both** target capture and indication depend on it, so indication is *not* a fallback when the package itself is missing. Ask the user to install/upgrade per uia-prerequisites.md. If they decline or the package cannot be installed, fall back to the **Placeholder-Selector Stub Pattern** (§ above) — real activities with `TODO Indicate` markers need no CLI. Never silently route to a non-existent skill path. Use indication capture only when a compatible UIA package *is* installed but `uia-configure-target` cannot see the element; record `UI capture: indication-only` in the plan header to skip `uia-configure-target` in that case.
 8. **Use `--output json`** on all CLI commands whose output is parsed programmatically.
 8a. **`run` / `debug start` success/failure verdict comes from the outer `Result` (and equivalently the inner `HasErrors`), NEVER from any log entry's `Level`.** A successful workflow may emit `Log Message` activities at `Error` or `Warning` level as observability — those are workflow-emitted data, not CLI failures. Compile failures, validation failures, and unhandled runtime exceptions all flip `HasErrors` and propagate to the outer `Result`. Treating log-entry levels as a failure signal flips green runs to "failed" and burns retries on healthy workflows. See [cli-reference.md § run](references/cli-reference.md) and [debugging.md § Reading Debug Output Effectively](references/debugging.md).
-9. **For "leverage / reuse / find shared libraries" requests, search the tenant feed — not the local filesystem, NuGet.org, or keyword-permutation loops.** Run `uip resource libraries list --limit 500 --output-filter "<JMESPath>" --output json`. On zero results from the filtered call, take the fallback branch — do not re-keyword. Skip when an SDD already records §16 "Shared libraries referenced" or the user has said "no shared libraries" earlier in the session. See [tenant-library-search-guide.md](references/tenant-library-search-guide.md) for the full procedure.
+9. **For "leverage / reuse / find shared libraries" requests, search the tenant feed — not the local filesystem, NuGet.org, or keyword-permutation loops.** Run `uip or libraries list --limit 500 --output-filter "<JMESPath>" --output json`. On zero results from the filtered call, take the fallback branch — do not re-keyword. Skip when an SDD already records §16 "Shared libraries referenced" or the user has said "no shared libraries" earlier in the session. See [tenant-library-search-guide.md](references/tenant-library-search-guide.md) for the full procedure.
 10. **Register every test case file in `project.json` → `designOptions.fileInfoCollection`.** Applies to both XAML and coded test cases. Required keys, GUID format, JSON snippet, and full schema (including `dataVariationFilePath` for data-driven and `publishAsTestCase` for coded): [references/testing-guide.md § project.json Registration](references/testing-guide.md) and [assets/json-template.md](assets/json-template.md).
 
 11. **Test case structure: Given-When-Then.** Applies to both XAML and coded test cases. See [references/testing-guide.md § XAML Test Case Structure](references/testing-guide.md) for the canonical patterns (the section's lead also points to the coded variant in `coded/operations-guide.md`).
@@ -187,7 +187,7 @@ uip rpa activities find --query log --output json > /dev/null 2>&1 &
 
 ### Destination Preflight (Both Modes)
 
-**Studio Web destination → Solution-wrapped deliverable, not a bare project.** Studio Web ingests Solutions only; a bare project folder is invisible in both SW workspace tabs. Treat these phrases as SW signals in the request: "Studio Web", "SW", "upload to web", "browser editor", "cloud workspace edit". On match, build the RPA project normally per the rest of this skill, then hand off to `uipath-solution` to wrap and ship it: `uip solution new <NAME>` → `uip solution project import --source <PROJECT_DIR> --solutionFile <SOLUTION>.uipx` → `uip solution upload <SOLUTION_DIR>`. The final deliverable is the Solution, not the bare project folder. Local execution (`uip rpa run`) and Orchestrator publish (`uip rpa publish`) are fine with a bare project — only an SW destination changes the deliverable shape.
+**Studio Web destination → Solution-wrapped deliverable, not a bare project.** Studio Web ingests Solutions only; a bare project folder is invisible in both SW workspace tabs. Treat these phrases as SW signals in the request: "Studio Web", "SW", "upload to web", "browser editor", "cloud workspace edit". On match, build the RPA project normally per the rest of this skill, then hand off to `uipath-solution` to wrap and ship it: `uip solution init <NAME>` → `uip solution project import "<PROJECT_DIR>" --solutionFile <SOLUTION>.uipx` → `uip solution upload "<SOLUTION_DIR>"`. The final deliverable is the Solution, not the bare project folder. Local execution (`uip rpa run`) and the Orchestrator package flow (`uip rpa pack` → `uip or packages upload` — there is no `uip rpa publish`) are fine with a bare project — only an SW destination changes the deliverable shape.
 
 ### Execution Discipline (Both Modes)
 
@@ -265,10 +265,14 @@ uip rpa activities find --query log --output json > /dev/null 2>&1 &
 | **Use execution templates** | XAML | [testing-guide.md § Execution Templates](references/testing-guide.md) |
 | **Create/edit XAML workflow** | XAML | [xaml/workflow-guide.md](references/xaml/workflow-guide.md) → [xaml/xaml-basics-and-rules.md](references/xaml/xaml-basics-and-rules.md) |
 | **Use a common activity** (`Sequence` / `If` / `Switch<T>` / `TryCatch` / `While` / `DoWhile` / `ForEach<T>` / `Assign` / `LogMessage` / `WriteLine` / `Delay` / `Throw` / `Rethrow`) | XAML | [common-activity-card.md](references/common-activity-card.md) |
-| **Create Flowchart/StateMachine/LRW** | XAML | [xaml/workflow-guide.md](references/xaml/workflow-guide.md) → [xaml/canvas-layout-guide.md](references/xaml/canvas-layout-guide.md) |
+| **Create Flowchart/StateMachine** | XAML | [xaml/workflow-guide.md](references/xaml/workflow-guide.md) → [xaml/canvas-layout-guide.md](references/xaml/canvas-layout-guide.md) |
+| **Create/edit Long Running Workflow (ProcessDiagram)** | XAML | [xaml/long-running-workflow-guide.md](references/xaml/long-running-workflow-guide.md) → [xaml/canvas-layout-guide.md](references/xaml/canvas-layout-guide.md) |
 | **Write UI automation** | Both | [ui-automation-guide.md](references/ui-automation-guide.md) → [uia-configure-target-workflows.md](references/uia-configure-target-workflows.md) |
 | **Build multi-screen UIA XAML workflow** | XAML | [ui-automation-guide.md](references/ui-automation-guide.md) → [uia-configure-target-workflows.md § Multi-Step UI Flows](references/uia-configure-target-workflows.md) |
+| **Share Object Repository selectors across projects (UI Library)** | Both | [ui-automation-guide.md § Object Repository as a Published UI Library](references/ui-automation-guide.md) |
 | **Use Excel/Word/Mail/etc.** | Both | Service table below → `.local/docs/packages/{PackageId}/` → fallback: `references/activity-docs/{PackageId}/{closest}/` |
+| **Use Data Fabric entities** | XAML | [xaml/workflow-guide.md](references/xaml/workflow-guide.md) → [activity-docs overview](references/activity-docs/UiPath.DataService.Activities/overview.md) |
+| **Query Data Fabric with filters** | XAML | [data-service-filter-builder-guide.md](references/activity-docs/UiPath.DataService.Activities/guides/data-service-filter-builder-guide.md) → [QueryEntityRecords](references/activity-docs/UiPath.DataService.Activities/activities/QueryEntityRecords.md) |
 | **Call an IS connector (coded)** | Coded | [coded/integration-service-guide.md](references/coded/integration-service-guide.md) |
 | **Call an IS connector (XAML)** | XAML | [is-connector-xaml-guide.md](references/is-connector-xaml-guide.md) → [connector-capabilities.md](references/connector-capabilities.md) |
 | **Build an event-triggered workflow** (O365 / Gmail / Salesforce / Jira / Slack / ServiceNow / time / queue / file watcher / UI click) | XAML | [trigger-pattern-guide.md](references/trigger-pattern-guide.md) → `activity-docs/{PackageId}/{closest}/activities/<TriggerActivity>.md` |
@@ -280,6 +284,8 @@ uip rpa activities find --query log --output json > /dev/null 2>&1 &
 | **List project best-practice / analyzer rules** | Both | [cli-reference.md § analyzer-rules list](references/cli-reference.md) |
 | **Add a NuGet package** | Coded | [coded/operations-guide.md § Add Dependency](references/coded/operations-guide.md) → [coded/third-party-packages-guide.md](references/coded/third-party-packages-guide.md) |
 | **Find / reuse existing tenant libraries** | Both | [tenant-library-search-guide.md](references/tenant-library-search-guide.md) |
+| **Extract reusable logic into a library** | Both | [library-authoring-guide.md](references/library-authoring-guide.md) — public-workflow contract, argument naming, private helpers |
+| **Publish a library** | Both | [library-authoring-guide.md § Pack & Publish](references/library-authoring-guide.md) — tenant libraries feed, versioning |
 | **Invoke a PowerShell script from a workflow** | Both | [powershell-interop-guide.md](references/powershell-interop-guide.md) |
 | **List / install Data Fabric entities** | Both | [cli-reference.md § Data Fabric Entities](references/cli-reference.md) |
 | **Discover activity APIs** | Coded | [coded/inspect-package-guide.md](references/coded/inspect-package-guide.md) |
@@ -345,7 +351,7 @@ XAML workflows follow a **discovery-first, phase-based approach**: Discovery →
 | **Sequence** | Linear step-by-step logic; most common for simple automations |
 | **Flowchart** | Branching/looping logic with multiple decision points |
 | **State Machine** | Long-running processes with distinct states and transitions |
-| **Long Running Workflow** | BPMN-style horizontal flow; event-driven processes with long waits |
+| **Long Running Workflow** | BPMN-style horizontal flow; event-driven processes with long waits. Requires `UiPath.FlowchartBuilder.Activities` — see [xaml/long-running-workflow-guide.md](references/xaml/long-running-workflow-guide.md) |
 
 ### Expression Language
 
@@ -370,6 +376,8 @@ Check `expressionLanguage` in `project.json`. VB.NET uses `[brackets]` for expre
 | Assign | built-in | Set variable/argument values |
 | For Each | built-in | Iterate over a collection |
 | Invoke Workflow File | built-in | Call another workflow file |
+| Create Entity Record | `UiPath.DataService.Activities` | Create a Data Fabric entity record |
+| Query Entity Records | `UiPath.DataService.Activities` | Query Data Fabric records with filters — see [filter builder guide](references/activity-docs/UiPath.DataService.Activities/guides/data-service-filter-builder-guide.md) |
 
 ### XAML File Anatomy
 
@@ -383,7 +391,9 @@ The XAML file anatomy template (namespace declarations, root Activity element, b
 - [xaml/csharp-activity-binding-guide.md](references/xaml/csharp-activity-binding-guide.md) — Canonical C# binding forms per common activity property (LogMessage, GetText, StartProcess, …) — flat lookup table + recipes
 - [xaml/csharp-expression-pitfalls.md](references/xaml/csharp-expression-pitfalls.md) — C#-specific expression failures (attribute-form VB JIT, ThrowIfNotInTree, OutArgument parse errors)
 - [xaml/canvas-layout-guide.md](references/xaml/canvas-layout-guide.md) — Flowchart, State Machine, and Long Running Workflow canvas layout with ViewState
+- [xaml/long-running-workflow-guide.md](references/xaml/long-running-workflow-guide.md) — LRW package dependency, node vocabulary, gateway patterns, suspend/resume persistence
 - [xaml/jit-custom-types-schema.md](references/xaml/jit-custom-types-schema.md) — JIT custom type discovery
+- [library-authoring-guide.md](references/library-authoring-guide.md) — Produce reusable libraries: public-workflow contract, activity layout sidecar (display name, icon, widgets), error contract, SemVer, pack & publish to the libraries feed
 
 ### Multi-Screen UI Automation Workflows
 
@@ -406,7 +416,7 @@ Check `project.json` → `dependencies` for the required package.
 
 ```bash
 uip rpa packages versions --package-id <PackageId> --include-prerelease --project-dir "<PROJECT_DIR>" --output json
-uip rpa packages install --packages '[{"id":"<PackageId>","version":"<LATEST_VERSION>"}]' --project-dir "<PROJECT_DIR>" --output json
+uip rpa packages install --packages 'id=<PackageId>,version=<LATEST_VERSION>' --project-dir "<PROJECT_DIR>" --output json
 ```
 
 ### Step 2 — Find activity docs (priority order)

package/skills/uipath-rpa/references/activity-docs/UiPath.DataService.Activities/activities/CreateEntityRecord.md

@@ -0,0 +1,149 @@
+# Create Entity Record
+
+`UiPath.DataService.Activities.CreateEntityRecord<TEntity>`
+
+**Package:** `UiPath.DataService.Activities`
+
+Creates a new record in a Data Fabric entity.
+
+**Category:** Data Service.Entity Record
+
+> **Single vs batch — use this only for ONE record.** For N records collected at runtime, use [CreateMultipleEntityRecords](CreateMultipleEntityRecords.md) — one HTTP request and per-record failure reporting via `FailedRecords`. Calling `CreateEntityRecord` inside a `ForEach` is a known performance anti-pattern. Full decision guide: [overview — When to Use Batch vs Single-Record Activities](../overview.md#when-to-use-batch-vs-single-record-activities).
+
+## Properties
+
+`x:TypeArguments` — concrete entity type, e.g. `local:EntityName`. Required at activity declaration.
+
+### Input
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `EntityId` | `InArgument<Guid>` | Yes | — | Entity GUID from `EntitiesStore.json` |
+| `InputEntityInFieldView` | `InArgument<TEntity>` | Yes | — | Object-initializer expression constructing the entity (runtime reads this) |
+| `InputEntity` | `InArgument<TEntity>` | No | — | Not recommended — Studio never syncs `SelectedFields` to this property, causing desync |
+| `State` | `RecordState` | Yes | — | Contains `SelectedFields` with field GUIDs and values (Studio card UI reads this) |
+| `ExpansionDepth` | `InArgument<int>` | No | `2` | Depth of relationship expansion in response (range: 1–3, max `3`). On write, relationship fields take **only** the target record's Id GUID — see [overview § Relationship Fields & ExpansionDepth](../overview.md#relationship-fields--expansiondepth) |
+
+### Output
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `OutputEntity` | `OutArgument<TEntity>` | No | — | Receives the created record with server-assigned ID |
+
+### Configuration
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `IsInRecordView` | `InArgument<bool>` | Yes | — | Set to `[False]` — makes runtime read `InputEntityInFieldView` |
+| `VisibleDynamicPropertiesInfo` | `InArgument<string>` | No | `{x:Null}` | Always set to `{x:Null}` |
+
+### Common
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueOnError` | `InArgument<bool>` | No | `false` | Continue workflow on error |
+| `TimeoutInMs` | `InArgument<int>` | No | `30000` | Timeout in milliseconds |
+
+> **Solution scope properties** (`ScopeValue`, `SolutionEntityKey`, `SolutionEntityName`) only apply when the project has a SolutionId. For standalone projects, omit them. See [overview — Solution Scope Properties](../overview.md#solution-scope-properties-conditional) and [Solution Context](../overview.md#solution-context-folder-vs-tenant-scope).
+
+## Field Binding — Two Required Components
+
+For Create and Update activities, set `IsInRecordView="[False]"` and populate two things:
+
+1. **`InputEntityInFieldView`** — object-initializer expression constructing the entity with field values. The runtime evaluates this expression and sends it to the Data Service API.
+2. **`State` with `RecordState.SelectedFields`** — declares each field with its GUID from `EntitiesStore.json` and its value. Studio's card UI reads this to render per-field editors.
+
+Studio syncs `SelectedFields` → `InputEntityInFieldView` on file load, keeping them aligned. Do NOT use `InputEntity` — Studio never syncs `SelectedFields` to it, which causes the card UI to show one value while the runtime uses a stale one.
+
+## RecordState and DynamicEntityField
+
+`RecordState` properties:
+
+| Property | Type | Description |
+|----------|------|-------------|
+| `IsInRecordView` | `bool` | Set to `False` |
+| `RequiredFieldCount` | `int` | Count of `DynamicEntityField` entries where `IsRequired="True"` |
+| `SelectedFields` | `IList<DynamicEntityField>` | List of field declarations |
+
+`DynamicEntityField` properties:
+
+| Property | Type | Description |
+|----------|------|-------------|
+| `Id` | `Guid` | Field GUID from `EntitiesStore.json` → `Fields[].Id` |
+| `Name` | `string` | Field name from `EntitiesStore.json` → `Fields[].Name` |
+| `IsRequired` | `bool` | Whether the field is required |
+| `ArgumentValue` | `Argument` | The value as `InArgument` with appropriate `x:TypeArguments` |
+
+## XAML Example (VB.NET expression language)
+
+> This snippet uses the `udam:` prefix (`RecordState`, `DynamicEntityField`). Ensure `xmlns:udam` is declared on the root `<Activity>` element — see [overview — XAML Namespace Declarations](../overview.md#xaml-namespace-declarations).
+
+```xml
+<uda:CreateEntityRecord
+    x:TypeArguments="local:ENTITY_NAME"
+    OutputEntity="{x:Null}"
+    VisibleDynamicPropertiesInfo="{x:Null}"
+    ContinueOnError="False"
+    DisplayName="Create ENTITY_NAME Record"
+    EntityId="ENTITY_GUID"
+    ExpansionDepth="2"
+    InputEntityInFieldView="[New ENTITY_NAME() With {.FIELD_A = &quot;valueA&quot;, .FIELD_B = 42}]"
+    IsInRecordView="[False]"
+    TimeoutInMs="30000">
+  <uda:CreateEntityRecord.State>
+    <udam:RecordState IsInRecordView="False" RequiredFieldCount="REQUIRED_COUNT">
+      <udam:RecordState.SelectedFields>
+        <scg:List x:TypeArguments="udam:DynamicEntityField">
+          <udam:DynamicEntityField Id="FIELD_A_GUID" IsRequired="True" Name="FIELD_A">
+            <udam:DynamicEntityField.ArgumentValue>
+              <InArgument x:TypeArguments="x:String">[&quot;valueA&quot;]</InArgument>
+            </udam:DynamicEntityField.ArgumentValue>
+          </udam:DynamicEntityField>
+          <udam:DynamicEntityField Id="FIELD_B_GUID" IsRequired="False" Name="FIELD_B">
+            <udam:DynamicEntityField.ArgumentValue>
+              <InArgument x:TypeArguments="x:Int32">[42]</InArgument>
+            </udam:DynamicEntityField.ArgumentValue>
+          </udam:DynamicEntityField>
+        </scg:List>
+      </udam:RecordState.SelectedFields>
+    </udam:RecordState>
+  </uda:CreateEntityRecord.State>
+</uda:CreateEntityRecord>
+```
+
+Replace: `ENTITY_NAME` (entity class), `ENTITY_GUID` (from `EntitiesStore.json` → `Entities[].Id`), `FIELD_A`/`FIELD_B` (field names), `FIELD_A_GUID`/`FIELD_B_GUID` (from `Fields[].Id`), `REQUIRED_COUNT` (count of required fields).
+
+## Key Rules
+
+- Set `IsInRecordView="[False]"` and populate both `InputEntityInFieldView` and `RecordState.SelectedFields` — do NOT use `InputEntity`
+- Include every required non-system field (`IsRequired: true` AND `IsSystemField: false`) in both `SelectedFields` and the `InputEntityInFieldView` expression — omitting a required field fails validation
+- `RequiredFieldCount` must equal the count of `DynamicEntityField` entries with `IsRequired="True"`
+- **Empty records are valid.** If the entity has no required non-system fields, use `RequiredFieldCount="0"` with an empty `SelectedFields` list (`Capacity="0"`), and `InputEntityInFieldView="[New ENTITY_NAME()]"` with no field initializers. This is common for entities with only a file-type field or all-optional fields
+- `VisibleDynamicPropertiesInfo` must always be set to `{x:Null}` — the type `DynamicPropertiesInfo` is not public
+- Entity fields cannot be set as direct activity properties — `<uda:CreateEntityRecord.FieldName>` produces `Cannot set unknown member`
+
+## XAML Example — Empty Record (No Required Fields)
+
+```xml
+<uda:CreateEntityRecord
+    x:TypeArguments="local:ENTITY_NAME"
+    OutputEntity="{x:Null}"
+    VisibleDynamicPropertiesInfo="{x:Null}"
+    ContinueOnError="False"
+    DisplayName="Create Empty ENTITY_NAME Record"
+    EntityId="ENTITY_GUID"
+    ExpansionDepth="2"
+    InputEntityInFieldView="[New ENTITY_NAME()]"
+    IsInRecordView="[False]"
+    TimeoutInMs="30000">
+  <uda:CreateEntityRecord.State>
+    <udam:RecordState IsInRecordView="False" RequiredFieldCount="0">
+      <udam:RecordState.SelectedFields>
+        <scg:List x:TypeArguments="udam:DynamicEntityField" Capacity="0" />
+      </udam:RecordState.SelectedFields>
+    </udam:RecordState>
+  </uda:CreateEntityRecord.State>
+</uda:CreateEntityRecord>
+```
+
+Use this pattern for entities where all non-system fields are optional (e.g., a file-only entity where the file is uploaded separately via `UploadFileToRecordField`).

package/skills/uipath-rpa/references/activity-docs/UiPath.DataService.Activities/activities/CreateMultipleEntityRecords.md

@@ -0,0 +1,67 @@
+# Create Multiple Entity Records
+
+`UiPath.DataService.Activities.CreateMultipleEntityRecords<TEntity>`
+
+**Package:** `UiPath.DataService.Activities`
+
+Creates multiple records in a Data Fabric entity in a single batch operation.
+
+**Category:** Data Service.Batch
+
+> **Batch vs single — use this for N records.** For exactly one record with design-time field bindings, use [CreateEntityRecord](CreateEntityRecord.md) — it exposes Studio's card UI via `RecordState.SelectedFields`. Picking batch for a single known record adds collection construction and `Tuple<string, TEntity>` unpacking for no gain. Full decision guide: [overview — When to Use Batch vs Single-Record Activities](../overview.md#when-to-use-batch-vs-single-record-activities).
+
+## Properties
+
+`x:TypeArguments` — concrete entity type, e.g. `local:EntityName`. Required at activity declaration.
+
+### Input
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `EntityId` | `InArgument<Guid>` | Yes | — | Entity GUID from `EntitiesStore.json` |
+| `InputRecords` | `InArgument<ICollection<TEntity>>` | Yes | — | Collection of entity objects to create (`[RequiredArgument]`) |
+| `ExpansionDepth` | `InArgument<int>` | No | `2` | Depth of relationship expansion in response (range: 1–3, max `3`). On write, relationship fields on each input entity take **only** the target record's Id GUID — see [overview § Relationship Fields & ExpansionDepth](../overview.md#relationship-fields--expansiondepth) |
+
+### Output
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `OutputRecords` | `OutArgument<IList<TEntity>>` | No | — | Successfully created records |
+| `FailedRecords` | `OutArgument<IList<Tuple<string, TEntity>>>` | No | — | Failed records with error messages |
+
+### Configuration
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueBatchOnFailure` | `InArgument<bool>` | No | `true` | If `true`, continues processing remaining records when one fails; if `false`, stops on first failure |
+
+### Common
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueOnError` | `InArgument<bool>` | No | `false` | Continue workflow on error |
+| `TimeoutInMs` | `InArgument<int>` | No | `30000` | Timeout in milliseconds |
+
+> **Solution scope properties** (`ScopeValue`, `SolutionEntityKey`, `SolutionEntityName`) only apply when the project has a SolutionId. For standalone projects, omit them. See [overview — Solution Scope Properties](../overview.md#solution-scope-properties-conditional) and [Solution Context](../overview.md#solution-context-folder-vs-tenant-scope).
+
+## XAML Example
+
+```xml
+<uda:CreateMultipleEntityRecords
+    x:TypeArguments="local:ENTITY_NAME"
+    ContinueOnError="False"
+    DisplayName="Create Multiple ENTITY_NAME Records"
+    EntityId="ENTITY_GUID"
+    ExpansionDepth="2"
+    ContinueBatchOnFailure="True"
+    InputRecords="[recordsCollection]"
+    OutputRecords="[successRecords]"
+    FailedRecords="[failedRecords]"
+    TimeoutInMs="30000" />
+```
+
+## Key Rules
+
+- `FailedRecords` contains `Tuple<string, TEntity>` — `Item1` is the error message, `Item2` is the failed record
+- If any records fail and `ContinueBatchOnFailure` is `true`, the activity throws after processing all records with a message indicating how many failed
+- The `InputRecords` collection must contain fully constructed entity objects (same as `InputEntity` for single creates)

package/skills/uipath-rpa/references/activity-docs/UiPath.DataService.Activities/activities/DeleteEntityRecord.md

@@ -0,0 +1,44 @@
+# Delete Entity Record
+
+`UiPath.DataService.Activities.DeleteEntityRecord<TEntity>`
+
+**Package:** `UiPath.DataService.Activities`
+
+Deletes a record from a Data Fabric entity by record ID.
+
+**Category:** Data Service.Entity Record
+
+> **Single vs batch — use this only for ONE record.** For N records, use [DeleteMultipleEntityRecords](DeleteMultipleEntityRecords.md) — accepts an `ICollection<Guid>`, makes one HTTP call, and returns failed IDs via `FailedRecords`. Deleting inside a `ForEach` loop is a performance anti-pattern. Full decision guide: [overview — When to Use Batch vs Single-Record Activities](../overview.md#when-to-use-batch-vs-single-record-activities).
+
+## Properties
+
+`x:TypeArguments` — concrete entity type, e.g. `local:EntityName`. Required at activity declaration.
+
+### Input
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `EntityId` | `InArgument<Guid>` | Yes | — | Entity GUID from `EntitiesStore.json` (marked `[RequiredArgument]`) |
+| `RecordId` | `InArgument<Guid>` | Yes | — | GUID of the record to delete |
+| `InputEntity` | `InArgument<TEntity>` | No | — | Entity object (alternative to RecordId for type resolution) |
+
+### Common
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueOnError` | `InArgument<bool>` | No | `false` | Continue workflow on error |
+| `TimeoutInMs` | `InArgument<int>` | No | `30000` | Timeout in milliseconds |
+
+> **Solution scope properties** (`ScopeValue`, `SolutionEntityKey`, `SolutionEntityName`) only apply when the project has a SolutionId. For standalone projects, omit them. See [overview — Solution Scope Properties](../overview.md#solution-scope-properties-conditional) and [Solution Context](../overview.md#solution-context-folder-vs-tenant-scope).
+
+## XAML Example
+
+```xml
+<uda:DeleteEntityRecord
+    x:TypeArguments="local:ENTITY_NAME"
+    ContinueOnError="False"
+    DisplayName="Delete ENTITY_NAME Record"
+    EntityId="ENTITY_GUID"
+    RecordId="[recordIdVariable]"
+    TimeoutInMs="30000" />
+```

package/skills/uipath-rpa/references/activity-docs/UiPath.DataService.Activities/activities/DeleteFileFromRecordField.md

@@ -0,0 +1,56 @@
+# Delete File From Record Field
+
+`UiPath.DataService.Activities.DeleteFileFromRecordField<TEntity>`
+
+**Package:** `UiPath.DataService.Activities`
+
+Deletes a file attachment from a file-type field on an entity record.
+
+**Category:** Data Service.File
+
+## Properties
+
+`x:TypeArguments` — concrete entity type, e.g. `local:EntityName`. Required at activity declaration.
+
+### Input
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `EntityId` | `InArgument<Guid>` | Yes | — | Entity GUID from `EntitiesStore.json` |
+| `RecordId` | `InArgument<Guid>` | Yes | — | GUID of the target record (`[RequiredArgument]`) |
+| `Field` | `InArgument<string>` | Yes | — | Name of the file field (`[RequiredArgument]`, `[Browsable(false)]`) |
+| `ExpansionDepth` | `InArgument<int>` | No | `2` | Depth of relationship expansion on the returned entity (range: 1–3, max `3`) — see [overview § Relationship Fields & ExpansionDepth](../overview.md#relationship-fields--expansiondepth) |
+
+### Output
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `OutputEntity` | `OutArgument<TEntity>` | No | — | Receives the updated entity after file deletion |
+
+### Common
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueOnError` | `InArgument<bool>` | No | `false` | Continue workflow on error |
+| `TimeoutInMs` | `InArgument<int>` | No | `30000` | Timeout in milliseconds |
+
+> **Solution scope properties** (`ScopeValue`, `SolutionEntityKey`, `SolutionEntityName`) are inherited from `BaseEntityActivity` and exist on every activity, but only apply when the project has a SolutionId. For standalone projects, omit them — they're ignored outside solution context. See [overview — Solution Scope Properties](../overview.md#solution-scope-properties-conditional) and [Solution Context](../overview.md#solution-context-folder-vs-tenant-scope).
+
+## XAML Example
+
+```xml
+<uda:DeleteFileFromRecordField
+    x:TypeArguments="local:ENTITY_NAME"
+    InputEntity="{x:Null}"
+    OutputEntity="{x:Null}"
+    ContinueOnError="False"
+    DisplayName="Delete File from ENTITY_NAME"
+    EntityId="ENTITY_GUID"
+    ExpansionDepth="2"
+    Field="FILE_FIELD_NAME"
+    RecordId="[recordIdVariable]"
+    TimeoutInMs="30000" />
+```
+
+- `Field` — bare string, not expression-wrapped. Use the field name exactly as it appears in `EntitiesStore.json`
+- Studio explicitly serializes unused nullable properties as `{x:Null}` — include `InputEntity`, `OutputEntity` (omit `ScopeValue`/`SolutionEntityKey`/`SolutionEntityName` in standalone projects — they're ignored outside solution context)

package/skills/uipath-rpa/references/activity-docs/UiPath.DataService.Activities/activities/DeleteMultipleEntityRecords.md

@@ -0,0 +1,65 @@
+# Delete Multiple Entity Records
+
+`UiPath.DataService.Activities.DeleteMultipleEntityRecords<TEntity>`
+
+**Package:** `UiPath.DataService.Activities`
+
+Deletes multiple records from a Data Fabric entity by their IDs.
+
+**Category:** Data Service.Batch
+
+> **Batch vs single — use this for N record IDs.** For exactly one record, use [DeleteEntityRecord](DeleteEntityRecord.md) — it takes a single `RecordId` directly. Picking batch for one ID adds collection construction for no gain. Full decision guide: [overview — When to Use Batch vs Single-Record Activities](../overview.md#when-to-use-batch-vs-single-record-activities).
+
+## Properties
+
+`x:TypeArguments` — concrete entity type, e.g. `local:EntityName`. Required at activity declaration.
+
+### Input
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `EntityId` | `InArgument<Guid>` | Yes | — | Entity GUID from `EntitiesStore.json` |
+| `InputRecords` | `InArgument<ICollection<Guid>>` | Yes | — | Collection of record GUIDs to delete (`[RequiredArgument]`) |
+
+### Output
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `FailedRecords` | `OutArgument<IList<Guid>>` | No | — | GUIDs of records that failed to delete |
+
+### Configuration
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueBatchOnFailure` | `InArgument<bool>` | No | `true` | If `true`, continues deleting remaining records when one fails |
+
+### Common
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueOnError` | `InArgument<bool>` | No | `false` | Continue workflow on error |
+| `TimeoutInMs` | `InArgument<int>` | No | `30000` | Timeout in milliseconds |
+
+> **Solution scope properties** (`ScopeValue`, `SolutionEntityKey`, `SolutionEntityName`) only apply when the project has a SolutionId. For standalone projects, omit them. See [overview — Solution Scope Properties](../overview.md#solution-scope-properties-conditional) and [Solution Context](../overview.md#solution-context-folder-vs-tenant-scope).
+
+No `ExpansionDepth` or `OutputRecords` — delete returns only failed record IDs, not entity objects.
+
+## XAML Example
+
+```xml
+<uda:DeleteMultipleEntityRecords
+    x:TypeArguments="local:ENTITY_NAME"
+    ContinueOnError="False"
+    DisplayName="Delete Multiple ENTITY_NAME Records"
+    EntityId="ENTITY_GUID"
+    ContinueBatchOnFailure="True"
+    InputRecords="[recordIdCollection]"
+    FailedRecords="[failedRecordIds]"
+    TimeoutInMs="30000" />
+```
+
+## Key Rules
+
+- `InputRecords` is a collection of `Guid` values (record IDs), not entity objects
+- `FailedRecords` is a list of `Guid` values — the IDs of records that failed to delete
+- If any records fail, the activity throws after processing all records

package/skills/uipath-rpa/references/activity-docs/UiPath.DataService.Activities/activities/DownloadFileFromRecordField.md

@@ -0,0 +1,115 @@
+# Download File From Record Field
+
+`UiPath.DataService.Activities.DownloadFileFromRecordField<TEntity>`
+
+**Package:** `UiPath.DataService.Activities`
+
+Downloads a file from a file-type field on an entity record.
+
+**Category:** Data Service.File
+
+## Properties
+
+`x:TypeArguments` — concrete entity type, e.g. `local:EntityName`. Required at activity declaration.
+
+### Input
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `EntityId` | `InArgument<Guid>` | Yes | — | Entity GUID from `EntitiesStore.json` |
+| `RecordId` | `InArgument<Guid>` | Yes | — | GUID of the source record (`[RequiredArgument]`) |
+| `Field` | `InArgument<string>` | Yes | — | Name of the file field (`[RequiredArgument]`, `[Browsable(false)]`) |
+| `FilePath` | `InArgument<string>` | No | — | Local path to save the downloaded file. If omitted (`{x:Null}`), the file is saved to the **current execution directory** with its stored filename. |
+
+### Output
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `DownloadedFileResource` | `OutArgument<ILocalResource>` | No | — | Resource object pointing to the downloaded file |
+
+### Common
+
+| Property | Type | Required | Default | Description |
+|----------|------|----------|---------|-------------|
+| `ContinueOnError` | `InArgument<bool>` | No | `false` | Continue workflow on error |
+| `TimeoutInMs` | `InArgument<int>` | No | `30000` | Timeout in milliseconds |
+
+> **Solution scope properties** (`ScopeValue`, `SolutionEntityKey`, `SolutionEntityName`) are inherited from `BaseEntityActivity` and exist on every activity, but only apply when the project has a SolutionId. For standalone projects, omit them — they're ignored outside solution context. See [overview — Solution Scope Properties](../overview.md#solution-scope-properties-conditional) and [Solution Context](../overview.md#solution-context-folder-vs-tenant-scope).
+
+## XAML Example
+
+```xml
+<uda:DownloadFileFromRecordField
+    x:TypeArguments="local:ENTITY_NAME"
+    FilePath="{x:Null}"
+    ContinueOnError="False"
+    DisplayName="Download File from ENTITY_NAME"
+    DownloadedFileResource="[downloadedFileResource]"
+    EntityId="ENTITY_GUID"
+    Field="FILE_FIELD_NAME"
+    RecordId="[recordIdVariable]"
+    TimeoutInMs="30000" />
+```
+
+- `Field` — bare string, not expression-wrapped. Use the field name exactly as it appears in `EntitiesStore.json`
+- `FilePath` — set to `{x:Null}` when using `DownloadedFileResource` (preferred). If saving to a specific path, use a bare string: `FilePath="C:\downloads\output.pdf"`
+- Studio explicitly serializes unused nullable properties as `{x:Null}` — include them for properties applicable to the activity (omit `ScopeValue`/`SolutionEntityKey`/`SolutionEntityName` in standalone projects — they're ignored outside solution context)
+
+### Variable Declaration
+
+```xml
+<Variable x:TypeArguments="upr:ILocalResource" Name="downloadedFileResource" />
+```
+
+Requires `xmlns:upr="clr-namespace:UiPath.Platform.ResourceHandling;assembly=UiPath.Platform"` on the root `<Activity>` element. See [overview — XAML Namespace Declarations](../overview.md#xaml-namespace-declarations).
+
+## Round-Trip Pattern (Download → Upload)
+
+When copying a file between records, chain `DownloadedFileResource` directly into `UploadFileToRecordField.FileResource`. This preserves the original filename and avoids fabricating temp paths.
+
+```xml
+<!-- Step 1: Download — capture DownloadedFileResource, set FilePath to {x:Null} -->
+<uda:DownloadFileFromRecordField
+    x:TypeArguments="local:ENTITY_NAME"
+    FilePath="{x:Null}"
+    ContinueOnError="False"
+    DisplayName="Download File"
+    DownloadedFileResource="[downloadedFileResource]"
+    EntityId="ENTITY_GUID"
+    Field="FILE_FIELD_NAME"
+    RecordId="[sourceRecordId]"
+    TimeoutInMs="30000" />
+
+<!-- Step 2: Upload — pass downloadedFileResource as FileResource, set FilePath to {x:Null} -->
+<uda:UploadFileToRecordField
+    x:TypeArguments="local:ENTITY_NAME"
+    FilePath="{x:Null}"
+    InputEntity="{x:Null}"
+    OutputEntity="{x:Null}"
+    ContinueOnError="False"
+    DisplayName="Upload File"
+    EntityId="ENTITY_GUID"
+    ExpansionDepth="2"
+    Field="FILE_FIELD_NAME"
+    FileResource="[downloadedFileResource]"
+    RecordId="[targetRecordId]"
+    TimeoutInMs="30000" />
+```
+
+> **Prefer `FileResource` over `FilePath`** when the file originates from another activity. `ILocalResource` (from download, `UiPath.Platform.ResourceHandling`) is assignment-compatible with `IResource` (upload input) — no cast needed. Using `FilePath` with a fabricated temp path loses the original filename. The round-trip preserves it.
+
+## When to Use FilePath vs DownloadedFileResource
+
+| Scenario | Use | FilePath value |
+|----------|-----|----------------|
+| File will be consumed by another activity in the same workflow (e.g., upload to another record) | `DownloadedFileResource` | `{x:Null}` |
+| File needs to be saved to a specific user-provided location | `FilePath` | Bare string path (e.g., `C:\downloads\output.pdf`) |
+| Both — save to disk AND pass to another activity | Both | Set `FilePath` to the desired path; also capture `DownloadedFileResource` |
+
+**Never fabricate a temp file path.** If you do not need a specific save location, omit `FilePath` (set `{x:Null}`) and use `DownloadedFileResource` — the runtime saves the file to the **current execution directory** with its stored filename, and downstream activities consume it via the resource. Fabricated paths (e.g., `"C:\temp\file_" & guid & ".pdf"`) lose the original filename and create cleanup obligations.
+
+## Key Rules
+
+- `DownloadedFileResource` returns a `UiPath.Platform.ResourceHandling.ILocalResource` — use `.LocalPath` to get the file path
+- **For round-trip file copies, omit `FilePath` (set `{x:Null}`) and use `DownloadedFileResource` → `FileResource` chaining** — see pattern above
+- `Field` and `FilePath` accept bare strings for literal values — do not wrap in expression brackets (`[...]`) unless the value comes from a variable