Skip to content

Draft Terminology

Christian Prior-Mamulyan edited this page Jul 6, 2025 · 1 revision

Terminology of argument passing – with UiPath mapping

1. Parameter Interface

  • Describes how data is received or returned by a function/module.
  • UiPath: Arguments in .xaml workflows (In_, Out_, InOut_ arguments).

2. Parameter Passing Modes

  • Specifies how arguments behave:

    • By value: copies passed
    • By reference: shared memory
    • Out: return-only
    • In: read-only
  • UiPath: Explicit direction of arguments (In, Out, In/Out).

3. Data Marshalling

  • Converts data into transferable formats (e.g. JSON ↔️ object).
  • UiPath: Deserialize JSON, Serialize JSON, JObject, JToken, Dictionary, .ToString, .ToObject.

4. Signature Design

  • Defines structure and readability of input/output interfaces.
  • UiPath: Number and naming of workflow arguments; using Config, TransactionItem, or structured payloads.

5. Data Contract

  • Formal specification of expected data shape (types, fields, constraints).
  • UiPath: Not enforced by default; emulated via strongly typed arguments, custom classes, or JSON Schema validation.

6. Coupling

  • Indicates dependency level between caller and callee structures.

  • UiPath:

    • Tight: multiple explicit arguments or shared config file
    • Loose: passing JObject, JSON string, or dictionary

7. Encapsulation / DTO

  • Use of structured objects to bundle related data and hide internals.

  • UiPath:

    • Custom .vb class or serialized JSON
    • Input/output Dictionary(Of String, Object) representing DTO

Clone this wiki locally