According to the Inline Variable documentation the inline variables should support any field that uses a string as an input. Does does the URL field for HTTP Request act definitely, because I’m seeing some strange functionality.
But looking at the Test Workflow output - no replacement was made, and no suppliedInlineExpression in the step output. The step input shows: "url": "https://[TENANTHERE].api.identitynow.com/v3/accounts/{{$.getAccounts.accounts[?(@.sourceName=='Active Directory')].id}}/reload"
Using the following URL was successful in its replacement, though. And the suppliedInlineExpression was successfully evaluated.
This successfully grabbed the ID I was looking for (of course failed the HTTP request step because it’s not a valid URL). So it seems to me that the URL is encoding or escaping before the inline variable is evaluated, which might be causing issues. Or does inline variable substitution not support the full Goessner JSONPath features?
That looks like a bug. It appears that inline variable currently only supports simple JSONpath expressions. Using a filter in the JSONpath doesn’t appear to resolve. If you haven’t already, can you please submit a support ticket describing this issue?
I am also looking out for the same thing, would love to see inline variable, with complex expressions like filters, working inside clear text fields like Request URL within HTTP Request action.
Engineering has informed me that currently the url for HTTP is not supported, however they are in progress to have that updated. I will link the tickets for your CSM to follow and go ahead and archive this.
Is there any update on this issue? We have a requirement to pass an identity variable in the request URL and this would be a common requirement for many APIs I would think.
