apps
latest
false
Apps user guide
- Getting Started
- Demo apps
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Designing your app with Autopilot
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Log Message
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Rule: Submit Action
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Leveraging Connections in your apps
- Apps in Studio Web
- App projects in Studio Web
- Differences in app development in Studio Web
- Application Lifecycle Management (ALM)
- UiPath First-Party Apps
- Basic Troubleshooting Guide
important :
For documentation on app projects in Studio Web, refer to the App Projects chapter in the Studio Web documentation: https://docs.uipath.com/studio-web/automation-cloud/latest/user-guide/apps-in-studio-web.
Differences in app development in Studio Web
Key differences between building apps in Studio Web and the standard Apps interface, including control access, rule support, and known limitations.
- In Studio Web, you add controls to an app by selecting the Toolbox icon below the Project Explorer icon, in the left-hand pane of the window, as opposed to selecting Add control in the standard Apps interface.
- Apps in Studio Web do not support rules. Use Studio automations triggered by events instead.
- Apps can only execute unattended automations using serverless robots.
- Apps do not currently support import and export of individual pages.
Important:
By default, the code-behind process runs in a serverless environment with a maximum lifetime of 15 minutes, and the system attempts to transfer state to a new process around the 12-minute mark. Long-running workflows that exceed this duration may be terminated unexpectedly. For critical data flows, use the Run Job activity to help prevent abrupt termination and data loss.
For more information on current limitations, refer to the Known limitations section of the Studio Web documentation.