Browse the docs

ui_act

Does one UI step in a session app: click, setValue, readValue, waitFor, typeText, pressKeys, menu or contextMenu.

Details #

step is a macro step exactly as the macro schema has it, so a tool call and a saved step are the same thing. It runs through the engine like any step, with its timeout and failure words, and becomes a row in the session's trace with the locator's score and how it matched. The fence refuses, in words: another app than the session's ("This session is for Slack"); a locator that did not come from find_elements and does not match at 70%; any write while a password field is active; setValue or readValue on a password field; a position click, or allowClick on a contextMenu, unless you approve every act; anything but readValue, waitFor and a contextMenu with no item (which only lists the menu's items) when Direct control is "Looking only". {{ }} expressions are not allowed in a session step.

{ "name": "ui_act", "arguments": { "sessionId": "…", "step": { "type": "click", "params": { "locator": { "role": "AXButton", "title": "Send" } } } } }

Parameters #

Answers with status (ok or failed), out, note, score, via and ms.