The Add dialog is a pop-up list picker, and the standard ATF steps cannot reliably set its filter or select rows in it. Community answers confirm that ATF can click the Add button but cannot choose records in that pop-up. They suggest linking the records directly through the data instead.
To build it in the test:
- Add a Record Query step on the restaurant case table for the record with State is Closed, and a second one for State is In Progress. Use your record producer’s submitted records, or a filter specific to this test run, so each query returns the right one.
- Pass the sys_ids to the next steps. Step outputs can be passed from one step to another, as the Add steps documentation describes.
- If the related list works through a reference field, such as a problem field on the restaurant case, use a Record Update step on each case to set that field to the problem created by your UI action step.
- If the related list works through a many-to-many table, use two Record Insert steps to create the links, as community answers suggest for similar lists.
- Finish with a Record Query or validation step that checks both cases are now linked to the problem.
The list steps under Lists and Related Lists can apply a filter and click list UI actions, but community answers say they do not work consistently inside the pop-up. Component steps (custom UI) are another option, but one reply says you cannot select specific records and only add all. A custom step that scripts the pop-up is possible but fragile.
The documentation also notes ATF supports Core UI forms and lists, with support for Next Experience pages still limited. If your related list is in a workspace, that adds to the difficulty. Test the Add pop-up itself manually once, and use the direct-link steps for automated runs.
Sources:
