Skip to content

Commit ca7a3b4

Browse files
A library hands no application handle across a call: each activity attaches where it acts, and an attach before acting is no step
1 parent c744d82 commit ca7a3b4

5 files changed

Lines changed: 5 additions & 4 deletions

File tree

‎skills/uipath-genome/references/composite-interactions-guide.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ Every derived element is named `derived from <anchor control> — <pattern>` in
3232
- **Open a browser at a URL:** the application card opens it, at the URL on its Object Repository screen. Not Start Process: the card starts the browser with flags that keep a minimised or covered window taking input and that suppress the first-run, search-engine and profile-picker prompts and the debugger banner.
3333
- **Start a desktop application:** the application card opens it, with the file path, arguments and working directory on its screen. A path the source does not record stays empty, a row of the live checks; until it is set, the card only attaches.
3434
- **Attach, or open when not open:** one card whose Open option opens the application only when no instance is open. An attach the source tries before a launch, a launch after a failed attach, and a test that chooses between them (whether the process runs, its window is open, the session is attached) are that card's work: no attempt in a Try/Catch, no test and no flag recording which way it went.
35+
- **Attach before acting:** no step; the card of each activity that acts attaches where it acts. Only an attach whose result the process uses otherwise — reported, or deciding work other than a launch — is a check: Check App State on an element of the window.
3536
- **Close the application where its work ends:** the Close option of the card around that work, at the point the source closes it.
3637
- **Force-close a process:** Kill Process.
3738
- **Bring a window to the front:** the Activate option of the activity that next acts in it, as for keystrokes; never a step of its own.

‎skills/uipath-genome/references/genome-reading-guide.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Inputs, outputs and side effects: the contract the Handoffs table relies on. Eac
4949

5050
**Library components** carry one table per public workflow, `Argument | Direction | Type | Description`: the type the rebuild gives the argument, its default and value format, and the conventions consumers rely on. Consumers are written against this table before the library packs. A workflow over the analyzer's argument cap (20) takes its optional switches and values in one options object — one In argument with its own table (`Field | Type | Default | Description`).
5151

52-
**State kept between calls lives in the consumer.** A library workflow starts each call from its declared defaults and a library project holds no global variables or constants, so state one action stores and another reads (a value, an attached application, its own instance of another component) crosses each call as an argument: Out from the workflow that produces it, In to each that reads it, In/Out where one changes it. A coded library's static field holds none of it. An attached application crosses as the application handle the owning skill's public-workflow contract has workflows return and accept. An instance per caller is held by each caller; one instance per run is held by the run's entry workflow and passed to every caller.
52+
**State kept between calls lives in the consumer.** A library workflow starts each call from its declared defaults and a library project holds no global variables or constants, so state one action stores and another reads (a value, its own instance of another component) crosses each call as an argument: Out from the workflow that produces it, In to each that reads it, In/Out where one changes it. A coded library's static field holds none of it. An attached application crosses no call: a library hands no application handle out, and each activity gets the application through its own Use Application/Browser card where it uses it. An instance per caller is held by each caller; one instance per run is held by the run's entry workflow and passed to every caller.
5353

5454
**Test components** list each test case's row schema (the fields that vary per scenario) apart from the test project's configuration constants, with credentials as asset names per row. Where each case's data set is built: [test-execution-guide.md § Test data](test-execution-guide.md); a case with no data set takes its values from configuration constants.
5555

‎skills/uipath-planner/references/shared/genome-format-guide.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Inputs, outputs, side effects. Mandatory content for a component inside a proces
7272

7373
**Library components** (a project other components consume as a package) carry, instead of the three bullets, one table per public workflow — never one table shared by several, which hides each workflow's types and directions: `Argument | Direction | Type | Description`. The Type is the one the rebuild gives the argument — a flag is a Boolean and a count a number, whatever text the source carried them in — and the description states the default and the value format (what a flag means, how a date is rendered, which side quotes a value), plus the conventions consumers rely on (naming, defaults, what a failed final check does). This table is the contract consumers are authored against before the library packs; every detail it omits becomes a question between two build groups. A workflow over the analyzer's argument cap (20) carries its optional switches and values in one options object — one In argument with its own table (`Field | Type | Default | Description`).
7474

