Salesforce controls

This chapter lists the control types you use to steer your Salesforce application, and provides information on special parameters and values to steer and uniquely identify Salesforce controls.

To steer your Salesforce application, you use two types of controls:

Standard Engines 3.0 controls for steering Salesforce

You can use the following Engine 3.0 standard controls for steering your Salesforce application:

Salesforce-specific controls

You can steer the following Salesforce-specific controls:

Additionally, you can find guides and best practices for special Salesforce use cases:

Identify Salesforce-specific controls

When you scan your Salesforce application with Tosca XScan, by default, all Salesforce controls are uniquely identified by the AssociatedLabel and Visible properties.

The Container property is available in the Identify by Properties window of Tosca XScan Advanced View for all Salesforce controls with the default value of Main.

The Container property has special values for specific controls. In these cases, the Container property is used for uniqueness identification:

  • Controls located in Related lists have the name of the Related list as the Container property value.

  • Controls located on panels have the following Container property value based on the panel type:

    • Controls in Highlight panels: Highlight

    • Controls in Key Fields: KeyField

    • Controls in Cards: the name of the card

  • The links in the App Launcher All Items drop-down menu have the AppLauncher Container property value.

Steer unique controls

In Salesforce Lightning Experience, it is possible to have more than one editors (Inline edit and New/Edit options) open at the same time.

When you steer or scan your Salesforce application, make sure to have only one editor open. This way, you ensure that controls are unique and steerable.