- Getting Started
- How To
- Build Your First App
- Build a Mobile-Friendly App
- General User Experience Guidelines
- Use Master Detail View
- Use Document Viewer
- Use Count With Choice Set Values
- Use Selected Values From a Table
- Embed Apps
- Embed Maps
- Hide Containers Using a Button
- Include MailTo Links
- Include Star Ratings
- Set External Context
- Work With Data Source and Value Bind
- Use the Send Interim Result Activity
- Public Apps
- Notifications
- Designing your App
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Values
- Rule: Start Process
- Rule: Upload File to Storage Bucket
- Rule: Get File From Storage Bucket
- Rule: Reset Values
- Rule: Create/Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Function: And, Or, Not
- Function: Concat
- Function: Contains
- Function: Count
- Function: EndsWith
- Function: If
- Function: IsBlank
- Function: Guid
- Function: Length
- Function: List
- Function: StartsWith
- Function: Sum
- Function: Sort
- Function: Now
- Function: Today
- Function: Time
- Function: Year
- Function: Month
- Function: Day
- Function: Hour
- Function: Minute
- Function: New
- Function: Lookup
- Function: Filter
- Leveraging RPA in your App
- Input and Output Type Properties
- Send Interim Result Activity
- Supported Process Argument Types
- Replacing a Process Referenced in an App
- Referencing a Storage Bucket From Orchestrator
- Configuring an On-Premise Orchestrator for Use by Apps
- Orchestrator Permissions
- Data Flow Between UiPath Apps and Orchestrator
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Application Lifecycle Management (ALM)
- UiPath First-Party Apps
- Basic Troubleshooting Guide
Input and Output Type Properties
You can use In/Out arguments in UiPath Apps. For more general information on Input and Output arguments, see the About Input and Output Arguments page.
An In/Out process type is treated as a single property, no separate input and output versions are created for the same property. For this, a third category of properties called Input/Output is used. This section contains all In/Out type properties.
When a control is bound to a property from this section, the same control works as input and output. This means that while a process is running, the control value goes as input to the process, and once the process is completed, the same control is refreshed with output.
If you have existing apps, or apps imported from an environment which does not have this feature, the following applies:
- Existing In/Out properties, which are present in both Input and Output sections will not be moved to the new section. No bindings are affected and existing apps should continue working as expected. A third Input/Output section is displayed in the process properties panel, which will be empty.
- When refreshing or replacing a process, existing In/Out properties will not be moved to the new section.
- New In/Out properties added to the process, which are not present in the app, are added to the new section after refreshing or replacing the process.
- If you want to treat existing In/Out properties in the new way, you need to delete the In/Out property from both Input and Output sections and refresh the process. The property is now displayed in the third section.
This section describes the behavior when importing an app from the cloud environment to an on-premises environment, which does not support the In/Out property.
When importing an app from the cloud environment to an on-premises environment, which does not support the In/Out property, the following applies:
- The entire Input/Output section disappears.
- Bindings referring to properties from the Input/Output section are displayed as invalid.
- After replacing the process, the In/Out properties are added to both sections. You can now update the invalid bindings to point to the new properties.
