19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration
Key Takeaways
Assistant shows automations, favorites on the Launchpad, and tabs for Reminders, Marketplace, Autopilot, and Tasks.
Reminders notify users to start attended automations; the user starts, snoozes (10 minutes), or dismisses them.
The details panel lets users set input arguments and connections before running an automation.
Widgets are deployed through Automation Ops policies from the Official feed or the Orchestrator library feed.
The Marketplace widget installs automations into the user's Personal Workspace.
19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration
Core Concept: UiPath Assistant is the desktop client through which people run attended automations. The exam description lists Assistant widgets, configuration, Marketplace, and schedules (reminders). Developers need to know what users see and how administrators control it.
The Assistant Interface
| Area | What it offers |
|---|---|
| Automations tab | All automations from the folders the robot belongs to (or from %ProgramData%\UiPath\Packages in offline mode), apps from UiPath Apps, and Studio Web templates. Users can update automations, add them to favorites, and pause, resume, or stop running processes |
| Launchpad | The right panel with favorite automations, and the details of the selected automation |
| Reminders tab | Scheduled notifications to start automations |
| Marketplace tab | Ready-made automations from UiPath Marketplace (the Marketplace widget) |
| Autopilot tab | The Autopilot for everyone chat, shown when Autopilot for everyone is installed in the tenant |
| Tasks tab | Action Center tasks assigned to the user |
The Pause button can be disabled for a process in Studio's process settings. A running process can show custom progress messages with the Report Status activity.
Reminders: Scheduling Attended Automations
Attended robots do not use Orchestrator time triggers, so Assistant offers reminders:
- A reminder sets a time or recurring period at which the user is notified to start an automation.
- Automations with reminders are listed on the Reminders tab.
- A notification appears just before the automation is due. The user's approval is required to start it: they can start it, snooze it for 10 minutes, or dismiss it.
Configuring an Automation
Selecting an automation shows its details panel, where the user can configure it before running:
- Inputs: values for the automation's input arguments, with mandatory fields marked by an asterisk. Automations without input arguments have no Inputs section.
- Connections: for automations that use Integration Service connectors, the user can select or create the connections they need; Assistant also offers a Connections area and can open connection management in the browser.
Designing attended automations with clear, typed input arguments and descriptions makes this panel self-explanatory for users.
Widgets
Widgets extend Assistant with extra tabs:
- Deployment is governed by Automation Ops policies for Assistant.
- Widgets come from the Official feed or from the tenant's Orchestrator library feed, where custom widgets are uploaded as packages.
- The Apps and Marketplace widgets are examples of UiPath-provided widgets.
The Marketplace widget
- Lets users browse ready-to-go automations published on UiPath Marketplace.
- Selecting Install adds the automation to the user's Personal Workspace in Orchestrator, so the Personal Workspace must be enabled for the user.
- Offline users can browse but must sign in to install.
- When an automation is installed, Install changes to View, and Update appears when a new version is published.
- Configurable parameters of installed automations can be edited in the details panel.
Governance with Automation Ops Policies
Administrators use Assistant policies in Automation Ops to control, for example:
- which widgets are deployed,
- which features and settings users can change,
- and default behaviors such as startup options.
Policies apply per user or group, so different teams can get different Assistant setups.
Robot Session (Picture in Picture) from Assistant
Processes can run in a Robot session (previously Picture in Picture) so that the automation works in an isolated session or desktop while the user keeps working. Whether a process starts there by default depends on the PiP options set in Studio's Project Settings; the next section covers the details.
Designing Attended Automations for Assistant
- Name and describe the process clearly; users pick it from a list.
- Use input arguments with clear names, types, and defaults so the Inputs panel is easy to fill in.
- Report progress with Report Status during long steps, and decide in Studio whether users may pause the process.
- Plan connections: if the automation uses Integration Service connectors, tell users which connection to select or create.
- Decide on PiP: test the process in a Robot session and set the PiP options before publishing.
Worked Example: A Month-End Helper
An accounts team uses three attended automations:
- Download statements runs every last working day. Each accountant sets a monthly reminder, and approves the run when the notification appears.
- Reconcile account asks for an account number and period in its Inputs and uses the user's Outlook connection to email the result.
- Post adjustments runs in a Robot session, so the accountant can keep working in Excel while it types into the ERP.
The team lead adds a custom widget with month-end instructions through an Automation Ops policy.
Common Traps
- Reminders notify; they do not start attended automations without the user's approval.
- The Marketplace widget installs into the Personal Workspace.
- Widgets are deployed through Automation Ops policies, not by copying files to user machines.
A user sets a reminder for an attended automation. What happens at the scheduled time?
The automation starts automatically without notice.
Orchestrator creates a time trigger for the user.
The automation is added to a queue.
A notification appears, and the user can start the automation, snooze it for 10 minutes, or dismiss it.
Where does the Marketplace widget install an automation that a user selects?
In the user's Personal Workspace in Orchestrator.
In the tenant's Shared folder.
Only on the local disk, without Orchestrator.
In Automation Hub.
How are Assistant widgets deployed to users?
By copying DLL files to each machine.
Through Automation Ops policies, with widgets from the Official feed or the Orchestrator library feed.
By publishing them as processes to each folder.
Through Studio project settings.
Sections you finish are checked off in the contents.