studio
2023.10
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities packages and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Chrome Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Edge Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- 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
- List of extensions for Edge
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
Studio User Guide
Last updated Nov 4, 2024
Creating a guided product tour
This tutorial demonstrates how to create a guided product tour, as part of the digital adoption attended scenario. This scenario is focused on increasing user productivity, experience, and optimize products in general. This tutorial, in particular, shows how to create a guided tour for the Wikipedia website.
The steps below show an overview on how to build a guided tour for the Wikipedia
website:
- Create a separate workflow for
showing the callouts (show callout.xaml). In this workflow you should
loop through every step and display it inside the callout. To make the tour
experience accurate, configure Advanced Logic on form components.
This way you can, for example, disable the Back button when showing the
first step of the tour.
- Create multiple trigger workflows
for possible user actions inside the callout, such as:
- When user clicks Next (click next.xaml)
- When user clicks Back (click back.xaml)
- When user clicks Skip (click skip.xaml)
- When user clicks Finish (click finish.xaml)
You can achieve this using the Form trigger activity.
- In the Main workflow, show a form that welcomes the user and asks if it's ready to start the tour. You can achieve this by building a Form file, and then displaying it using the Show Form activity (welcome.uiform).
- Create a CSV file that holds all
the UI (user interface) elements and the corresponding steps used inside the
tour. Separate the information in two columns:
- Selector - the
value of the UI element. You can get the value of a UI element using
UI Explorer.
- Message - the message that you want to indicate next to the UI element.
- Selector - the
value of the UI element. You can get the value of a UI element using
UI Explorer.
- Read the CSV file created at step 2 and save it to a global variable. You can achieve this by using the Read CSV activity and the Data Manager panel to create the global variable.
- To display the number of steps left to complete inside each callout, save the number of steps inside a global variable.
- When you open the Wikipedia
website, invoke show.callout.xaml , and run all local triggers in
parallel. This allows you to show the callout for each step, based on the
actions a user takes inside a callout.
Learn how to create this guided product tour, using this sample project as inspiration.
