I am trying to use velocity to dynamically expand the array as there is no limit for this attribute. I also tried to use velocity playground and the output worked on postman.
1. Retrieve the comma-delimited string from the plan arguments
But when the application gets my request, they are reading the exact string instead of value. I have tried using “{$id} still the same. Appreciate any feedback!
Good point. I tried that as well. Here is my actual JSON Body, error is with rowidObject where its not passing the value to end point. When I use this on developer velocity play ground and use the output on postman, it works fine.
it looks like you are using Smart Quotes rather than straight quotation marks. I don’t know if this matters or not, but wonder if you replace them with ’ " ', rather than ’ “ ', if it would help… But maybe this is just a difference on keyboard layout …
What if you try changing the “$branchid” to ${branchid}. This might help the Velocity engine know where the variable name begins and ends.
I tried “${branchid} , didn’t work. ${branchid} without quotes throwing error stating not a json object. I am thinking if I should use transform script to convert the incoming comma delimited values and provision it part of create plan .
With the data implying a location, does it make sense that the authoritative source handles them as entitlements in the schema? The ISC Identity attribute is single valued, so a regular transform wouldn’t help, from my perspective.
Good point. unfortuantely we can’t handle them as entitlement eventually switching the static value to identity attribute where we get 10 plus codes dynamically , we should be able to dynamically expand the array. Also attribute sync enabled when there are changes in these codes happen in our authoritative source.
Lots of articles pointing to before operations rule, which we are trying to maintain the environment low code as possible.
I have also raised a ticket to support asking best way to handle, looks like the logic is working dynamically expanding the array, its just not passing the values from the csv. Wonder if that is a limitation on the product itself.
low code is nice in theory, but when you are discussing web services, low or no code isn’t realistic. If you can use the VA web services connector your connector rules aren’t too much of a step up once you get into them.