Steer Related Lists

This chapter explains how to steer the Related Lists of various Salesforce applications.

Related Lists have two kinds of layouts:

• Table layout: available in both Salesforce Classic and Salesforce Lightning Experience.

• Card layout: only available in Salesforce Lightning Experience.

The screenshots below show the same Related List in different layouts and Salesforce interfaces.

When scanned, the Related List card layout produces the following table structure in Tricentis Tosca:

Primary Column	Title	Email	Phone	Action
John Smith	CTO	Jo.Smith@tricentis.com	(002)123-4567	Edit/Delete
Jack Smith	CFO	Jack@mail.com	(002)-1237654	Edit/Delete
Lou Lee		lee.l@test.com	(002)321-4567	Edit/Delete

When scanned, the Related List table layout from Salesforce Lightning Experience produces the following table structure in Tricentis Tosca:

Contact Name	Title	Email	Phone	Action
John Smith	CTO	Jo.Smith@tricentis.com	(002)123-4567	Edit/Delete
Jack Smith	CFO	Jack@mail.com	(002)-1237654	Edit/Delete
Lou Lee		lee.l@test.com	(002)321-4567	Edit/Delete

The Related List table layout from Salesforce Classic produces the following table structure in Tricentis Tosca when scanned:

Action	Contact Name	Title	Email	Phone
Edit/Delete	John Smith	CTO	Jo.Smith@tricentis.com	(002)123-4567
Edit/Delete	Jack Smith	CFO	Jack@mail.com	(002)-1237654
Edit/Delete	Lou Lee		lee.l@test.com	(002)321-4567

Steer Related Lists and embedded controls

Tosca XScan identifies both Related List layouts as tables, so you can steer Related Lists as standard Table controls.

Embedded controls in the table are steered as standard Engine 3.0 controls. For example, you can steer Actions drop-down menus as standard ComboBoxes.

In this example, you select the Edit option from the Actions drop-down menu in the first row of the All Accounts Related List. You select Edit in the Value field for Show ActionsComboBox. You set the ActionMode of Show ActionsComboBox to Input. Steer embedded controls of Related Lists

Compatibility between layouts and Salesforce interfaces

Table layout

The Modules created with the table layout in Salesforce Lightning Experience and the table layout in Salesforce Classic are compatible. Therefore, if you migrate from Salesforce Classic to Salesforce Lightning Experience, you don't need to make manual changes in your Tosca Modules and TestCases.

Tricentis recommends that you identify the table columns by ColumnName instead of ColumnNumber because the order of columns is different in Salesforce Classic and Salesforce Lightning Experience table layouts.

Card layout

The card layout and the table layout differ in column naming. The first column of the card layout is called Primary Column and the last column is called Action.

To maintain the compatibility between card and table layout, use the following values for the first and last column:

• Specify the first column as $1.

• Specify the last column as $last.

In this example, you want to verify the first cell of the first entry in the related list and click on the button in the second row. You want to run your TestCase on both types of related lists. Related list - table Related list - card To do so, you specify the following values in your TestCase: To identify the first column, you use $1. To identify the last column $last. Related list in a TestCase