75-
**State kept between calls.** A library workflow starts each call from its declared defaults, and a library project holds no global variables or constants, so state the source keeps from one call of its actions to the next — a value one action stores and another reads, an attached application or handle, its own instance of another component it calls — lives in the consumer and crosses each call as an argument: Out from the workflow that produces it, In to each that reads it, In/Out where one changes it. A coded library's static field does outlive a call, but as one value for every caller in the job and none inside an isolated invoke, and no Interface shows it, so it holds none of this state. An attached application crosses as the application handle the owning skill's public-workflow contract has workflows return and accept. The conventions name the holder and the work the source ran on its own — set-up before the first call, a close-down when the run ends, after a failure too — each a public workflow the holder calls at that point. The holder follows the source's instances, as the source guide's § Call Graph Rules state them: an instance per caller is held by each caller — a process in its entry workflow for its whole run, passed to the workflows that call the library, and a calling library in its own Interface, since it holds nothing either; one instance per run is held by the run's entry workflow and passed to every caller, calling libraries included. A stored value no action changes is no state: it is a fact or a Configuration Question (§ Configuration Questions).
75+
**State kept between calls.** A library workflow starts each call from its declared defaults, and a library project holds no global variables or constants, so state the source keeps from one call of its actions to the next — a value one action stores and another reads, its own instance of another component it calls — lives in the consumer and crosses each call as an argument: Out from the workflow that produces it, In to each that reads it, In/Out where one changes it. A coded library's static field does outlive a call, but as one value for every caller in the job and none inside an isolated invoke, and no Interface shows it, so it holds none of this state. An attached application is no state that crosses a call: a library hands no application handle out for a caller to pass to another call, and each activity gets the application through its own Use Application/Browser card where it uses it. The conventions name the holder and the work the source ran on its own — set-up before the first call, a close-down when the run ends, after a failure too — each a public workflow the holder calls at that point. The holder follows the source's instances, as the source guide's § Call Graph Rules state them: an instance per caller is held by each caller — a process in its entry workflow for its whole run, passed to the workflows that call the library, and a calling library in its own Interface, since it holds nothing either; one instance per run is held by the run's entry workflow and passed to every caller, calling libraries included. A stored value no action changes is no state: it is a fact or a Configuration Question (§ Configuration Questions).
7676

