UiPath Documentation
studio
latest
false
Importante :
A localização de um conteúdo recém-publicado pode levar de 1 a 2 semanas para ficar disponível.
UiPath logo, featuring letters U and I in white

Guia do usuário do Studio

Última atualização 15 de abr de 2026

Diferenças entre Experiência Moderna e Experiência Clássica

Gravadores

Atividades

Por padrão, um conjunto de atividades separado é disponibilizado com cada experiência.

Independentemente da experiência selecionada para um projeto, também é possível habilitar as atividades que, por padrão, somente são disponibilizadas com a outra experiência. Clique em Visualizar Opções, no alto do painel Atividades e, em seguida, selecione:

  • Mostrar Moderna para visualizar as atividades modernas em um projeto que utiliza a experiência clássica

  • Mostrar Clássica para visualizar as atividades clássicas em um projeto que utiliza a experiência moderna.

    docs image

A tabela a seguir lista as atividades disponíveis por padrão em uma experiência, mas não na outra. Por padrão, as atividades de Automação de Interface Gráfica que não estão listadas na tabela são disponibilizadas em ambas as experiências.

Atividades ModernasAtividades Clássicas
AtivarClicar, Atalhos de teclado, Type into
Check App StateOn Element Appear, On Element Vanish, On Image Appear, On Image Vanish, Wait Element Vanish, Wair Image Vanish, Find Image, Image Exists, Element Exists
Check/UncheckMarcar
ClickClick, Click Image
Extract Table DataExtrair Dados Estruturados, Obter Texto Completo, Tornar Texto Visível
Get TextGet Text
Go To URLNavegar Para
HighlightHighlight
HoverFocalizar, Focalizar Imagem
Keyboard ShortcutsEnviar Tecla de Acesso
Navigate BrowserFechar a Guia, Voltar, Avançar, Voltar para o Início, Atualizar Navegador
Select ItemSelect Item
Take ScreenshotTake Screenshot
Type IntoDigitar em, Digitar Texto Seguro
Use Application/BrowserAbrir Aplicativo, Abrir Navegador, Anexar Janela, Anexar Navegador, Escopo do Elemento, Fechar Janela, Iniciar Processo
N/AAncorar Base, Âncora Sensível a Contexto

Exceções

The table below presents for each classic exception, its modern counterpart with relationship type: direct rename (same concept and scope in modern), partial mapping (narrower/broader scope in modern), or no counterpart (feature removed, not yet ported, or exception not needed in modern).

