I understand the interpreter issue with objects/arrays, but the original example should have been returning a string already, but is for some reason returning the empty object instead. Here is a more obvious example that is clearly returning a string, but still demonstrates the issue:
{
"Name": "test",
"CreationDate": "2022-5-4",
"Commands": [
{
"Command": "executeScript_Sandbox",
"Target": "var t = 'hello'.match(/(.)/)[0]; return 'test';",
"Value": "notWorking",
"Description": "This does not work, value is {} even though a string is clearly returned."
},
{
"Command": "executeScript_Sandbox",
"Target": "var t = 'hello'.replace('he','c'); return 'test';",
"Value": "thisWorks",
"Description": ""
}
]
}
It seems to me that any regex usage breaks what is ultimately returned.
Also, I appreciate the suggestion to open a dummy tab and run my more complex javascript processing there. Though that would be really great if your team could figure out a way for the tool to expose a more capable interpreter without requiring us to manually code the workaround each time it is needed.