UiPath Studio

The UiPath Studio Guide

Support for Salesforce Lightning Interface

When automating the Salesforce Lighting interface, the out-of-the-box generated selectors contain specific Lightning attributes that are stable and will not change over time, thus making them very reliable and resilient to UI changes. This means the UIAutomation Activities Pack is a great choice for automating this environment. The attributes are sfl-path, sfl-name and sfl-type.



Any UiPath.UIAutomation.Activities package can be used to automate Salesforce Classic and Lightning UI interfaces through the generic UiPath browser automation support.

UiPath.UIAutomation.Activities v21.10 or above is required to create automation projects for Salesforce Lightning interface by using the specific attributes described below.

Using sfl-path

Most elements in Salesforce Lightning can be identified by using the sfl-path attribute. You can find several examples below:

A selector identifying a search input field; the selector contains the sfl-path attribute determining the precise path of the element:


A selector identifying an icon:


Using sfl-name and sfl-type

In some cases, however, the sfl-path attribute might not be enough to precisely identify the element you are trying to automate. In these cases, the sfl-name and sfl-type attributes are exposed in UIExplorer and can be included in the selector as needed:


Using Standard HTML Attributes

If the Salesforce Lightning specific attributes are not required and standard HTML attributes are enough for uniquely identifying an element on a page, the selector is generated with the standard <html> strategy and may look like this:


Updated about a year ago

Support for Salesforce Lightning Interface

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.