I’m seeing issues with regex matching or replacing when using JS-Interpreter. This is on a site with a Content Security Policy that prohibits me simply switching to executeScript. It seems any regex usage that I could come up with, results in the empty {} object being returned. This example below works on RPA 6 and the statement also runs on the online JS-Interpreter demo.
{
"Command": "executeScript_Sandbox",
"Target": "return 'hello'.match(/(.)/)[0];",
"Value": "result",
"Description": ""
}
Alternatively, I see myself running into a lot of issues with the new interpreter since I have some existing scripts that scrape sites that I do not have any control over. I would be interested to know about any best practices that allow for using a more capable interpreter with scripts executing against sites with a CSP.