-
Notifications
You must be signed in to change notification settings - Fork 1
Draft Terminology
Christian Prior-Mamulyan edited this page Jul 6, 2025
·
1 revision
Terminology of argument passing – with UiPath mapping
- Describes how data is received or returned by a function/module.
-
UiPath: Arguments in
.xamlworkflows (In_,Out_,InOut_arguments).
-
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).
- Converts data into transferable formats (e.g. JSON
↔️ object). -
UiPath:
Deserialize JSON,Serialize JSON,JObject,JToken,Dictionary,.ToString,.ToObject.
- Defines structure and readability of input/output interfaces.
-
UiPath: Number and naming of workflow arguments; using
Config,TransactionItem, or structured payloads.
- 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.
-
Indicates dependency level between caller and callee structures.
-
UiPath:
- Tight: multiple explicit arguments or shared config file
-
Loose: passing
JObject, JSON string, or dictionary
-
Use of structured objects to bundle related data and hide internals.
-
UiPath:
- Custom
.vbclass or serialized JSON - Input/output
Dictionary(Of String, Object)representing DTO
- Custom
Note
Help to improve this documentation. Submit feedback.
Copyright © 2025 Christian Prior-Mamulyan · License CC BY-SA 4.0