Summary: Some applications check whether an action was completed by a real user using the isTrusted property. Synthetic users don't pass this check out of the box, so we need to update the script to change this.
Resolution
With the snippet below, Browser Clickpath Monitors can click and enter keystrokes in applications that require the events to be trusted.
- Trusted events impact only Click and Keystroke steps; no other steps' behavior is impacted by the flag, including JavaScript steps.
- The trusted Click step has the following limitations:
the click may not work when- An element is behind another element (overlay) on a page
- An element is inside an iframe
- An element is outside of visible part of the webpage.
Supported Versions
This feature was added:
- For Clicks, from 1.266 (1.266 Recorder, 1.266 Public Locations, 1.267 Synthetic-enabled ActiveGates).
- For Keystrokes, from 1.269 (1.269 Recorder, 1.269 Public Locations, 1.269 Synthetic-enabled ActiveGates)
How to enable interacting with trusted events in a Browser Clickpath monitor
Add the following to the configuration section of the script to enable Trusted Events feature
,"experimentalProperties": [
{
"name": "enableTrustedEvents",
"value": "true"
}
]
No further changes are required to the monitor. Now all click and keystroke events in the script will be considered trusted.
What's Next
If this does not resolve the issue, please open a support ticket and provide
- a link to the affected monitor
- mention this article and any other troubleshooting steps taken
What to read next:
