@uipath/skills 1.195.0

package/skills/uipath-rpa/references/legacy/project-structure.md

@@ -0,0 +1,206 @@
+# Legacy Project Structure
+
+Understanding the layout and configuration of a legacy UiPath RPA project.
+
+---
+
+## Directory Layout
+
+```
+{projectRoot}/
+├── project.json              # Project metadata and dependencies
+├── Main.xaml                 # Entry point workflow
+├── *.xaml                    # Additional workflows (flat or in folders)
+├── Workflows/                # (Optional) Sub-folder for organized workflows
+├── Data/                     # (Optional) Input/output data files
+├── .screenshots/             # (Optional) Studio screenshot captures
+├── .settings/                # (Optional) Studio settings profiles
+└── .tmh/                     # (Optional) Test Manager data
+```
+
+**Notable absences compared to modern projects:**
+- No `.local/docs/packages/` — no auto-generated activity documentation
+- No `.codedworkflows/` — no coded automation support
+- No `.objects/` — no Object Repository
+- No `.project/JitCustomTypesSchema.json` — no JIT custom types
+
+---
+
+## Creating a project.json from Scratch
+
+### Minimal Template
+
+Start with this — only `UiPath.System.Activities` is required. Add other packages as needed.
+
+```json
+{
+  "name": "MyProject",
+  "description": "",
+  "main": "Main.xaml",
+  "dependencies": {
+    "UiPath.System.Activities": "[24.10.8]"
+  },
+  "schemaVersion": "4.0",
+  "studioVersion": "25.10.0.0",
+  "projectVersion": "1.0.0",
+  "expressionLanguage": "VisualBasic",
+  "targetFramework": "Legacy",
+  "runtimeOptions": {
+    "autoDispose": false,
+    "isPausable": true,
+    "isAttended": false,
+    "requiresUserInteraction": true,
+    "supportsPersistence": false,
+    "workflowSerialization": "DataContract",
+    "excludedLoggedData": ["Private:*", "*password*"],
+    "executionType": "Workflow"
+  },
+  "designOptions": {
+    "projectProfile": "Developement",
+    "outputType": "Process"
+  },
+  "entryPoints": [
+    {
+      "filePath": "Main.xaml",
+      "uniqueId": "00000000-0000-0000-0000-000000000000",
+      "input": [],
+      "output": []
+    }
+  ]
+}
+```
+
+### Package Selection Guide
+
+**Add packages based on what the workflow needs.** Only `UiPath.System.Activities` is required — everything else is optional.
+
+| Need | Package | Latest Legacy Version |
+|------|---------|----------------------|
+| **Core (always include)** | `UiPath.System.Activities` | **24.10.8** |
+| UI automation (click, type, selectors) | `UiPath.UIAutomation.Activities` | **25.10.28** |
+| Excel (read/write, macros, CSV) | `UiPath.Excel.Activities` | **2.24.4** |
+| Email (SMTP, IMAP, POP3, Outlook) | `UiPath.Mail.Activities` | **1.24.18** |
+| HTTP/REST/SOAP/JSON/XML | `UiPath.WebAPI.Activities` | **1.21.1** |
+| Testing and assertions | `UiPath.Testing.Activities` | **25.10.1** |
+| PDF (read text, OCR, merge, split) | `UiPath.PDF.Activities` | **3.25.2** |
+| Office 365 (Graph API) | `UiPath.MicrosoftOffice365.Activities` | **2.9.13** |
+| Word documents | `UiPath.Word.Activities` | **1.20.3** |
+| PowerPoint presentations | `UiPath.Presentations.Activities` | **1.14.2** |
+| Database (SQL queries) | `UiPath.Database.Activities` | **1.10.1** |
+| Windows Credential Manager | `UiPath.Credentials.Activities` | **2.1.0** |
+| FTP/SFTP file transfer | `UiPath.FTP.Activities` | **2.4.0** |
+| Encryption/hashing (AES, HMAC, PGP) | `UiPath.Cryptography.Activities` | **1.6.1** |
+| Python script execution | `UiPath.Python.Activities` | **1.10.0** |
+| Java method invocation | `UiPath.Java.Activities` | **1.3.1** |
+| Document Understanding/OCR | `UiPath.IntelligentOCR.Activities` | **6.27.3** |
+| Forms (FormIo/HTML) | `UiPath.Form.Activities` | **2.0.8** |
+| Terminal emulation (3270/5250/VT) | `UiPath.Terminal.Activities` | **2.9.0** |
+| Google Suite (Gmail, Drive, Sheets) | `UiPath.GSuite.Activities` | **2.8.28** |
+| NLP (sentiment, translation) | `UiPath.Cognitive.Activities` | **2.2.4** |
+| StudioX scenario templates | `UiPath.ComplexScenarios.Activities` | **1.5.1** |
+| OmniPage OCR engine | `UiPath.OmniPage.Activities` | **1.22.2** |
+| Persistence (long-running workflows) | `UiPath.Persistence.Activities` | **1.8.1** |
+| Mobile automation (iOS/Android) | `UiPath.MobileAutomation.Activities` | **25.10.0** |
+| SAP BAPI function calls | `UiPath.SAP.BAPI.Activities` | **3.0.4** |
+
+**Example:** A workflow that reads Excel, sends email, and calls a REST API needs:
+```json
+"dependencies": {
+  "UiPath.System.Activities": "[24.10.8]",
+  "UiPath.Excel.Activities": "[2.24.4]",
+  "UiPath.Mail.Activities": "[1.24.18]",
+  "UiPath.WebAPI.Activities": "[1.21.1]"
+}
+```
+
+### Packages Can Be Added Later
+
+You don't need all packages upfront. Add them to `dependencies` as you discover what the workflow needs.
+
+**Important:** `find-activities` only searches packages listed in `dependencies`. If you add a package to project.json, re-run `find-activities` to discover its activities.
+
+### Searching for Packages
+
+When the known packages above don't cover a need, search configured NuGet feeds:
+
+```bash
+uip rpa-legacy find-package --query "barcode" --limit 10 --output json
+```
+
+This searches all configured feeds (UiPath official + any custom feeds) by name and description. Add the discovered package to `dependencies`, then `find-activities` will index it.
+
+### Arbitrary .NET Packages
+
+Any NuGet package can be added to `dependencies` for custom .NET classes, methods, and types. Examples:
+- `CsvHelper` — advanced CSV parsing
+- `ClosedXML` — .xlsx manipulation without COM
+- `HtmlAgilityPack` — HTML parsing
+
+Use these via `InvokeCode` with the appropriate namespace imports.
+
+**Avoid adding packages already bundled with Studio** (e.g., `Newtonsoft.Json`) — version conflicts can cause runtime issues.
+
+---
+
+## project.json Key Fields
+
+| Field | Description |
+|-------|-------------|
+| `name` | Project name (used as package ID when packaged) |
+| `main` | Entry point XAML file (relative path) |
+| `dependencies` | NuGet package dependencies with version constraints |
+| `expressionLanguage` | `"VisualBasic"` (most legacy) or `"CSharp"` |
+| `targetFramework` | `"Legacy"` for .NET Framework 4.6.1 projects |
+| `designOptions.outputType` | `"Process"` (standalone) or `"Library"` (reusable) |
+| `studioVersion` | Studio version that created the project |
+
+### Version Constraints
+
+| Syntax | Meaning |
+|--------|---------|
+| `[1.2.3]` | Exact version 1.2.3 |
+| `[1.2.3, )` | Minimum version 1.2.3 |
+| `[1.0, 2.0)` | Range: >= 1.0, < 2.0 |
+
+---
+
+## Library Project Template
+
+To create a **Library** project (reusable workflows published as a NuGet package), set `outputType` to `"Library"`:
+
+```json
+{
+  "name": "Acme.Finance.InvoiceUtilities",
+  "description": "Reusable invoice processing workflows",
+  "dependencies": {
+    "UiPath.System.Activities": "[24.10.8]"
+  },
+  "schemaVersion": "4.0",
+  "studioVersion": "25.10.0.0",
+  "projectVersion": "1.0.0",
+  "expressionLanguage": "VisualBasic",
+  "targetFramework": "Legacy",
+  "runtimeOptions": {
+    "autoDispose": false,
+    "isPausable": true,
+    "isAttended": false,
+    "requiresUserInteraction": false,
+    "supportsPersistence": false,
+    "workflowSerialization": "DataContract",
+    "excludedLoggedData": ["Private:*", "*password*"],
+    "executionType": "Workflow"
+  },
+  "designOptions": {
+    "projectProfile": "Developement",
+    "outputType": "Library"
+  }
+}
+```
+
+**Key differences from Process projects:**
+- **No `main` field** — libraries have no entry point
+- **No `entryPoints` array** — all workflows are callable individually
+- **`outputType: "Library"`** — published as activity package, not deployed as process
+- Workflows marked **Public** become activities when consumed; **Private** workflows are internal helpers
+
+For full library design guidance (naming, versioning, patterns), see [project-organization-guide.md](./project-organization-guide.md).

package/skills/uipath-rpa/references/legacy/selector-guide.md

@@ -0,0 +1,326 @@
+# Selector Guide
+
+Selector anatomy, strategy, and best practices for building reliable UI automation in legacy UiPath workflows.
+
+For UI automation activities (Click, TypeInto, etc.), see [activity-docs/UIAutomation.md](./activity-docs/UIAutomation.md).
+For input method gotchas (SimulateType, EmptyField), see [activity-docs/_COMMON-PITFALLS.md](./activity-docs/_COMMON-PITFALLS.md).
+
+---
+
+## 1. Selector XML Anatomy
+
+A selector is an XML string that identifies a UI element by its position in the application's control hierarchy. Each XML tag represents one level in the hierarchy.
+
+### Tag Types
+
+| Tag | Represents | Found In |
+|---|---|---|
+| `<wnd>` | Window (Win32/WPF/Java) | Desktop applications |
+| `<ctrl>` | Control inside a window | Desktop applications |
+| `<html>` | Browser window/document | Web applications |
+| `<webctrl>` | HTML element | Web applications |
+| `<java>` | Java component | Java applications |
+
+### Common Attributes
+
+| Attribute | Description | Stability |
+|---|---|---|
+| `automationid` | Developer-assigned unique ID (WPF/UWP) | **HIGH** — rarely changes |
+| `id` | HTML element ID | **HIGH** — if developer-assigned (not auto-generated) |
+| `name` | Control name | **MEDIUM** — stable for named controls |
+| `role` | ARIA role or control type (button, edit, combobox) | **MEDIUM** — describes function, not instance |
+| `aaname` | Accessible name (screen reader text) | **MEDIUM** — may change with UI text changes |
+| `cls` | Window class name | **MEDIUM** — stable within app version |
+| `tag` | HTML tag (input, div, span, a) | **LOW** — too generic for identification |
+| `parentid` | Parent element's ID | **MEDIUM** — depends on parent stability |
+| `idx` | Positional index among siblings | **VERY LOW** — breaks when UI order changes |
+| `title` | Window title | **LOW** — often contains dynamic data |
+
+### Selector Example (Web)
+
+```xml
+<html app='chrome.exe' title='Invoice Portal*' />
+<webctrl id='txtInvoiceNumber' tag='INPUT' />
+```
+
+### Selector Example (Desktop)
+
+```xml
+<wnd app='notepad.exe' cls='Notepad' title='Untitled*' />
+<ctrl name='Text Editor' role='edit' />
+```
+
+---
+
+## 2. Attribute Stability Ranking
+
+When multiple attributes are available, prefer the most stable ones:
+
+1. **automationid** — best for WPF/UWP apps; developer-assigned, rarely changes
+2. **id** — best for web apps with stable IDs (not auto-generated like `id='ember-1234'`)
+3. **name** — good for named controls in desktop apps
+4. **role** — good as supporting attribute (not unique alone)
+5. **aaname** — acceptable when other stable attributes unavailable
+6. **cls** — use for window-level identification
+7. **tag** — too generic alone; use only with other attributes
+8. **idx** — **AVOID** — breaks when siblings are added/removed/reordered
+
+### Rules
+
+1. **NEVER rely solely on `idx`** — positional indices break when the UI changes. If `idx` is the only distinguishing attribute, use Anchor Base instead.
+2. **Avoid auto-generated IDs** — IDs like `ember-1234`, `react-abc123`, or `__ID0` change between sessions
+3. **Prefer `automationid` over `name`** — both identify the control, but `automationid` is more stable across UI updates
+4. **Combine 2-3 attributes** for robust identification — e.g., `role='button' aaname='Submit'` is stronger than either alone
+
+---
+
+## 3. Full vs Partial Selectors
+
+### Full Selector
+
+Includes the top-level window tag. Used when the activity is NOT inside a container scope.
+
+```xml
+<wnd app='notepad.exe' cls='Notepad' title='*' />
+<ctrl name='Text Editor' role='edit' />
+```
+
+### Partial Selector
+
+Omits the top-level window tag. Used ONLY inside a container scope (Attach Window, Attach Browser, Open Browser, Open Application).
+
+```xml
+<!-- Inside Attach Browser for chrome.exe -->
+<webctrl id='txtInvoiceNumber' tag='INPUT' />
+```
+
+### When to Use Each
+
+| Context | Selector Type | Why |
+|---|---|---|
+| Activity is standalone (no container) | Full selector | Must identify the window + element |
+| Activity is inside Attach Browser | Partial selector | Container already identifies the browser window |
+| Activity is inside Attach Window | Partial selector | Container already identifies the app window |
+| Activity is inside Open Application | Partial selector | Container already identifies the app window |
+
+### Rule
+
+**ALWAYS use container scopes (Attach Browser/Window) with partial selectors inside** — this is more reliable than full selectors on every activity because:
+1. The window identification is done once (in the container)
+2. If the window title changes, you fix it in one place
+3. Partial selectors are shorter and less fragile
+
+---
+
+## 4. Dynamic Selector Strategies
+
+### Wildcards
+
+Use `*` to match any text in a dynamic attribute portion:
+
+```xml
+<!-- Window title changes with document name -->
+<wnd app='excel.exe' title='* - Excel' />
+
+<!-- Button text includes dynamic count -->
+<webctrl aaname='Show Results (*)' tag='BUTTON' />
+```
+
+### Variables in Selectors
+
+Inject VB.NET variables into selectors using `{{variableName}}` syntax:
+
+```xml
+<!-- Select a specific row by customer name -->
+<webctrl aaname='{{customerName}}' tag='TD' />
+
+<!-- Dynamic window title -->
+<wnd app='sap.exe' title='{{sapTransactionCode}} *' />
+```
+
+In XAML, this looks like:
+```xml
+<ui:Click Selector="&lt;html app='chrome.exe' /&gt;&lt;webctrl aaname='{{customerName}}' tag='TD' /&gt;" />
+```
+
+### Rules
+
+1. **Use wildcards for known-dynamic portions** — window titles with filenames, buttons with counts, timestamps
+2. **Use variables for data-driven selection** — customer names, invoice numbers, row identifiers
+3. **Don't wildcard everything** — `<webctrl aaname='*' tag='*' />` matches every element; keep enough specificity
+
+---
+
+## 5. Anchor Base Pattern
+
+When a target element has no stable selector, use a nearby stable element (the anchor) as reference.
+
+### Structure
+
+```
+Anchor Base
+  ├── Anchor: Find Element (stable label/header near the target)
+  │   └── Selector: <webctrl aaname='Invoice Amount' tag='LABEL' />
+  └── Action: Get Text / TypeInto / Click (target element)
+      └── Selector: <webctrl tag='INPUT' />
+```
+
+### When to Use
+
+1. Target element has only `idx` or auto-generated ID
+2. Multiple identical elements on the page (e.g., multiple "Edit" buttons)
+3. Element position changes relative to page but stays fixed relative to its label
+4. Data-driven forms where the field structure is consistent but selectors are not
+
+### Rules
+
+1. **The anchor must be unique and stable** — labels, headers, static text
+2. **Anchor and target must be visually close** — the Anchor Base finds the nearest matching target relative to the anchor
+3. **Set AnchorPosition** if needed — Top, Bottom, Left, Right, Auto (Auto works for most cases)
+
+---
+
+## 6. Container Scope Strategy
+
+Structure UI automation workflows with container scopes to reduce selector fragility and improve readability.
+
+### Recommended Pattern
+
+```
+Sequence "Process Invoice in Web Portal"
+  ├── Attach Browser (selector: <html app='chrome.exe' title='Invoice Portal*' />)
+  │   ├── TypeInto "Invoice Number" (partial: <webctrl id='txtInvoice' />)
+  │   ├── TypeInto "Amount" (partial: <webctrl id='txtAmount' />)
+  │   ├── Click "Submit" (partial: <webctrl id='btnSubmit' />)
+  │   └── Element Exists "Success" (partial: <webctrl id='lblSuccess' />)
+```
+
+### Rules
+
+1. **One container per application window** — don't nest Attach Browser inside Attach Browser
+2. **Use partial selectors inside containers** — shorter, less fragile, window identification handled by container
+3. **Check App State or Element Exists before acting** — verify the app is ready before clicking
+
+---
+
+## 7. Selector Validation Checklist
+
+When generating XAML with selectors, verify:
+
+1. [ ] No reliance on `idx` attribute alone — use stable attributes or Anchor Base
+2. [ ] Window title uses wildcard for dynamic portions — `title='Invoice*'` not `title='Invoice #12345'`
+3. [ ] No auto-generated IDs — avoid `id='ember-1234'`, `id='__ID0'`
+4. [ ] Container scope used for multiple actions on same window — Attach Browser/Window with partial selectors
+5. [ ] Variables used for data-driven selectors — `{{variableName}}` syntax
+6. [ ] Special characters escaped in XAML — `&lt;` for `<`, `&gt;` for `>`, `&amp;` for `&`, `&quot;` for `"`
+7. [ ] Web selectors start with `<html>` tag (full) or `<webctrl>` tag (partial)
+8. [ ] Desktop selectors start with `<wnd>` tag (full) or `<ctrl>` tag (partial)
+
+---
+
+## 8. Frames and iFrames
+
+Web pages with frames or iFrames have nested document contexts. Selectors must include the frame boundary.
+
+### Identifying Frame Selectors
+
+```xml
+<!-- Main page element -->
+<html app='chrome.exe' title='Portal' />
+<webctrl id='mainContent' tag='DIV' />
+
+<!-- Element INSIDE an iFrame -->
+<html app='chrome.exe' title='Portal' />
+<webctrl tag='IFRAME' id='contentFrame' />        <!-- frame boundary -->
+<webctrl id='txtField' tag='INPUT' />              <!-- element inside frame -->
+```
+
+### Rules
+
+1. **Each iFrame adds a `<webctrl>` tag level** in the selector pointing to the IFRAME element
+2. **Nested iFrames add multiple levels** — each frame boundary is a separate `<webctrl>` tag
+3. **Frame IDs may be dynamic** — use `name` attribute or wildcard if `id` changes
+
+---
+
+## 9. Common Selector Patterns by Platform
+
+### Desktop Application (Win32)
+
+```xml
+<wnd app='notepad.exe' cls='Notepad' title='*' />
+<ctrl name='Text Editor' role='edit' />
+```
+
+### Web — Chrome
+
+```xml
+<html app='chrome.exe' title='My Application*' />
+<webctrl id='submitBtn' tag='BUTTON' />
+```
+
+### Web — Edge
+
+```xml
+<html app='msedge.exe' title='My Application*' />
+<webctrl id='submitBtn' tag='BUTTON' />
+```
+
+### Java Application
+
+```xml
+<wnd app='java.exe' cls='SunAwtFrame' title='*' />
+<ctrl role='push button' name='OK' />
+```
+
+### SAP GUI
+
+```xml
+<wnd app='saplogon.exe' cls='SAP_FRONTEND_SESSION' title='SAP*' />
+<ctrl automationid='usr/txtRSYST-MESSION' />
+```
+
+### Citrix/RDP (Virtual Desktop)
+
+Standard selectors do NOT work inside Citrix/RDP sessions. Use:
+1. **Image-based automation** — Click Image, Find Image
+2. **OCR-based automation** — Get OCR Text, Click OCR Text
+3. **Citrix extension** (if available) — provides native selectors inside the virtual session
+
+---
+
+## 10. Object Repository Concepts
+
+For teams managing many UI automations against the same applications, the Object Repository centralizes selector management.
+
+### Hierarchy
+
+```
+Application (e.g., "InvoicePortal")
+  └── Screen (e.g., "LoginPage", "InvoiceListing")
+      └── UI Element (e.g., "UsernameField", "SubmitButton")
+          └── UI Descriptor (selector + fuzzy selector + image + anchor)
+```
+
+### Naming Convention
+
+`[ApplicationName].[ScreenName].[ElementName]` — e.g., `InvoicePortal.LoginPage.UsernameField`
+
+### UI Libraries
+
+Object Repository descriptors can be published as **UI Libraries** — NuGet packages that other projects consume. When a selector changes, update the UI Library once and all consuming projects get the fix.
+
+### Multiple Targeting Strategies
+
+A UI Descriptor can include multiple targeting methods for resilience:
+1. **Strict selector** — exact match (primary)
+2. **Fuzzy selector** — attribute-flexible match (fallback)
+3. **Image** — visual match (fallback when selectors fail)
+4. **Anchor** — relative to nearby stable element
+
+### When to Use Object Repository
+
+- Team maintains 5+ automations against the same application
+- Application undergoes frequent UI changes
+- Multiple developers work on automations for the same application
+- Organization wants centralized selector management

package/skills/uipath-rpa/references/legacy/test-data-guide.md

@@ -0,0 +1,142 @@
+# Test Data Creation Guide
+
+How to create test data files and UiPath types for legacy workflow testing.
+
+---
+
+## Excel Test Data (COM-Compliant)
+
+### Using ExcelApplicationScope (Interop — .xls/.xlsx)
+
+Create a DataTable in code, then write it via Excel Interop:
+
+```xml
+<!-- Step 1: Build DataTable with InvokeCode -->
+<ui:InvokeCode Code="
+Dim dt As New DataTable()
+dt.Columns.Add(&quot;Name&quot;, GetType(String))
+dt.Columns.Add(&quot;Amount&quot;, GetType(Double))
+dt.Columns.Add(&quot;Date&quot;, GetType(String))
+dt.Columns.Add(&quot;Status&quot;, GetType(String))
+dt.Rows.Add(&quot;Invoice-001&quot;, 1500.50, &quot;2024-01-15&quot;, &quot;Active&quot;)
+dt.Rows.Add(&quot;Invoice-002&quot;, 2300.00, &quot;2024-02-20&quot;, &quot;Pending&quot;)
+dt.Rows.Add(&quot;Invoice-003&quot;, 890.25, &quot;2024-03-10&quot;, &quot;Closed&quot;)
+dt.Rows.Add(&quot;Invoice-004&quot;, 0, &quot;&quot;, &quot;Active&quot;)
+dt.Rows.Add(&quot;Invoice-005&quot;, -100.00, &quot;2024-12-31&quot;, &quot;Error&quot;)
+testData = dt" Language="VBNet">
+  <ui:InvokeCode.Arguments>
+    <scg:Dictionary x:TypeArguments="x:String, Argument">
+      <OutArgument x:TypeArguments="sd:DataTable" x:Key="testData">[dtTestData]</OutArgument>
+    </scg:Dictionary>
+  </ui:InvokeCode.Arguments>
+</ui:InvokeCode>
+
+<!-- Step 2: Write to Excel via ExcelApplicationScope -->
+<!-- Use ExcelApplicationScope + ExcelWriteRange (Interop) for .xls/.xlsx -->
+```
+
+### Test data design principles
+- Include edge cases: empty strings, zero values, negative numbers, special characters
+- Include null/DBNull values to test null handling
+- Mix data types per column to test type coercion
+- Include dates in multiple formats to test parsing
+- Include at least 5-10 rows for meaningful iteration testing
+
+### Using WriteCsvFile (Portable — no Excel needed)
+
+```xml
+<!-- Write CSV then optionally convert to Excel -->
+<ui:WriteCsvFile FilePath="[Path.Combine(Environment.CurrentDirectory, &quot;Data&quot;, &quot;test.csv&quot;)]"
+  DataTable="[dtTestData]" />
+```
+
+---
+
+## Top 10 File Types
+
+| File Type | How to Create | Key Activity | Notes |
+|-----------|--------------|-------------|-------|
+| **Excel (.xls/.xlsx)** | `ExcelApplicationScope` + `ExcelWriteRange` | COM Interop | Use `.xls` for max legacy compat; `.xlsx` for modern |
+| **CSV (.csv)** | `WriteCsvFile` or `Write Text File` | Portable | Set `Delimitator` explicitly; specify `"UTF-8"` encoding |
+| **Text (.txt)** | `Write Text File` activity | System.IO | Use `Encoding="UTF-8"` for portability |
+| **JSON (.json)** | `Serialize JSON` + `Write Text File` | WebAPI package | Build JObject/JArray in InvokeCode, serialize, write |
+| **XML (.xml)** | Build XDocument in InvokeCode + `Write Text File` | System.Xml.Linq | Or use `Serialize XML` if available |
+| **PDF (.pdf)** | Export from Excel/Word scope, or HTML string + wkhtmltopdf | Requires source app | No native PDF creation activity in legacy |
+| **Word (.docx)** | `WordApplicationScope` + `Word Write Text` | COM Interop | Requires Word installed |
+| **HTML (.html)** | `Write Text File` with HTML string content | String building | Build HTML in InvokeCode or Assign |
+| **Email (.eml/.msg)** | `Save Mail Message` from mail activities | Mail package | Create MailMessage object first |
+| **Config (.xlsx)** | REFramework pattern: Config.xlsx with Settings/Constants/Assets sheets | Excel Interop | See `_REFRAMEWORK.md` for sheet structure |
+
+### Creating JSON test data
+
+```vb
+' InvokeCode — build JSON string
+Dim json As String = "{" & vbCrLf &
+  "  ""name"": ""Test User""," & vbCrLf &
+  "  ""amount"": 1500.50," & vbCrLf &
+  "  ""items"": [""A"", ""B"", ""C""]" & vbCrLf &
+  "}"
+output = json
+```
+
+### Creating XML test data
+
+```vb
+' InvokeCode — build XML string
+Dim xml As String = "<?xml version=""1.0"" encoding=""UTF-8""?>" & vbCrLf &
+  "<Invoices>" & vbCrLf &
+  "  <Invoice Id=""001"" Amount=""1500.50"" />" & vbCrLf &
+  "  <Invoice Id=""002"" Amount=""2300.00"" />" & vbCrLf &
+  "</Invoices>"
+output = xml
+```
+
+---
+
+## Top 10 UiPath Types
+
+| Type | How to Create | Common Test Values | VB.NET Expression |
+|------|--------------|-------------------|-------------------|
+| **DataTable** | `Build Data Table` activity or InvokeCode | Headers + 5-10 rows, mixed types, nulls | `New DataTable()` |
+| **String** | `Assign` / literal | `"test"`, `""`, `Nothing`, special chars `<>&"` | `"value"` |
+| **Int32** | `Assign` / `CInt()` | `0`, `-1`, `Integer.MaxValue`, `Integer.MinValue` | `CInt("42")` |
+| **Boolean** | `Assign` | `True`, `False` | `True` |
+| **DateTime** | `Assign` / `DateTime.Parse()` | Today, epoch, future, `DateTime.MinValue` | `DateTime.Now` |
+| **Dictionary(Of String, Object)** | InvokeCode or `Assign` | Config-style key-value pairs, nested objects | `New Dictionary(Of String, Object)` |
+| **String()** (array) | `Assign` / `Split()` | Empty `{}`, single item, many items | `New String() {"a","b","c"}` |
+| **SecureString** | `Get Credential` or InvokeCode | Test password strings | `New NetworkCredential("","pass").SecurePassword` |
+| **MailMessage** | `Get Outlook Mail Messages` or InvokeCode | Email with To/Subject/Body/Attachments | `New System.Net.Mail.MailMessage()` |
+| **QueueItem** | `Get Transaction Item` from Orchestrator | SpecificContent dictionary, Priority, Deadline | Requires Orchestrator queue |
+
+### Creating a test Dictionary (Config-style)
+
+```vb
+' InvokeCode
+Dim config As New Dictionary(Of String, Object)
+config("MaxRetryNumber") = 3
+config("logF_BusinessProcessName") = "TestProcess"
+config("OrchestratorQueueName") = "TestQueue"
+config("ExcelFilePath") = "Data\Input\test.xlsx"
+output = config
+```
+
+### Creating a test DataTable with edge cases
+
+```vb
+' InvokeCode
+Dim dt As New DataTable()
+dt.Columns.Add("Name", GetType(String))
+dt.Columns.Add("Amount", GetType(Double))
+dt.Columns.Add("IsActive", GetType(Boolean))
+
+' Normal rows
+dt.Rows.Add("Alice", 100.50, True)
+dt.Rows.Add("Bob", 0, False)
+
+' Edge cases
+dt.Rows.Add("", -999.99, True)           ' Empty name
+dt.Rows.Add(DBNull.Value, DBNull.Value, DBNull.Value)  ' All nulls
+dt.Rows.Add("Special <>&""chars", 1E+15, True)  ' Special chars, large number
+
+testData = dt
+```