Selectors and target descriptors are available where the customer’s application is available. That is why capture belongs in a consented session on the SME’s Windows machine, not in a developer-only environment.
#Supported working pattern
- The customer opens the application and representative pages.
- The customer explicitly grants control for the agreed session, or performs the actions while the recorder observes.
- The recorder captures named targets, accessible roles, labels, automation IDs and screenshots where appropriate.
- The developer reviews the captured targets and removes secrets or unnecessary values.
- The resulting target evidence is linked to the specification and used to author the UiPath workflow.
The recorder must not capture passwords, tokens or unrelated windows. A customer can stop the session at any time. Captured target data should be treated as sensitive customer evidence.
#What is not promised
AutoHub cannot reliably discover every selector from “whatever happens to be open” without an application-specific capture step. Modern, dynamic and protected applications still need a human to identify the correct control and test the generated selector.