ClássicoModern (UiPath.UIAutomationNext.Exceptions)MapeamentoObservações
General Activity (UiPath.Core.Activities)
ElementNotSetExceptionNotInitializedExceptionParcialClassic: element not provided in context. Modern: InUIElement property not initialized before use. Concept is the same; modern is scoped to the InUIElement input specifically.
TextNotFoundExceptionNodeNotFoundExceptionParcialClassic: dedicated exception for text-find activities. Modern: all "not found" cases (including text targets) collapse into NodeNotFoundException.
RegistrationException(none)No counterpartNot thrown in production in classic either; no equivalent concept in modern.
ActivityTimeoutExceptionRuntimeTimeoutExceptionDirect renameSame concept; renamed and moved to UiPath.UIAutomationNext.Exceptions namespace.
PropertyNotSetException(none)No counterpartDesign-time ValidationError only in classic. Modern activities use a different validation mechanism.
BrowserNotSetExceptionBrowserNotFoundExceptionDirect renameClassic: no browser in context. Modern: no matching browser found. Same concept; modern name is more descriptive.
WindowNotSetExceptionApplicationNotFoundExceptionParcialClassic: no window in context for a window-scoped activity. Modern: application not found when attaching. Closest equivalent; modern is broader (covers all app types, not just windows).
SAP (UiPath.Core.Activities)
SAPCallTransactionExceptionSAPCallTransactionExceptionDirect renameSame name, same concept; namespace moved from UiPath.Core.Activities to UiPath.UIAutomationNext.Exceptions.
SAPLoginExceptionSAPLoginExceptionDirect renameSame name, same concept; namespace moved from UiPath.Core.Activities to UiPath.UIAutomationNext.Exceptions.
CellScopeExceptionSAPTableCellScopeExceptionDirect renameSame concept (table cell scope failures); renamed to be SAP-specific and clarify it is for tables.
ExpandALVTreeExceptionSAPExpandTreeExceptionDirect renameSame concept (SAP tree expansion failure); simplified name.
Selector (UiPath.Core)
InvalidSelectorExceptionInvalidSelectorExceptionDirect renameSame name, same concept (unparseable selector); namespace moved from UiPath.Core to UiPath.UIAutomationNext.Exceptions.
InvalidFilterSelectorException (interno)(none)No counterpartInternal class; no equivalent in modern.
SelectorOperationExceptionUiAutomationExceptionParcialClassic: wraps COM/parse failures during selector operations. Modern: these are surfaced as the general UiAutomationException; no dedicated selector-operation exception type.
Element / Node (UiPath.Core)
SelectorNotFoundExceptionNodeNotFoundExceptionDirect renameSame concept (element not found by selector); modern name generalises beyond selectors. SelectorNotFoundException extends FindElementException in classic; modern uses a flat hierarchy under UiAutomationException.
FindElementExceptionRuntimeFindExceptionParcialClassic: COM error during find that is not "not found". Modern: find failed with details about which search step failed. Closest equivalent; modern includes richer diagnostic info.
InvalidUiElementExceptionNodeNotFoundExceptionParcialClassic: COM error E_UINODE_INVALID_ELEMENT (stale/invalid reference). Modern: COM error E_UINODE_INVALID_IDENTIFIER is mapped to NodeNotFoundException. Concept is the same (stale element); different exception type in modern.
UninitializedNodeExceptionUiNodeUninitializedElementExceptionDirect renameSame concept (uninitialized node, COM error E_UINODE_UNINITIALIZED_ELEMENT); renamed with UiNode prefix for consistency.
UiElementHasNoItemsExceptionUiNodeHasNoItemsExceptionDirect renameSame concept (empty list/tree/combo, COM error E_UINODE_HAS_NO_ITEMS); renamed from UiElement to UiNode prefix.
ElementOperationExceptionUiAutomationExceptionParcialClassic: broad catch-all wrapping any COM failure on element operations (click, type, highlight, etc.). Modern: the same role is played by the base UiAutomationException; no dedicated element-operation exception type.
Browser (UiPath.Core)
InvalidBrowserExceptionBrowserNotFoundExceptionParcialClassic: uiBrowser COM reference is null. Modern: no matching browser instance found. Same user-visible scenario (browser unavailable); modern name reflects the attach-by-find model.
BrowserOperationExceptionUiAutomationExceptionParcialClassic: dedicated exception for browser COM operation failures. Modern: browser operation failures surface as UiAutomationException; no dedicated browser-operation type.
Window (UiPath.Core)
InvalidWindowExceptionApplicationNotFoundExceptionParcialClassic: window COM reference is null before an operation. Modern: application not found when attaching. Closest equivalent; modern is broader (all app types).
WindowOperationExceptionUiAutomationExceptionParcialClassic: dedicated exception for window COM operation failures (hide, close, maximize, etc.). Modern: these surface as UiAutomationException; no dedicated window-operation type.
Image (UiPath.Core)
InvalidImageExceptionUiAutomationExceptionParcialClassic: dedicated exception for invalid image data. Modern: image errors surface as UiAutomationException; no dedicated image exception type.
InvalidRegionExceptionUiAutomationExceptionParcialClassic: screen region is null or empty. Modern: no dedicated region exception; surfaces as UiAutomationException.
ImageOperationExceptionUiAutomationExceptionParcialClassic: dedicated catch-all for any image operation failure. Modern: image operation failures surface as UiAutomationException; no dedicated type.
Scrape (UiPath.Core)
InvalidScrapeOptionsException(none)No counterpartClassic scrape options pattern does not exist in modern; scraping is handled differently with no equivalent options object.
ActiveX (UiPath.Core.Activities)
AutomateActiveXException(none)No counterpartActiveX automation is a classic-only feature; not available in modern activities.
ActiveXOutputArgumentsNotSupportedException(none)No counterpartActiveX-only feature.
ActiveXUnknownMethodException(none)No counterpartActiveX-only feature.
ActiveXInvalidArgumentsException(none)No counterpartActiveX-only feature.
InjectDotNet (UiPath.Core.Activities)
InjectDotNetMethodNotFoundException(none)No counterpart"Inject .NET Code" activity is classic-only; no modern equivalent activity.
InjectDotNetAmbiguousMethodException(none)No counterpartClassic-only feature.
InjectDotNetTypeNotFoundException(none)No counterpartClassic-only feature.
InjectDotNetTypeNotSupportedException(none)No counterpartClassic-only feature.
InjectDotNetAssemblyReflectionException(none)No counterpartClassic-only feature; also not thrown in production.
InjectDotNetArgumentNotDefinedException(none)No counterpartClassic-only feature.

Repo. de Objetos

Você só pode usar o Object Repository na experiência moderna com atividades modernas.

Assistentes de Extração

  • Experiência Moderna: o assistente Extração de Tabela está disponível para a extração de dados.
  • Experiência Clássica: os assistentes de Extração de Dados e Extração de Telas estão disponíveis.
  • Gravadores
  • Atividades
  • Exceções
  • Repo. de Objetos
  • Assistentes de Extração

Esta página foi útil?

Conectar

Precisa de ajuda? Suporte

Quer aprender? Academia UiPath

Tem perguntas? Fórum do UiPath

Fique por dentro das novidades