marketplace
latest
false
- Release Notes
- Overview
- Getting Started
- Marketplace Vendors
- Marketplace Customers
- Publishing Guidelines
- Publishing Guidelines for Ready-to-go Automations
- Publishing Guidelines for Solution Accelerators
- Publishing Guidelines for Integration Service Connectors
- Security & IP Protection
- Other UiPath Listings
- Node-RED
- Setup
- Teams
- Microsoft Teams Scope
- Create Team
- Create Team From Group
- Get Team
- Get Teams
- Channels
- Create Channel
- Delete Channel
- Get Channel
- Get Channels
- Update Channel
- Chats
- Get Chat
- Get Chats
- Get Chat Members
- Messages
- Get Message
- Get Messages
- Get Message Replies
- Reply To Message
- Send Message
- Events
- Create Event
- Delete Event
- Get Event
- Get Events
- Users
- Get User Presence
- How It Works
- Technical References
- Get Started
- About
- Setup
- Technical References
- Azure Form Recognizer Scope
- Activities
- Analyze Form
- Analyze Form Async
- Get Analyze Form Result
- Analyze Receipt
- Analyze Receipt Async
- Get Analyze Receipt Result
- Analyze Layout
- Analyze Layout Async
- Get Analyze Layout Result
- Train Model
- Get Models
- Get Model Keys
- Get Model Info
- Delete Model
- Connectors
- How to Create Activities
- Build Your Integration
Marketplace User Guide
Last updated Sep 5, 2024
Direction
There are four directions in which a property can point:
- In: The most common. Used for input arguments.
- Out: Used for output arguments, the results of an activity.
- InOut: Rarely used, but can be handy in activities that take in data, modify it, and output it for use in other activities.
-
None: Discrete types like Booleans and Enums do not require a direction. Use None when creating properties of these types.
Note: Note that Out and InOut properties can only accept variables, not literal values, in UiPath Studio. This makes sense since the activity needs something to which the outputted value can be written.
Activity Creator
Generated Code
The Argument direction is seen in the declaration of each property. Notice that `FirstNumber` and `SecondNumber` are both `InArguments` while `Sum` is an `OutArgument`.
... #region Properties
[LocalizedDisplayName(nameof(Resources.Addition_FirstNumber_DisplayName))]
[LocalizedDescription(nameof(Resources.Addition_FirstNumber_Description))]
[LocalizedCategory(nameof(Resources.Input_Category))] public InArgument<int>
FirstNumber { get; set; }
[LocalizedDisplayName(nameof(Resources.Addition_SecondNumber_DisplayName))]
[LocalizedDescription(nameof(Resources.Addition_SecondNumber_Description))]
[LocalizedCategory(nameof(Resources.Input_Category))] public InArgument<int>
SecondNumber { get; set; }
[LocalizedDisplayName(nameof(Resources.Addition_Sum_DisplayName))]
[LocalizedDescription(nameof(Resources.Addition_Sum_Description))]
[LocalizedCategory(nameof(Resources.Output_Category))] public OutArgument<int> Sum
{ get; set; } #endregion ...
... #region Properties
[LocalizedDisplayName(nameof(Resources.Addition_FirstNumber_DisplayName))]
[LocalizedDescription(nameof(Resources.Addition_FirstNumber_Description))]
[LocalizedCategory(nameof(Resources.Input_Category))] public InArgument<int>
FirstNumber { get; set; }
[LocalizedDisplayName(nameof(Resources.Addition_SecondNumber_DisplayName))]
[LocalizedDescription(nameof(Resources.Addition_SecondNumber_Description))]
[LocalizedCategory(nameof(Resources.Input_Category))] public InArgument<int>
SecondNumber { get; set; }
[LocalizedDisplayName(nameof(Resources.Addition_Sum_DisplayName))]
[LocalizedDescription(nameof(Resources.Addition_Sum_Description))]
[LocalizedCategory(nameof(Resources.Output_Category))] public OutArgument<int> Sum
{ get; set; } #endregion ...
Effect in UiPath Studio
Hover over each property in the Properties Pane to see its direction.