- Erste Schritte
- Einstellung und Konfiguration (Setup and Configuration)
- Automationsprojekte
- Über die Veröffentlichung von Automatisierungsprojekten
- Entwerfen von Automatisierungen
- Verwalten von Aktivitätspaketen
- Konfigurieren von Aktivitätsprojekteinstellungen
- Signieren von Paketen
- Governance
- Importieren von Entitäten
- Verknüpfen eines Projekts mit einer Idee im Automation Hub
- Verwenden des Data Managers
- Solutions (Lösungen)
- Abhängigkeiten
- Workflow-Typen
- Kontrollfluss
- Dateivergleich
- Beste Praktiken für die Automatisierung (Automation Best Practices)
- Integration der Quellenkontrolle
- Informationen zur Versionskontrolle
- Verwalten von Projekten mit TFS
- Verwalten von Projekten mit SVN
- Workflow Diff
- Das Source Control-Panel
- Debugging
- Protokollierung
- Das Diagnose-Tool
- Workflow-Analyse
- Über die Workflow-Analyse
- ST-NMG-001 – Namenskonvention für Variablen
- ST-NMG-002 – Namenskonvention für Argumente
- ST-NMG-004 – Duplizierung des Anzeigenamens
- ST-NMG-005 – Variable überschreibt Variable
- ST-NMG-006 – Variable überschreibt Argument
- ST-NMG-008 – Variablenlänge überschritten
- ST-NMG-009: Datentabellenvariablen mit Präfix versehen
- ST-NMG-011 – Datentabellenargumente mit Präfix versehen
- ST-NMG-012 – Standardwerte für Argumente
- ST-NMG-016 – Argumentlänge überschritten
- ST-NMG-017 – Der Klassenname stimmt mit dem Standard-Namespace überein
- ST-DBP-002 – Hohe Anzahl von Argumenten
- ST-DBP-003 – Leerer Catch-Block
- ST-DBP-007 – Mehrere Flussdiagrammebenen
- ST-DPB-010 – Mehrere Instanzen von [Workflow] oder [Testfall]
- ST-DBP-020 – Nicht definierte Ausgabeeigenschaften
- ST-DBP-021 – Hartcodiertes Timeout
- ST-DBP-023 – Leerer Workflow
- ST-DBP-024 – Prüfung der Persistenzaktivität
- ST-DBP-025 – Voraussetzung für Variablenserialisierung
- ST-DBP-027 – Bewährte Methode für Persistenz
- ST-DBP-028 – Voraussetzung für Argumentenserialisierung
- ST-USG-005 – Hartcodierte Aktivitätseigenschaften
- ST-USG-009 – Nicht verwendete Variablen
- ST-USG-010 – Nicht verwendete Abhängigkeiten
- ST-USG-014 – Paketbeschränkungen
- ST-USG-017 – Ungültiger Parametermodifizierer
- ST-USG-020 – Minimale Protokollmeldungen
- ST-USG-024 – Nicht verwendet, gespeichert für später
- ST-USG-025 – Missbrauch gespeicherter Werte
- ST-USG-026 – Aktivitätseinschränkungen
- ST-USG-027 – Erforderliche Pakete
- ST-USG-028 – Aufruf von Dateivorlagen einschränken
- ST-USG-032 – Erforderliche Tags
- ST-USG-034 – Automation Hub-URL
- Variablen
- Argumente
- Importierte Namespaces
- Codierte Automatisierungen
- Einleitung
- Registrieren von benutzerdefinierten Diensten
- „Vor“- und „Nach“-Kontexte
- Generieren von Code
- Generieren eines codierten Testfalls aus manuellen Testfällen
- Integrieren von OpenAI in codierte Workflows
- Beantragen eines Kredits bei der UiBank
- Warteschlangengenerierung mit codierten Workflows und Orchestrator-APIs
- Verwenden importierter Bibliotheksprojekte in codierten Automatisierungen
- Verwenden der zweistufigen Authentifizierung in codierten Automatisierungen
- Herstellen einer Verbindung zu MongoDB Atlas mit codierten Automatisierungen
- Fehlersuche und ‑behebung
- Triggerbasierte Attended-Automatisierung
- Objekt-Repository
- Das Tool ScreenScrapeJavaSupport
- Erweiterungen
- Über Erweiterungen
- SetupExtensions-Tool
- „UiPathRemoteRuntime.exe“ wird nicht in der Remotesitzung ausgeführt.
- UiPath Remote Runtime blockiert das Schließen der Citrix-Sitzung
- UiPath Remote Runtime verursacht Speicherverlust
- Versionen von UiPath.UIAutomation.Activities-Paket und UiPath Remote Runtime stimmen nicht überein
- Die erforderliche UiPath-Erweiterung ist auf der Remotemaschine nicht installiert
- Einstellungen für die Bildschirmauflösung
- Gruppenrichtlinien
- Kommunikation mit Browser nicht möglich
- Die Chrome-Erweiterung wird automatisch entfernt
- Möglicherweise ist die Erweiterung beschädigt
- Überprüfen Sie, ob die Erweiterung für Chrome installiert und aktiviert ist
- Überprüfen Sie, ob ChromeNativeMessaging.exe ausgeführt wird
- Überprüfen der korrekten Definition der ComSpec-Variablen
- Aktivieren Sie den Zugriff auf Datei-URLs und den Inkognito-Modus
- Mehrere Browser-Profile
- Group Policy conflict
- Spezifische bekannte Probleme für MV3-Erweiterungen
- Liste der Erweiterungen für Chrome
- Chrome-Erweiterung für Mac
- Gruppenrichtlinien
- Kommunikation mit Browser nicht möglich
- Die Edge-Erweiterung wird automatisch entfernt
- Möglicherweise ist die Erweiterung beschädigt
- Überprüfen, ob die Erweiterung für Microsoft Edge installiert und aktiviert ist
- Überprüfen Sie, ob ChromeNativeMessaging.exe ausgeführt wird
- Überprüfen der korrekten Definition der ComSpec-Variablen
- Aktivieren des Zugriffs auf Datei-URLs und den InPrivate-Modus
- Mehrere Browser-Profile
- Group Policy conflict
- Spezifische bekannte Probleme für MV3-Erweiterungen
- Liste der Erweiterungen für Edge
- Erweiterung für Safari
- Erweiterung für Amazon WorkSpaces
- SAP Solution Manager-Plugin
- Excel-Add-in
- Studio Testing
- Fehlersuche und ‑behebung
- Informationen zur Fehlerbehebung
- Fehler bei der Assembly-Kompilierung
- Microsoft App-V – Unterstützung und Einschränkungen
- Fehlerbehebung bei Internet Explorer x64
- Probleme in Microsoft Office
- Erkennen von UI-Elementen in PDF mit Zugriffsoptionen.
- Reparieren der Active Accessibility-Unterstützung
- Die Validierung großer Windows-Legacy-Projekte dauert länger als erwartet
Migration report
HTML migration report generated by Activity Migrator, including the report structure, tabs, and bulk-run view.
The analyze, upgrade, and bulk commands generate an HTML migration report alongside the SARIF report. Both reports are saved in the .upgrade folder of the original project.
The HTML report file is named after the project, followed by a unique identifier, for example GSuiteMigration-7de07881-c2fa-4f2b-b750-28b1c483dbad.html. The file can be opened in a browser to view the report.
A log file is also saved next to the report (project-<id>.log in the .upgrade folder).
Viewing the HTML report requires a recent browser, such as Microsoft Edge or Google Chrome version 123 or later.
The report header shows the project name, the overall migration status (for example, Completed with errors), the Activity Migrator version, the duration of the run, and the date and time it ran.
The HTML report is organized into the following tabs:
- Overview: A summary of the migration results and the actions required after migration.
- Projects: The projects included in the run and their migration status. It appears only for bulk runs.
- Workflows: Every workflow in the project, with its migration status, activity outcomes, and findings.
- Findings: All errors, warnings, and notes reported during migration.
- Run details: Information about the migration run, the project and log files, and the results reported by each migration rule.
Registerkarte „Übersicht“
The Overview tab contains the following:
- Status summary: The overall result of the migration, with the number of workflows analyzed, activities attempted, and errors and warnings reported.
- Summary cards:
- Errors: Issues that need manual work.
- Warnings: Issues for which a review is recommended.
- Notes: Informational steps.
- Workflows: The number of workflows that are clean, have warnings, or have errors.
- Activities migrated: The number of activities that migrated cleanly, migrated with warnings, or failed.
- Migration breakdown: Bar charts that show workflows by status and activity outcomes.
- Project-level results: Findings that apply to the project as a whole rather than to a specific workflow, such as the general migration summary for each extension.
- Next steps: The action items marked as PostMigration Action Required, which you must fix in Studio after the migration. Each item shows the activity, the reason, the workflow file, and the finding code. Selecting View all action items shows the full list.
The migration can have one of the following statuses:
| Status | Beschreibung |
|---|---|
| Erfolgreich | All workflows and activities were migrated without issues. |
| Completed with warnings | Everything was migrated, but some results need a review, such as validation errors or incomplete migrations in the resulting workflows. |
| Completed with errors | Some workflows or activities couldn't be migrated. The original workflow is kept in the output folder. You can try to migrate it manually in Studio, but this isn't guaranteed to work. |
Workflows tab
The Workflows tab lists every workflow in the project with its migration status. It contains the following:
- Status filters: Show all workflows, or only the workflows with a specific status. Each filter shows the number of workflows with that status.
- Not migrated: Workflows with activities that failed to migrate.
- With warnings: Workflows that migrated, but have warnings to review.
- Clean: Workflows that migrated without issues.
- Filter by workflow path: Search for workflows by their path in the project.
- Results summary: The number of workflows shown, along with the totals for failed activities, validation issues, and action items.
- Workflows table:
- Workflow: The workflow path, relative to the project folder.
- Status: The migration status of the workflow. Selecting the column header sorts by status.
- Activities: The number of activities in the workflow, broken down into migrated, with warnings, and failed, along with a progress bar.
- Problems in: The migration step that reported the issues, for example GSuite Activities Upgrade.
Selecting a workflow opens its findings.
Findings tab
The Findings tab lists all the results reported during migration. By default, it shows errors and warnings. It contains the following:
- Level filters: Show or hide findings by level. Each filter shows the number of findings at that level.
- Errors: Activities that couldn’t be migrated and need manual work.
- Warnings: Issues for which a review is recommended.
- Notes: Informational steps performed during migration.
- Action required: Findings marked as PostMigration Action Required, which you must fix in Studio after the migration.
- Search: Search findings by message, workflow, or activity.
- Rule: Show only the findings reported by a specific migration rule.
- Group by: Group the findings, for example by workflow. Each group shows the workflow path and the number of findings it contains. Selecting a group expands or collapses it.
- Show all results: Display all findings, at every level.
The findings table contains the following columns:
- Level: The severity of the finding: Error, Warning, or Note.
- Message: The description of the finding. Findings that require action after migration are labeled Action required. For longer messages, selecting the link below the message, for example +1 more line, expands the full text.
- Activity: The display name of the affected activity.
- Rule: The migration rule that reported the finding, for example CreateScriptDeployment Activity Migration.
Selecting a finding opens its details. The details window contains the following:
- Activity: The activity before and after migration. For example, a Get Outlook Mail Messages activity can be replaced by a migrated Get Outlook Mail Messages activity and an Assign activity. If the activity couldn't be migrated, the After side is empty. Below it, the finding message explains the result.
- About the rule: A description of the migration rule that reported the finding, including what the rule migrates and which properties it preserves. Selecting the heading expands or collapses the description.
- Level: The severity of the finding: Error, Warning, or Note.
- Workflow: The workflow that contains the activity.
- Step: The migration step that reported the finding, for example Mail Activities Upgrade.
- Rule: The display name and the ID of the rule that reported the finding.
Run details tab
The Run details tab contains information about the migration run itself:
-
Run summary:
- Execution: Whether the migration ran to completion, for example All steps ran.
- Started and Finished: The date and time the run started and ended.
- Duration: How long the run took.
- Tool version: The version of the Activity Migrator used for the run.
-
Files:
- Project folder: The path to the migrated project.
- Log file: The path to the migration log file, saved in the
.upgradefolder of the project. Selecting the path opens the log file.
Selecting Copy next to a path copies it to the clipboard.
-
Results by rule: The migration rules that reported results during the run. The header shows the number of rules reported. For each rule, the table shows:
- Rule: The display name and the ID of the rule, for example CreateScriptDeployment Activity Migration (
CREATE-SCRIPT-DEPLOYMENT-ACTIVITY-MIGRATION). - Results: The number of results the rule reported, by level.
- Locations: The number of locations where the rule reported results.
Selecting a rule opens its description and results.
- Rule: The display name and the ID of the rule, for example CreateScriptDeployment Activity Migration (
The filters and search narrow the results. For each changed activity, the activity before and after migration is available for review. The theme selector in the top-right corner of the report switches between light and dark mode. Auto follows your system setting.
Bulk migration report
For bulk runs, the Activity Migrator also generates a report for all projects, saved in the folder specified with the -p, --path option, for example repository-analyze-results.html. Each project still gets its own report in its .upgrade folder.
For this case, the HTML report contains the same tabs as the project report, plus a Projects tab and an all-projects view that lists the projects needing attention first.
The report header shows the number of projects and how many of them need attention. The Project dropdown in the top-right corner switches between All projects and the results of an individual project.
Registerkarte Projekte
The Projects tab lists all the projects included in the bulk run. By default, the projects that need attention are shown first. It contains the following:
- Status filters: Show all projects, or only the projects with a specific status: Need attention, With warnings, or Clean. Each filter shows the number of projects with that status.
- Filter by project name or path: Search for projects by name or folder path.
- Has problem: Show only the projects with a specific type of problem.
- Projects table:
- Project: The project name and folder path.
- Status: The migration status of the project, for example Succeeded, Completed with warnings or Completed with errors. Selecting the column header sorts by status.
- Workflows: The number of workflows in the project and how many of them migrated cleanly, along with a progress bar.
- Errors, Warnings, and Notes: The number of findings at each level.
- Actions: The number of action items that require manual fixes in Studio after the migration.
- Duration: How long the migration of the project took.
Viewing a project in the bulk report
Selecting a project in the Projects table, or from the Project dropdown, opens its detailed results. The dropdown shows each project's name and status, for example CreateSAPOrders · Warnings.
The project opens with the same Overview, Workflows, Findings, and Run details tabs as a project report. In addition:
- The breadcrumb at the top of the page shows the selected project. Selecting All projects returns to the results for all projects.
- The project navigation in the top-right corner shows the position of the project in the list, for example 1 of 3, worst first. The arrows go to the previous or next project. Projects are ordered starting with the ones that need the most attention.