Rest Step in Flow Designer has unexpected results when compared to making the same call outside the Flow.


Description

When testing a Rest Step you may notice the response body is not showing the expected results when comparing to the response body when sent via a web services client such as Postman.

There may be different data in the body entirely.

Release or Environment

Orlando Patch 7

Cause

This is due to the way the Rest Step is designed to create the request, which breaks down the request into different fields and entires.

There is a "

Often times the query parameters will be added to the resource path as some will use the way they normally would write a request URI in this field.


For example an incorrect Resource Path with query parameters in the path:

/api/now/table?sysparm_limit=10

Example for how the Resource Path should display:

/api/now/table

Resolution

You will need to remove the query parameters from the Resource Path and add it to the Query Parameters field.

The query parameters in the resource path will not be respected.