Anyone free to help troubleshoot this weird syntax issue i’m hitting with GetRESTProxy() in a CXone Studio snippet.
The error pops up immediately during the validation phase:
Error: INVALID_FUNCTION
Details: Function 'GetRESTProxy' is not recognized or arguments are malformed.
i’ve been using this pattern for a while to call our internal rest api from within the interaction flow, but suddenly it’s breaking on a fresh snippet. my current code looks like this:
ASSIGN restProxy = GetRESTProxy("https://my-api.example.com/v1/data", "GET", {}, {})
i’ve double checked the docs and it says the signature should be GetRESTProxy(url, method, headers, body). the url is a string, method is a string, and the empty objects {} represent headers and body.
what’s confusing is that this exact same logic works fine in a different skill’s flow, but here it throws INVALID_FUNCTION. i’m running this on CXone Studio v2.0 (or whatever the latest build is since they don’t really version the ui clearly).
is there a specific namespace or import needed? or maybe the empty object syntax {} isn’t being parsed correctly by the engine? i tried using null instead but that just gave me a NULL_REFERENCE error later in the flow when i tried to read the response.
here’s the full snippet context:
// Step 1: Initialize Proxy
ASSIGN restProxy = GetRESTProxy("https://my-api.example.com/v1/data", "GET", {}, {})
// Step 2: Execute
ASSIGN response = restProxy.Execute()
// Step 3: Check Status
IF response.StatusCode == 200
ASSIGN data = response.Body
ELSE
ASSIGN error = response.Error
END IF
any idea why the parser is rejecting GetRESTProxy? i’ve restarted the browser, cleared cache, nothing. feels like a platform bug but maybe i’m missing a subtle syntax change. thanks.