When a task needs current information, DataMind Oda searches the web, reads the pages it finds and answers from them, naming the pages it used. This page covers how that works and where the search comes from.
Search and page reading are two sides of the same web access, and each side can use a different service. Which services are used is decided in your company's deployment: it can pick the service for each side, and when a choice is left open and exactly one service is available, Oda uses it automatically. Oda itself has no web search setting, and Built-in plugins covers why the card is missing.
When a task needs current information. Oda searches, opens the pages that look useful and answers from what it read; you can also ask it to search, or give it the address of a page.
From the search service your company's deployment uses. Search and page reading are two sides of the same web access, and each side can use a different service; when a choice is left open and exactly one service is available, Oda uses it automatically.
Through your company's DataMind server, like every call the app makes (Account, data and updates). The search itself reaches further: web searches go to services outside DataMind, and your search text is sent with the request. A page Oda reads is retrieved on the server's side, not by Oda on your computer.
No. A search or a page read does not stop for a confirmation, and the chat's access mode and approvals do not cover them; those govern what Oda may do on this computer.
Yes. Say so in your message for a single task, or run the chat on a preset with Web search and pages switched off (Create a custom preset); a chat on that preset cannot search or read pages.
Page reading reports what the page answered, and an error status is still an answer. A page that was not found, or that refused the request, stays a result rather than failing the step, and its card shows the status that came back.
Page text is read up to a limit set for the deployment. When a page is longer, the text is cut short, and the step says so on its card (Step cards in chat shows the exact wording).
Up to eight by default, and the deployment can set a different bound. When the search service returned more, the list is cut to the bound and the card marks the cut.
Not from Oda: there is no web search card in its settings, and Built-in plugins covers why the card is missing. The service for each side is set in your company's deployment.
The search ends with no results and says so; nothing is broken. Ask again with different words, or give Oda the address of a page to read instead. A step that fails rather than finding nothing reports a message, and Troubleshooting collects the web search and page reading messages.