- Démarrage
- Paramétrage et configuration
- Prérequis logiciels et matériels
- À propos des licences à tarification unifiée
- À propos des licences Flex
- Activation de Studio
- Mettre à jour Studio
- Paramètres de la ligne de commande
- Applications et technologies prises en charge
- Activer Gmail pour les activités de messagerie
- Refus de la télémétrie
- Exécutables Studio
- Projets d'automatisation
- À propos de la publication de projets d'automatisation
- Conception d'automatisations
- Gérer les package d’activités
- Configuration des paramètres du projet d'activité
- Signature de paquets
- Gouvernance
- Import des entités
- Lier un projet à une idée dans Automation Hub
- Utilisation du gestionnaire de données
- Solutions
- Dépendances
- Types de workflows
- Flux de contrôle
- Comparaison de fichiers
- Meilleures pratiques d'automatisation
- Intégration du contrôle de code source
- À propos du contrôle de version
- Gestion de projets à l'aide de TFS
- Gestion de projets à l'aide de SVN
- Diff de workflow
- Le panneau de contrôle de code source
- Débogage
- Journalisation
- L'outil de diagnostic (Diagnostic Tool)
- Analyseur de workflow
- À propos de l'analyseur de workflow
- ST-NMG-001 - Convention d'affectation de noms des variables
- ST-NMG-002 - Convention d'affectation de noms des arguments
- ST-NMG-004 - Duplication du nom complet
- ST-NMG-005 - La variable remplace une autre
- ST-NMG-006 - La variable remplace l'argument
- ST-NMG-008 - Longueur de variable dépassée
- ST-NMG-009 - Ajouter un préfixe aux variables DataTable
- ST-NMG-011 - Ajouter un préfixe aux arguments Datatable
- ST-NMG-012 - Valeurs par défaut de l'argument
- ST-NMG-016 : longueur d'argument dépassée
- ST-NMG-017 : le nom de la classe correspond à l’espace de noms par défaut
- ST-DBP-002 - Nombre élevé d'arguments
- ST-DBP-003 - Bloc d'interception vide
- ST-DBP-007 - Plusieurs couches de l'organigramme
- ST-DPB-010 : plusieurs instances de [workflow] ou [cas de test]
- ST-DBP-020 - Propriétés de sortie non définies
- ST-DBP-021 - Délai d'expiration codé en dur
- ST-DBP-023 : Workflow vide
- ST-DBP-024 - Vérification de l’activité de persistance
- ST-DBP-025 - Condition préalable à la sérialisation des variables
- ST-DBP-027 - Pratiques exemplaires de persistance
- ST-DBP-028 - Condition préalable à la sérialisation des arguments
- ST-MRD-002 - Valeurs par défaut des noms d'activités
- ST-MRD-004 - Activités inaccessibles
- ST-MRD-005 - Séquences redondantes
- ST-MRD-007 - Clauses If imbriquées
- ST-MRD-008 - Séquence vide
- ST-MRD-009 - Activités profondément imbriquées
- ST-MRD-011 - Utilisation de la ligne d'écriture
- ST-MRD-017 - Incomplet si (Incomplete If)
- ST-USG-005 - Propriétés de l'activité codées en dur
- ST-USG-009 - Variables inutilisées
- ST-USG-010 - Dépendances inutilisées
- ST-USG-014 - Restrictions sur les paquets (Package Restriction)
- ST-USG-017 - Modificateur de paramètre non valide
- ST-USG-020 - Nombre minimum de messages consignés
- ST-USG-024 - Non utilisé, sauvegardé pour plus tard (Unused Saved for Later)
- ST-USG-025 - Utilisation abusive de la valeur enregistrée (Saved Value Misuse)
- ST-USG-026 - Restrictions d'activité (Activity Restrictions)
- ST-USG-027 - Packages requis
- ST-USG-028 - Restreindre l'invocation des modèles de fichier
- ST-USG-027 - Balises requises
- ST-USG-034 – URL Automation Hub
- Variables
- Arguments
- Noms d'espace importés
- Automatisations codées
- Introduction
- Enregistrement de services personnalisés
- Contextes Avant (Before) et Après (After)
- Génération du code
- Génération de cas de test codé à partir de cas de test manuels
- Intégration d'OpenAI avec des workflows codés
- Demander un prêt auprès de UiBank
- Génération de files d'attente avec workflows codés et API Orchestrator
- Utilisation de projets de bibliothèque importés dans des automatisations codées
- Utilisation de l’authentification à deux facteurs dans des automatisations codées
- Connexion à MongoDB Atlas avec des automatisations codées
- Résolution des problèmes
- Automatisation Attended basée sur déclencheur
- Réf. d’objets
- Outil ScreenScrapeJavaSupport
- Extensions
- À propos des extensions
- Outil SetupExtensions
- UiPathRemoteRuntime.exe n'est pas en cours d'exécution dans la session distante
- UiPath Remote Runtime bloque la fermeture de la session Citrix
- UiPath Remote Runtime provoque une fuite de mémoire
- Le package UiPath.UIAutomation.Activities ne correspond pas aux versions d’UiPath Remote Runtime
- L'extension UiPath requise n'est pas installée sur la machine distante
- Paramètres de résolution d’écran
- Stratégies de groupe
- Impossible de communiquer avec le navigateur
- L’extension Chrome est automatiquement supprimée
- L'extension a peut-être été corrompue
- Vérification de l'installation et de l'activation de l'extension pour Chrome
- Vérifiez si ChromeNativeMessaging.exe est en cours d’exécution
- Vérifier si la variable ComSpec est correctement définie
- Activez l’accès aux URL de fichiers et au mode navigation privée
- Profils de navigateur multiples
- Group Policy conflict
- Problèmes connus spécifiques aux extensions MV3
- Liste des extensions pour Chrome
- Extension Chrome sur Mac
- Stratégies de groupe
- Impossible de communiquer avec le navigateur
- L’extension Edge est automatiquement supprimée
- L'extension a peut-être été corrompue
- Vérification si l'extension pour Microsoft Edge est installée et activée
- Vérifiez si ChromeNativeMessaging.exe est en cours d’exécution
- Vérifier si la variable ComSpec est correctement définie
- Activation de l'accès aux URL de fichiers et au mode navigation privée
- Profils de navigateur multiples
- Group Policy conflict
- Problèmes connus spécifiques aux extensions MV3
- Liste des extensions pour Edge
- Extension pour Safari
- Extension pour Amazon WorkSpaces
- Plug-in du gestionnaire de solution SAP
- Complément Excel
- Tests Studio
- Résolution des problèmes
- À propos de la résolution des problèmes
- Erreurs de compilation de l’assembly
- Prise en charge et limitations de Microsoft App-V
- Résolution des problèmes rencontrés avec Internet Explorer x64
- Problèmes rencontrés avec Microsoft Office
- Identification des éléments d'IU dans PDF avec options d'accessibilité
- Réparation de la prise en charge d'Active Accessibility
- La validation des projets volumineux hérités depuis Windows prend plus de temps que prévu
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.
Onglet Vue d'ensemble (Overview)
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:
| État (Status) | Description |
|---|---|
| réussie | 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.
Onglet Projets
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.