UiPath Documentation
studio
latest
false
Wichtig :
Es kann 1–2 Wochen dauern, bis die Lokalisierung neu veröffentlichter Inhalte verfügbar ist.
UiPath logo, featuring letters U and I in white

Studio-Benutzerhandbuch

Letzte Aktualisierung 15. Apr. 2026

Unterschiede zwischen moderner und klassischer Umgebung

Recorder

Aktivitäten

In jeder Umgebung ist standardmäßig ein separater Satz von Aktivitäten verfügbar.

Unabhängig von der für ein Projekt ausgewählten Umgebung können Sie auch die Aktivitäten aktivieren, die nur standardmäßig in der anderen Umgebung verfügbar sind. Klicken Sie oben im Bereich Aktivitäten auf Optionen anzeigen und wählen Sie dann folgende Option aus:

  • Modern anzeigen, um moderne Aktivitäten in einem Projekt anzuzeigen, das die klassische Umgebung verwendet.

  • Klassisch anzeigen, um klassische Aktivitäten in einem Projekt anzuzeigen, das die moderne Umgebung verwendet.

    docs image

In der folgenden Tabelle sind die Aktivitäten aufgeführt, die standardmäßig nur in einer der beiden Umgebungen verfügbar sind. Die UI-Automatisierungsaktivitäten, die nicht in der Tabelle aufgeführt sind, sind in beiden Umgebungen standardmäßig verfügbar.

Moderne AktivitätenKlassische Aktivitäten
Aktivieren (Activate)Klicken, Tastenkombinationen, Eingeben in
Check App StateOn Element Appear, On Element Vanish, On Image Appear, On Image Vanish, Wait Element Vanish, Wait Image Vanish, Find Image, Image Exists, Element Exists
Check/UncheckPrüfen (Check)
Klicken (Click)Klicken, Bild klicken
Extract Table DataExtract Structured Data, Get Full Text, Get Visible Text
Text erhalten (Get Text)Text erhalten (Get Text)
Zu URL wechselnNavigieren zu (Navigate To)
Markieren (Highlight)Markieren (Highlight)
Darauf zeigen (Hover)Hover, Hover Image
TastenkombinationenHotkey senden (Send Hotkey)
Navigate BrowserClose Tab, Go Back, Go Forward, Go Home, Refresh Browser
Objekt auswählen (Select Item)Objekt auswählen (Select Item)
Screenshot anfertigen (Take Screenshot)Screenshot anfertigen (Take Screenshot)
Eingeben in (Type Into)Type Into, Type Secure Text
Use Application/BrowserAnwendung öffnen, Browser öffnen, Fenster anhängen, Browser anhängen, Element Scope, Fenster schließen Start Prozess
Keine AngabeAnchor Base, Context Aware Anchor

Ausnahmen

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).

KlassischModern (UiPath.UIAutomationNext.Exceptions)ZuordnungHinweise
General Activity (UiPath.Core.Activities)
ElementNotSetExceptionNotInitializedExceptionTeilweiseClassic: element not provided in context. Modern: InUIElement property not initialized before use. Concept is the same; modern is scoped to the InUIElement input specifically.
TextNotFoundExceptionNodeNotFoundExceptionTeilweiseClassic: 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.
WindowNotSetExceptionApplicationNotFoundExceptionTeilweiseClassic: 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 (intern)(none)No counterpartInternal class; no equivalent in modern.
SelectorOperationExceptionUiAutomationExceptionTeilweiseClassic: 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.
FindElementExceptionRuntimeFindExceptionTeilweiseClassic: 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.
InvalidUiElementExceptionNodeNotFoundExceptionTeilweiseClassic: 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.
ElementOperationExceptionUiAutomationExceptionTeilweiseClassic: 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)
InvalidBrowserExceptionBrowserNotFoundExceptionTeilweiseClassic: 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.
BrowserOperationExceptionUiAutomationExceptionTeilweiseClassic: dedicated exception for browser COM operation failures. Modern: browser operation failures surface as UiAutomationException; no dedicated browser-operation type.
Window (UiPath.Core)
InvalidWindowExceptionApplicationNotFoundExceptionTeilweiseClassic: window COM reference is null before an operation. Modern: application not found when attaching. Closest equivalent; modern is broader (all app types).
WindowOperationExceptionUiAutomationExceptionTeilweiseClassic: dedicated exception for window COM operation failures (hide, close, maximize, etc.). Modern: these surface as UiAutomationException; no dedicated window-operation type.
Image (UiPath.Core)
InvalidImageExceptionUiAutomationExceptionTeilweiseClassic: dedicated exception for invalid image data. Modern: image errors surface as UiAutomationException; no dedicated image exception type.
InvalidRegionExceptionUiAutomationExceptionTeilweiseClassic: screen region is null or empty. Modern: no dedicated region exception; surfaces as UiAutomationException.
ImageOperationExceptionUiAutomationExceptionTeilweiseClassic: 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.

Objekt-Repository

Sie können das Object Repository nur in der modernen Umgebung mit modernen Aktivitäten verwenden.

Extraktions-Assistenten

  • Moderne Umgebung – Der Tabellenextraktions-Assistent steht für die Datenextraktion zur Verfügung.
  • Klassische Umgebung – Die Assistenten zur Datenextraktion und für das Screen Scraping sind verfügbar.
  • Recorder
  • Aktivitäten
  • Ausnahmen
  • Objekt-Repository
  • Extraktions-Assistenten

War diese Seite hilfreich?

Verbinden

Benötigen Sie Hilfe? Support

Möchten Sie lernen? UiPath Academy

Haben Sie Fragen? UiPath-Forum

Auf dem neuesten Stand bleiben