7777
**A value passed down only to reach its reader is the reader's own read.** A value that is the same wherever and whenever the run reads it — the machine name, the user name, the robot's name — and that the source reads once and passes through calls only to reach the step that uses it is read by that step, and is no argument of the workflows it passes through. A value the caller computes or changes, or one that must hold the value of one moment for the whole run (the run's start time), stays an argument.
7878

‎skills/uipath-rpa/SKILL.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ Common Rules are 1–12. Coded rules 13–19 are in [coded/codedworkflow-referen
108108
<!--skill-flavor:rules-validation-gate:end-->
109109
4a. Use file tools: `Write` each `.xaml`/`.cs` completely and `Edit` later; never generate workflow files with scripts/templates: validation and fixes stay per file, and Object Repository links survive `Edit` but not regeneration. For similar files, parallel `Write`s, a helper workflow, or copy a validated file and `Edit` differences.
110110
4b. Write only invokable units: extract reused or independently readable groups; keep one activity or short assignments inline. Do not wrap one activity merely to pass arguments. A scope the activity needs (an Application Card, an attach) is no reason to extract it: open the scope at the step, around the steps that act on that window in a row.
111-
4c. **Prefix each XAML workflow argument with its direction** — `in_InvoiceId`, `out_Result`, `io_Browser` — entry points included; the analyzer's argument-naming rule (ST-NMG-002) warns on any other name. Three kinds take no prefix: a library's public workflow arguments, which become the activity's properties ([library-authoring-guide.md § The Public-Workflow Contract](references/library-authoring-guide.md)); coded workflow arguments, whose direction the signature carries ([coded/operations-guide.md § Add a Workflow File to Existing Project](references/coded/operations-guide.md#add-a-workflow-file-to-existing-project), step 3); and names fixed elsewhere — the Global Exception Handler's `errorInfo` and `result`, which the runtime requires as written ([error-handling-guide.md § Global Exception Handler](references/error-handling-guide.md#8-global-exception-handler-geh)), and test-data arguments, bound to their data by name ([testing-guide.md § Data-Driven Testing](references/testing-guide.md#data-driven-testing)). A DataTable argument also carries `dt_` after its direction prefix (`in_dt_Rows`, `out_dt_Result`), and a DataTable variable starts with it (`dt_Rows`); the analyzer warns on a missing `dt_` (ST-NMG-011 for arguments, ST-NMG-009 for variables). After the prefixes a name is letters with digits only at its end — `in_dt_InvoiceRows`, not `in_dt_Invoice_Rows`: the naming rules reject any further `_`.
111+
4c. **Prefix each XAML workflow argument with its direction** — `in_InvoiceId`, `out_Result`, `io_Counter` — entry points included; the analyzer's argument-naming rule (ST-NMG-002) warns on any other name. Three kinds take no prefix: a library's public workflow arguments, which become the activity's properties ([library-authoring-guide.md § The Public-Workflow Contract](references/library-authoring-guide.md)); coded workflow arguments, whose direction the signature carries ([coded/operations-guide.md § Add a Workflow File to Existing Project](references/coded/operations-guide.md#add-a-workflow-file-to-existing-project), step 3); and names fixed elsewhere — the Global Exception Handler's `errorInfo` and `result`, which the runtime requires as written ([error-handling-guide.md § Global Exception Handler](references/error-handling-guide.md#8-global-exception-handler-geh)), and test-data arguments, bound to their data by name ([testing-guide.md § Data-Driven Testing](references/testing-guide.md#data-driven-testing)). A DataTable argument also carries `dt_` after its direction prefix (`in_dt_Rows`, `out_dt_Result`), and a DataTable variable starts with it (`dt_Rows`); the analyzer warns on a missing `dt_` (ST-NMG-011 for arguments, ST-NMG-009 for variables). After the prefixes a name is letters with digits only at its end — `in_dt_InvoiceRows`, not `in_dt_Invoice_Rows`: the naming rules reject any further `_`.
112112
5. Prefer UiPath built-in activities for Orchestrator integration, UIA, and documents; use plain .NET/third-party packages for pure transforms, HTTP, and parsing, but reach a third-party system through an Integration Service connector, or build one with `uip is connectors builder`; a direct API call needs a stated reason.
113113
5a. **A secret stays in its asset until the scope that uses it.** Read a Credential or Secret asset (Get Credential, Get Secret, or their coded equivalents) inside the scope that types or sends the secret — the application card of the sign-in, the request that carries it — and pass only the asset's name between workflows and through the configuration. A password passed as an argument, `SecureString` or `String`, or kept in a dictionary reaches every workflow it crosses; the analyzer refuses only the `SecureString` workflow argument (`ST-SEC-007`, [cli-reference.md § Analyzer errors](references/cli-reference.md#analyzer-errors)). Where a connection holds the secret (an Integration Service connection), use the connection.
114114
6. **ALWAYS ensure required package dependencies are in `project.json`** before using their activities or services.

‎skills/uipath-rpa/references/library-authoring-guide.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ Each public workflow is an API surface. Apply every rule:
135135
2. **Public arguments: PascalCase, NO `in_`/`out_`/`io_` prefixes** — `InvoiceId`, `RecipientEmail`, `NotificationResult`. Argument names become activity property names; prefixes become noise on the property grid. Private workflows follow SKILL.md Common Rule 4c.
136136
3. **Describe every public argument** via its `sap2010:Annotation.AnnotationText` — descriptions ship as property tooltips. For display names, placeholders, widgets, and grouping, add the layout sidecar ([§ Activity Layout](#activity-layout--the-sidecar-file)).
137137
4. **Expect — and keep — the analyzer naming warnings.** `build`/`pack` emit `Argument <Name> does not respect the set pattern ^in_...` for prefix-free library arguments, and a public DataTable argument also draws `doesn't have datatable prefix` (ST-NMG-011). The warnings are non-blocking. Do NOT rename arguments to silence them, `dt_` included.
138-
5. **Return application handles.** A workflow that opens or attaches to an app outputs the window/browser object; downstream public workflows accept it as an input argument instead of reopening.
138+
5. **No application handle crosses the library boundary.** A public workflow neither returns the window/browser it opens or attaches to nor accepts one from its caller; each activity gets the application through its own Use Application/Browser card where it uses it.
139139
6. **Post-authoring audit:** before packing, re-check every public workflow against rules 1-3 — name form, argument naming, argument descriptions.
140140

141141
## Error Contract

0 commit comments

Comments
 (0)