- Versionshinweise
- 2024.10.1
- 2024.10.5
- 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
- Moderne Designumgebung
- Verknüpfen eines Projekts mit einer Idee im Automation Hub
- Verwenden des Data Managers
- Abhängigkeiten
- Workflow-Typen
- 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
- Debugging
- 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 - Class name matches default namespace
- ST-DBP-002 – Hohe Anzahl von Argumenten
- ST-DBP-003 – Leerer Catch-Block
- ST-DBP-007 – Mehrere Flussdiagrammebenen
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- 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-026 – Verwendung der Verzögerungsaktivität
- ST-DBP-027 – Bewährte Methode für Persistenz
- ST-DBP-028 – Voraussetzung für Argumentenserialisierung
- ST-USG-005 – Hartcodierte Aktivitätsargumente
- ST-USG-009 – Nicht verwendete Variablen
- ST-USG-010 – Nicht verwendete Abhängigkeiten
- ST-USG-014 – Paketbeschränkungen
- 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
- Triggerbasierte Attended-Automatisierung
- Aufzeichnung
- UI-Elemente
- Kontrollfluss
- Selektoren
- Objekt-Repository
- Data-Scraping
- Bild- und Textautomatisierung
- Automatisierung von Citrix-Technologien
- RDP-Automatisierung
- VMware Horizon-Automatisierung
- Salesforce-Automatisierung
- SAP-Automation
- Protokollierung
- Das Tool ScreenScrapeJavaSupport
- Das WebDriver-Protokoll
- Test Suite – Studio
- 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
- UiPath.UIAutomation.Activities-Pakete und UiPath Remote Runtime-Versionen stimmen nicht überein
- Die erforderliche UiPath-Erweiterung ist auf der Remotemaschine nicht installiert
- Einstellungen für die Bildschirmauflösung
- Chrome-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
- Edge-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 VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager-Plugin
- Excel-Add-in
- Fehlersuche und ‑behebung
- Informationen zur Fehlerbehebung
- 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
2024.10.5
Release date: 21 October 2024
Autopilot can also generate activity output variables which are then automatically used in subsequent activities (for example, Autopilot will use the output variable generated for a Create Event activity in the Event field of a Forward Event activity).
The new Autopilot panel makes the development process more accessible and efficient.
Two new Workflow Analyzer rules are now available to help with migrating projects from the Windows - Legacy to the Windows compatibility.
Workflow Analyer rule for code
- ST-DPB-010: Make sure that within any coded workflow or test case, only one method is marked with either the
[Workflow]
or[Test Case]
attribute. - ST-NMG-017: Ensures that a class name is distinct from the default namespace.
XML documentation file for your custom code and libraries
XML
documentation files after you publish a project and enjoy the benefit of code documentation for your custom code and libraries. After the project is published, the XML
files are generated alongside the DLL
and PDB
files in your project folder. You can also find them in the lib folder of the generated NUPKG
file. Visit Working with Coded automations to learn more about publishing projects that contain coded automations.
XBrowser-Testvorlage
Streamline your testing processes of websites and web applications by using the XBrowser Test Template. This template allows you to test the same test data of a web application with multiple browsers, all into one single automation. Visit XBrowser Test Template for more information.
Generating low-code test cases using AI
You can now generate a fully automated low-code test case using natural language, with the help of AutopilotTM. Visit Generating test cases using AI to check how to generate low-code test cases.
We have made several improvements to the way in which you can manage cloud projects.
When a cloud project is edited in Studio Web, you can only open it in Studio in read-only mode (the project cannot be opened in edit mode both in Studio Web and Studio).
Studio now informs you every time you lose editing access (for example, when the project is edited by someone else or the cloud connection is lost), to avoid possible future conflicts when trying to save the project.
When a project is saved in a different location on your machine, you now have the option to either unlink the project from the cloud or use the new local path to the project.
When you open a project, Studio automatically detects if you manually moved the project to a different location on your machine, and your input is not needed.
Lastly, local and cloud projects are now clearly labeled as such in the Studio Backstage.
- New designs for the Start, State, and Final nodes.
- An infinite canvas Designer panel, with a new grid system to better position your activities.
- Improvements to the design and functionality of activities and connectors, complete with support for adding annotations.
- Korrigieren des Zeilenabstands und der Textausrichtung.
- Improving the layout of the Fix and Use Variables buttons.
- Hinzufügen dedizierter Schaltflächen Rückgängig ( Undo) und Wiederherstellen ( Redo )
- The following keyboard shortcuts now allow you to expand or reduce your current code selection as follows:
Ctrl + Shift + <Num+
: Expand your current code selection to include the next larger syntax node. From the current line, you can expand to include the current block, then the current method, the current class, the namespace, and finally the entire file.Ctrl + <Shift + Num-
: Contract the current syntax node selection incrementally.
- You can now record your interactions with UI elements and translate them into coded automations.
AI-generated test data improvements
- When using Autopilot for generating test data, you can instruct it to introduce additional arguments, which will be included in the test case once you import the generated data set.
- Now, you initially offer a prompt instruction to Autopilot to get a primary test data set. This is a change from the previous behavior where Autopilot initially created a test data set that you were able to refine using prompt instructions.
- You can instruct Autopilot to generate a certain number of data variations.
Improved error messages for Postman integration
We've made improvements to the API Test Automation. Error messages from the Postman integration are now more clearly displayed in the user interface.
Converting text into code improvements
You can now turn text into code by selecting the Autopilot icon or by choosing the existent Generate Code action.
- The
UiPathStudio.msi
installer no longer supports thePackages
command line feature flag . This does not impact the installation process, as the feature flag was kept for backwards compatibility and had no real function. UiPathStudio.msi
does not support direct upgrade from Studio 2018.4 or lower. Upgrading from such a version must be done through an intermediary upgrade to the latest 24.10 patch.
- Optimized compile times for complex projects including low-code and coded test cases, execution templates, and entities.
- You can now improve the alignment of flowchart nodes and connectors in the Designer panel by using the Auto arrange context menu option. You can choose to make your flowcharts more readable by arranging them either horizontally or vertically.
- Project validation is now faster.
- Die GIT-Integration in Studio unterstützt jetzt Schannel.
- The Dictionary Builder now supports complex expressions both in the Key and Value fields. You can also switch between the Expression Editor and the Dictionary Builder in activity properties that only used the Dictionary builder.
- You can now add a top level annotation to the main sequence of a project by right-clicking the Designer panel and selecting Annotations > Add Annotation. The main sequence is now hidden by default.
- We have improved the message you see in the Manage Packages window when you select an activities package that is not compatible with your project.
- The Project Dependencies Mass Update Tool now has an Install Missing Package option for updating dependencies which are already part of projects or installing dependencies in projects that do not contain them.
- To reduce the size of published packages, .git and .svn folders are now excluded from the resulting NUPKG file.
-
Several performance improvements have been made to RAM usage.
Coded Automations
To avoid conflicts when you use connections from the same Orchestrator folders, you now need to use a different naming convention when establishing connections in coded automations. After you create the connection in Integration Service, call it in your coded automation using both the Orchestrator folder and subfolder name where the connection resides.
var myGmailConnection = connections.Gmail.My_Workspace_john_doe_gmail_com
, where My_Workspace
is the Orchestrator folder name, you now need to include the subfolder name where the connection was first made. So if the Gmail connection is in the My Gmail Workspace
subfolder, you would change the connection name to: var myGmailConnection = connections.Gmail.My_Workspace_My_Gmail_Workspace_john_doe_gmail_com
.
For more details on the new way to set up service connections in coded automations, visit Creating Connections for services in coded automations.
Studio-Protokolle
Fatal
severity logs appear as Trace
logs in the Output panel and are filtered as Trace
logs when clicking the Trace button in the panel’s header.
- While debugging a XAML workflow within a project that contained CS files, an 'Unexpected error during library compilation: Value cannot be null. (Parameter 'type')' error occurred, which caused the compilation to fail.
- A Root element is missing error occurred when publishing some background processes.
- Einige Projekte mit fehlenden Abhängigkeiten wurden fälschlicherweise als veröffentlicht gemeldet, wenn das Massenaktualisierungstool für Projektabhängigkeiten verwendet wurde.
- Studio logged Bad IL format compilation errors when running some projects migrated from Windows - Legacy. These errors did not affect project execution.
- Unused dependencies were not correctly identified when analyzing some projects migrated from Windows - Legacy.
- Compilation failed for some projects where the combined length of user strings exceeded the allowed limit.
- Renaming a project caused invalid references in projects with XAML files referencing code assemblies.
- When creating custom activities using code, the UiPath.Workflow 6.0.0-20231211-03 package led to a version conflict with Microsoft.CodeAnalysis.Common. The solution involved adding a previously missing dependency.
- Publishing some projects with missing dependencies in a GitHub CI/CD pipeline did not return validation errors.
- The ST-NMG-004 - Display Name Duplication rule incorrectly detected repetitive activities names.
- The Locals panel did not display any information when debugging some projects saved on a network drive.
- Elastic Robot Pools were not displayed in the Machine drop-down menu when configuring an Unattended Robot remote debugging connection.
- Studio incorrectly detected workflow changes when debugging some projects using Step Into.
- The Text Builder showed a non-functional Plus button in cross-platform projects.
- Multiple BC31424 and BC30652 validation errors occurred when trying to publish some projects created in earlier versions of Studio.
- Publishing some projects that contained a large number of test cases (200+) took longer than expected.
- Compiling some projects containing a large number of workflows (1000+) took longer than expected.
- Application tracking does not work for applications used in libraries.
- When working with coded workflows or test cases, an error can occur. If you attempt to create arguments of any type (including In, Out, and In/Out) with certain names such as
result
,newResult
,codedWorkflow
andisolated
, you may encounter a compilation error.
UiPathStudio.msi
-Installationsprogramm enthalten und können im lokalen Feed gefunden werden.
Aktivitätspaket |
Version |
---|---|
UiPath.UIAutomation.Activities | |
UiPath.System.Activities | |
UiPath.Excel.Aktivitäten (UiPath.Excel.Activities) | |
UiPath.Mail.Aktivitäten (UiPath.Mail.Activities) | |
UiPath.Word.Aktivitäten (UiPath.Word.Activities) | |
UiPath.ComplexScenarios.Activities | |
UiPath.Presentations.Activities | |
UiPath.Testing.Activities | |
UiPath.WebApi.Activities | |
UiPath.Form.Activities | v24.10.5 |
UiPath.Callout.Activities | v24.10.5 |
- Neuigkeiten
- New Autopilot™ features
- New Workflow Analyzer rules
- Coded automations features
- Testautomatisierungsfunktionen
- Verbesserungen
- Improved save to the cloud experience
- State machine improvements
- Verbesserter Ausdrucks-Editor
- Coded automations improvements
- Test automation improvements
- Installation und Upgrade
- Weitere Verbesserungen
- Durchschlagende Änderungen
- Fehlerkorrekturen (Bug Fixes)
- Bekannte Probleme (Known Issues)
- Aktivitätspaketversionen