studio-web
latest
false
Studio Web user guide
- Getting started
- For administrators
- RPA workflow projects
- Creating an RPA workflow from an idea
- Creating a project
- How to start an RPA workflow
- Managing project files and folders
- Connecting RPA workflows to your accounts
- Configuring activities
- Managing the activities in a project
- Passing values between activities
- Iterating through items
- Managing the data in a project
- Configuring a project to use your data
- Using file and folder resources
- Local setup for RPA workflow and app projects
- App projects
- Agentic processes
- Maestro Case
- Maestro Flow
- Agents
- Solutions
- API workflows
- Tests
Known limitations for app projects in Studio Web, covering restrictions on Autopilot generation, Studio Desktop compatibility, and page export support.
App projects in Studio Web present certain limitations.
When designing an app:
- Apps cannot be generated using Autopilot from a Data Service entity.
- Apps cannot be opened in Studio Desktop.
- Apps do not support page export and import.
- Apps do not use the Query Builder. Instead, you must add a Query Entity Record automation to your workflow.
- Apps do not support entity choice sets and the
GetChoiceSetandGetChoiceSetValuefunctions.Do not support theFetchandFetchOnefunctions. Instead, you must add a Query Entity Record automation to your workflow.
When deploying an app project:
- Apps cannot be published to a personal workspace or to folder feeds. Instead, you publish at the tenant level.
- Apps cannot be imported and exported as packages in Orchestrator. You can instead import and export them as Solutions.
- Apps cannot currently be deployed as Public Apps. This is a temporary limitation which will be removed in an upcoming release.