Hi Saikiran,

Good question  this is a known tricky scenario when working with ATF and related list popups like “Add Affected CIs”.

A few things you should know and try:

1. Why this is difficult in ATF
The popup you’re seeing (Add Affected CIs) is a list collector / slushbucket-style UI (GlideList / GlideModal).

• It runs in a separate UI frame/modal
• Standard ATF steps don’t always interact well with it
• Multi-select inside this modal is not directly supported via OOB steps

2. Recommended approach → Use “Set Field Values” instead of UI

Instead of automating the UI popup:

 Directly insert/update the related records

For Affected CIs:

• Table: task_ci
• Fields:
  • task → Change Request sys_id
  • ci_item → CI sys_id

In ATF:

• Use “Record Insert” step
• Add multiple records for each CI

This is the most reliable and recommended approach

3. Alternative → Use “Open a List” + “Click a UI Action” (limited)

If you still want UI-based testing:

• Open the CI list directly
• Use “List v3 steps”:
  • Filter list
  • Select checkbox
  • Perform action

But this may not work inside modal consistently.

4. Advanced option → Custom Test Step (GlideModal handling)

If UI validation is mandatory:

• Create a Custom ATF Test Step
• Use client-side script to:
  • Access iframe/modal
  • Select rows programmatically

Example idea:

var frame = document.querySelector('iframe');
var doc = frame.contentDocument;

// find checkboxes and click
doc.querySelectorAll('input[type="checkbox"]')[0].click();

This is fragile and not recommended unless necessary.

5. Best practice (important)

✔ ATF is meant to test logic, not complex UI interactions
✔ Avoid modal/list collector automation where possible
✔ Use backend record validation instead

6. Validation step

After inserting records:

• Add “Assert Record” step
• Verify CIs are linked to Change