- Introdução
- Para administradores
- Projetos de fluxo de trabalho de RPA
- Como criar um fluxo de trabalho de RPA a partir de uma ideia
- Criação de um projeto
- Como iniciar um fluxo de trabalho de RPA
- Gerenciamento de arquivos e pastas do projeto
- Conectar fluxos de trabalho de RPA às suas contas
- Configuração de atividades
- Gerenciamento de atividades em um projeto
- Como transmitir valores entre atividades
- Como iterar por itens
- Como gerenciar os dados em um projeto
- Configuração de um projeto para usar seus dados
- Como usar recursos de arquivos e pastas
- Configuração local para fluxo de trabalho de RPA e projetos de aplicativos
- Projeto do aplicativo
- Apps no Studio Web
- Definir um contexto externo usando parâmetros de consulta
- Definir um contexto externo usando eventos externos
- Use matrizes para preencher os controles Lista suspensa, Lista suspensa multiseleção e Botão de rádio
- Usar controles tabulares com entidades do Data Service em projetos de aplicativos
- Incorporar agentes de conversa
- Atividades do aplicativo
- Processos com agentes
- Caso do Maestro
- Fluxo do Maestro
- Agents
- Soluções
- Fluxos de trabalho da API
- Testes
Coded apps in Studio Web: a solution-native pro-code project that you initialize in the browser, build locally in your IDE, and push into Studio Web with the UiPath CLI to publish alongside the rest of the solution.
Studio Web lets you author UiPath® Coded Apps inside a solution, alongside RPA workflows, agents, API workflows, and other project types. Studio Web owns the project's identity, versioning, and publish lifecycle. The app's source code is written in your own local project and pushed into Studio Web with the UiPath CLI.
Authoring a coded app through Studio Web gives you:
- A solution-native project that you initialize once and then push code into from your own local build;
- A
uip codedapp pushcommand that uploads your locally built app — including abindings_v2.jsonfile, if you provide one — into the Studio Web project; - A
uip codedapp pullcommand to sync the latest pushed source back into a local folder (useful when a teammate has pushed changes or you need to reset your working copy); - Bindings to Orchestrator resources — assets, storage buckets, queues, connections, and processes — declared in
bindings_v2.jsonand registered by Studio Web on push; - Solution-native publish and deploy, so the coded app ships together with the other projects it depends on.
At initialization time, Studio Web creates the project scaffolded with a single file, webAppManifest.json, that describes the project's type and configuration. No source code, no framework template, and no dependencies are added — you bring those from your own local project.
Studio Web does not ship a pre-wired coded-app template, an in-browser code editor, or a live preview. After you push code with uip codedapp push, Studio Web displays it in read-only mode under the project's Source view. All source-code editing happens in your local IDE.
Availability of coded app projects also depends on the delivery model you are on.
Coded app projects in Studio Web are available on Automation Cloud only. They are not supported in Studio Web on Automation Suite.
To initialize a coded app project, see Initializing a coded app project. For the full walkthrough of working with coded app projects, see About coded app projects.