The list of defects addressed in each release is listed on the release notes for each product. The links to the release notes is from the product install / download page.
Jon Hardy | Nintex® Workflow for Everyone® | Senior Product Manager | Jon.Hardy@nintex.com<mailto:Jon.Hardy@nintex.com> | T: +61 3 9972 2554 | M: +61 437 942 425
The real issue I found is when having curly brackets in a variable mixed in with other references as those also include curly brackets. Somehow, the Nintex Workflow confuses the two and can't parse them.
A slightly simpler solution is to use tokens instead of the curly brackets and then use the Replace Substring in String action to substitute the curly brackets in place of the tokens. So in my solution, I would use lcurl for left curly brackets and rcurl for right curly brackets. The actions would be as follows:
Then, you can use the body variable when needing to use the JSON string.
I am trying to update site title using REST API.
I am getting bad request error or Forbidden error when i try to test the connection in web request action.
Same REST API url is giving me a result if i try through browser. Also I am able to access ASMX service through web request action for same account.
So, Just wanted to know is there any setting required to use REST service in web request action ?
In order for me to get this working, i only had to do a "Build string" action and store the result in a multiline variable ML_body
and after that, i could use ML_body in my web request action, but my headers are a bit different:
The account that you use to perform the request has to have the permission to change the site title.
Another reason that could cause the forbidden error is that the header "X-RequestDigest" hasn't been initialised in the web request or it's value is not correct.