What is the main function of UIPath's autopilot?

UIPath's autopilot helps maintain automation resilience and adaptability despite unforeseen application changes.

How does autopilot handle UI changes in automation processes?

Autopilot automatically finds new selectors when UI changes occur, allowing the automation to continue successfully.

What problem did the autopilot solve in the video example?

In the example, the autopilot fixed issues with UI changes and closed an unexpected pop-up that disrupted the automation process.

Who typically uses the autopilot feature?

Automation developers and administrators use the autopilot feature to manage and maintain automations.

What is one benefit of using autopilot for automation?

Autopilot reduces the need for extensive troubleshooting and automation downtime.

UiPath Automation Healing

00:03:09

https://www.youtube.com/watch?v=1cyO7N8ztts

Summary

TLDRThe video showcases how a global engineering company uses UIPath's autopilot to automate and streamline employee onboarding through multiple applications like Workday, Google, and Kooper. Despite initial success, the automation began failing due to UI changes. Autopilot intervened by automatically adjusting selectors, closing unexpected pop-ups, and allowing the process to continue seamlessly. The insights provided by autopilot are shared with developers, enabling quick fixes without the need for detailed troubleshooting. This function is beneficial for both UI and API scenarios, ensuring automations remain resilient even as applications evolve.

Takeaways

🤖 UIPath's autopilot adapts automation to unforeseen application changes.
📈 Automates employee onboarding using multiple applications successfully.
🔧 Finds new selectors automatically when UI changes happen.
🚫 Closes unexpected pop-ups to maintain automation flow.
🛠 Provides valuable insights for developers to fix issues easily.
🌐 Useful in both UI and API-based scenarios.
📊 Keeps automation programs running smoothly with minimal downtime.

Timeline

00:00:00 - 00:03:09
Autopilot for robots ensures automation resilience amid application changes. A global company uses the UI Path platform for onboarding automation across multiple apps. Despite a process failure due to UI changes, Autopilot adapts, completing tasks successfully by identifying new selectors and handling pop-ups automatically. Developers benefit from Autopilot's insights for effective resolution, enhancing automation in evolving app environments.

Mind Map

Video Q&A

What is the main function of UIPath's autopilot?
UIPath's autopilot helps maintain automation resilience and adaptability despite unforeseen application changes.
How does autopilot handle UI changes in automation processes?
Autopilot automatically finds new selectors when UI changes occur, allowing the automation to continue successfully.
What problem did the autopilot solve in the video example?
In the example, the autopilot fixed issues with UI changes and closed an unexpected pop-up that disrupted the automation process.
Who typically uses the autopilot feature?
Automation developers and administrators use the autopilot feature to manage and maintain automations.
What is one benefit of using autopilot for automation?
Autopilot reduces the need for extensive troubleshooting and automation downtime.

View more video summaries

Get instant access to free YouTube video summaries powered by AI!

Subtitles

Auto Scroll:

00:00:05
[Music]
00:00:18
autopilot for robots includes automation
00:00:21
healing ensuring your automations remain
00:00:24
resilient and adaptable despite
00:00:26
unforeseen application changes a global
00:00:30
engineering company uses the UI path
00:00:32
platform to automate employee on
00:00:35
boarding this UI based automation
00:00:38
involves multiple applications like
00:00:40
workday Google and kooper and is used to
00:00:43
create assert requisitions and assess
00:00:46
requests the process ran successfully
00:00:49
for months but then started
00:00:52
failing as an admin you receive a
00:00:55
notification whenever something goes
00:00:57
wrong in this case it shows UI changes
00:01:01
that caused issues despite this with
00:01:03
autopilot the automation still completed
00:01:07
successfully let's see what went wrong
00:01:10
in orchestrator there is a new autopilot
00:01:13
panel allowing you to quickly understand
00:01:16
what happened and how the problem was
00:01:19
repaired a recording from the automation
00:01:22
execution shows the application UI
00:01:24
changed and the selector identifying the
00:01:27
search field was not found autopilot
00:01:30
automatically found a new selector and
00:01:33
the automation continued
00:01:37
successfully autopilot also closed an
00:01:40
unexpected pop-up window allowing the
00:01:42
automation to continue
00:01:48
uninterrupted with both issues autopilot
00:01:51
collected information from the
00:01:53
application interfaces intelligently
00:01:55
analyzed it and knows the right fixes
00:01:58
these insights are easy shared with the
00:02:00
automation developer who will fix the
00:02:03
problems let's see that in action as a
00:02:06
developer you can see all collected
00:02:08
information in
00:02:10
studio autopilot offers essential
00:02:13
insights to fix the issue without the
00:02:15
need to troubleshoot or debug further
00:02:18
you can see where problems occurred and
00:02:20
understand how they affected the
00:02:22
automation for the selector issue you
00:02:25
accept the autopilot recommendation for
00:02:27
the updated selector and the activity is
00:02:30
fixed for the unexpected popup window
00:02:33
you review and accept the autopilot code
00:02:35
snippet
00:02:39
recommendation there are many other use
00:02:41
cases where autopilot can help in both
00:02:43
UI based and API based scenarios in a
00:02:47
world where applications constantly
00:02:49
evolve and unpredictable UI changes
00:02:51
occur autopilot helps you successfully
00:02:54
drive your automation program reducing
00:02:57
troubleshooting and automation downtime
00:02:59
time
00:03:06
[Music]