Current behavior

SystemAction.PageSearch, the action behind Tell Me (Alt+Q), is on the page scripting deny list, and the list is enforced twice. Once in the recorder and once in the player. Verified by inspecting the web client in BC 28.4.

• Recording. Tell Me interactions are not captured at all. Alt+Q, typing a page name and pressing Enter produce exactly one reproducible step, a navigate to the resulting page.

• Replay. A step that resolves to a denied system action is skipped silently and reported as successful, although nothing was performed.

• Targeting cannot work around this. The block sits on the action path and not on the target, so no automationId or runtimeRef variant helps. Typing into the Tell Me search box does work once the panel is already open, because input is not a session action. But a script cannot open the panel.

Why it matters

Page scripting recordings are made to be handed over. A script can be saved to a file or shared as a link so that someone else can replay it, for example to reproduce a scenario or to walk through how a process is done. When a shared script is replayed, navigation is the part that cannot be followed. A navigate step switches pages instantly and leaves no visible trace on screen, so the person watching has no way to see how the script reached the next page. Everything that happens on a page is visible, and even list search is visible through the search box (filter:system:search). Page to page navigation is the only part that stays invisible. A person doing the same flow by hand opens Tell Me and types the page name, and that step is exactly what makes a walkthrough understandable.

Request

1. Allow PageSearch during replay, so a script can navigate through Tell Me. Recorder support would be nice to have, but replay is what matters. Or

2. Add a player option that visualizes navigation, for example an optional on screen indication while a navigate step runs. And

3. Either way, replaying a step that hits a denied action should produce a warning or a failure instead of silent success. The current silent skip makes scripts falsely green, which is the worst possible outcome for a testing tool.

4. Document the excluded system actions. The page scripting documentation does not mention that any system actions are excluded, so today the only way to find out is to read the client code.