Workspace ATF: can not view the options in the drop down

[PatriciaLC]

Hello, 

I am currently trying to create an ATF workflow that closes a record in workspace view. Everything works except when I use the step 'Click Component (Custom UI)' and click on the 'Reason' field drop down to view the options, I am not seeing any values. It says 'No results found'. The purpose of this step is to select a reason for closure (i.e. cancelled or fixed).  This was not the case when I created the test in Yokohama environment. It worked then, but it's not working in the Zurich environment. Please help. See attached screen shots.   

[pr8172510]

Hi PatriciaLC,

Good question — this is a known behavior difference when working with ATF in Workspace (UI Builder / Now Experience)

---

1. Why “No results found” is happening

In Workspace, fields like Reason (choice/reference) are not always loaded like classic UI.

In ATF:

• The step “Click Component (Custom UI)” only clicks the dropdown
• It does NOT guarantee that:
  • Data is fetched
  • Options are populated

That’s why you see “No results found”, even though values exist.

---

2. Key difference (Yokohama vs Zurich)

What worked in Yokohama may fail in Zurich because:

• Workspace components are more dynamic (lazy loading)
• Data is fetched via client-side APIs
• ATF sometimes clicks before data is available

So timing + component behavior is the main issue

---

3. Recommended approach → Don’t rely on dropdown selection

Instead of trying to open and select from dropdown:

 Use “Set Field Values” step (best practice)

• Field: Reason
• Value: (backend value, not label)
  • e.g. fixed or cancelled

This directly sets the value without UI dependency

---

4. Alternative → Add wait before interaction

If you must use UI steps:

• Add:
  • Wait for condition / Wait for element
• Then:
  • Click dropdown

But still:
 Not fully reliable in Workspace ATF

---

5. Check field type (important)

Verify if Reason is:

• Choice field → use value directly
• Reference field → ensure:
  • Records exist
  • Proper query is applied

Sometimes “No results found” is due to:

• Dynamic reference qualifier
• Context not loaded in ATF

[PatriciaLC]

Thank you @pr8172510 . I will consider this!

[Sardash]

@PatriciaLC - Can you try 'Set Component Values (Custom UI)' step instead of 'Click Component (Custom UI) as Workspace components respond better to Set Value than click-based interactions.

---------------------------------------------------------------------------------------------------------------------------------------------------

If my response helped, please mark it by selecting "Accept as Solution" and " Helpful." 

[PatriciaLC]

Hi @Sardash , 

Thank you for your help. I will try this!