Bis the correct answer — in UiPath’sAgent Builder (Studio Web), when you want to invoke an existing UiPath process from an agent (viaTools → Processes), that process must meettwo key prerequisites:
It must be published and deployed to a shared Orchestrator folder
You — and the agent — must have access to that folder
This ensures that:
The agent canlocate and run the processat execution time
Role-based access control (RBAC) is respected
Input/output arguments, execution logs, and exceptions are properly managed within the correct environment
This aligns with UiPath’sOrchestrator-integrated agent orchestration model, where security and deployment visibility are tightly governed. It also allows agent authors toreuse existing RPA logicinside dynamic agent flows without duplicating automation work.
Option A and D incorrectly imply that argument types affect process visibility — that’s false. Agents can invoke processes withany argument signature, as long as mapping is defined.
Option C is incorrect — publishing alone is not enough.Deployment and permissionsare required for the process to appear in the tool selector.
This model ensures that agents can call any compliant UiPath processsecurely, reliably, and in line with enterprise governance.
