- Primeros pasos
- Instalación y configuración
- Requisitos de hardware y software
- Acerca de las Licencias de Precios Unificados
- Acerca de las Licencias Flexibles
- Activar Studio
- Actualizar Studio
- Parámetros de la línea de comandos
- Aplicaciones y tecnologías compatibles
- Habilitación de Gmail para actividades de correo electrónico
- Deshabilitar la telemetría
- Studio Executables
- Proyectos de automatización
- Acerca de la publicación de proyectos de automatización
- Diseñar automatizaciones
- Gestionar paquetes de actividades
- Configuración de los Ajustes del Proyecto de Actividades
- Firma de paquetes
- Control
- Importar entidades
- Vincular un proyecto a una idea en Automation Hub
- Usar Data Manager
- Soluciones
- Dependencias
- Tipos de flujos de trabajo
- Flujo de control
- Comparación de archivos
- Mejores prácticas de automatización
- Integración del control de código fuente
- Depuración
- Registro
- La herramienta de diagnóstico
- Analizador de flujo de trabajo
- Acerca del analizador de flujo de trabajo
- ST-NMG-001: convención sobre nombres de variables
- ST-NMG-002: convención de nombres de argumentos
- ST-NMG-004: duplicación de nombres de visualización
- ST-NMG-005: anulación de variables
- ST-NMG-006: argumentos de anulación de variables
- ST-NMG-008: longitud variable excedida
- ST-NMG-009: variables de datos prefijados
- ST-NMG-011: argumentos de prefijo Datatable
- ST-NMG-012: valores predeterminados de los argumentos
- ST-NMG-016: longitud del argumento excedida
- ST-NMG-017: el nombre de la clase coincide con el espacio de nombres predeterminado
- ST-DBP-002: recuento de Argumentos elevado
- ST-DBP-003: bloque de Catch vacío
- ST-DBP-007: múltiples capas de diagramas de flujo
- ST-DPB-010: varias instancias de [flujo de trabajo] o [caso de prueba]
- ST-DBP-020: propiedades de salida no definidas
- ST-DBP-021: tiempo de espera codificado
- ST-DBP-023: flujo de trabajo vacío
- ST-DBP-024: comprobación de actividad de persistencia
- ST-DBP-025: requisito previo para la serialización de variables
- ST-DBP-027: mejor práctica de persistencia
- ST-DBP-028: requisito de serialización de argumentos
- ST-USG-005 - Propiedades de la actividad codificadas
- ST-USG-009: variables no utilizadas
- ST-USG-010: dependencias sin utilizar
- ST-USG-014: restricciones de los paquetes
- ST-USG-017: modificador de parámetro no válido
- ST-USG-020: mensajes de registro mínimos
- ST-USG-024: guardado sin usar para más adelante
- ST-USG-025: uso incorrecto de los valores guardados
- ST-USG-026: restricciones de actividad
- ST-USG-027: paquetes necesarios
- ST-USG-028: Restringir la invocación de plantillas de archivo
- ST-USG-032 - Etiquetas obligatorias
- ST-USG-034 - URL Automation Hub
- Variables
- Argumentos
- Espacios de nombres importados
- Automatizaciones codificadas
- Introducción
- Registrar servicios personalizados
- Contextos Antes y Después
- Generando código
- Generar casos de prueba codificados a partir de casos de prueba manuales
- Integración de OpenAI con los flujos de trabajo codificados
- Solicita un préstamo con UiBank
- Generación de colas con flujos de trabajo codificados y API de Orchestrator
- Utilizar proyectos de biblioteca importados en automatizaciones codificadas
- Uso de la autenticación de dos factores dentro de automatizaciones codificadas
- Conectar a MongoDB Atlas con automatizaciones codificadas
- Solución de problemas
- Automatización atendida basada en desencadenadores
- Repo. de objetos
- La herramienta ScreenScrapeJavaSupport
- Extensiones
- Acerca de las extensiones
- Herramienta SetupExtensions
- UiPathRemoteRuntime.exe no se está ejecutando en la sesión remota
- UiPath Remote Runtime impide que la sesión de Citrix pueda cerrarse
- UiPath Remote Runtime provoca una fuga de memoria
- Las versiones del paquete UiPath.UIAutomation.Activities y UiPath Remote Runtime no coinciden
- La extensión de UiPath necesaria no está instalada en la máquina remota
- Configuración de la resolución de la pantalla
- Políticas de grupo
- No se puede comunicar con el navegador
- La extensión de Chrome se elimina automáticamente
- Es posible que la extensión se haya dañado
- Comprueba si la extensión para Chrome está instalada y habilitada
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Habilitar el acceso a las URL de archivos y el modo de incógnito
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- Lista de extensiones para Chrome
- Extensión de Chrome en Mac
- Políticas de grupo
- No se puede comunicar con el navegador
- La extensión de Edge se elimina automáticamente
- Es posible que la extensión se haya dañado
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- Lista de extensiones para Edge
- Extensión para Safari
- Extensión para Amazon WorkSpaces
- Complemento SAP Solution Manager
- Add-in de Excel
- Pruebas de Studio
- Solución de problemas
- Acerca de la resolución de problemas
- Errores de compilación del ensamblado
- Compatibilidad y limitaciones de Microsoft App-V
- Solución de problemas de Internet Explorer x64
- Problemas de Microsoft Office
- Identificación de elementos de la interfaz de usuario en PDF con opciones de accesibilidad
- Reparar Soporte Active Accessibility
- Validation of large Windows-legacy projects takes longer than expected
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.
Overview tab
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:
| Estado | Descripción |
|---|---|
| correcta | 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.
Pestaña Proyectos
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.