Which statement best describes a method to make a REST step dynamic as described for Flow Designer?

Which statement best describes a method to make a REST step dynamic as described for Flow Designer?

• A. Use a data pill in the resource path for variable information and a data pill in the query parameter value for described parameters
• B. Hard-code values in both resource path and query parameter
• C. Modify the REST step with a script to alternate values
• D. Use a static payload without dynamic fields

Answer: (A)

Dynamic REST calls in Flow Designer come from binding flow data to the REST step using data pills. By placing a data pill in the resource path you enable parts of the endpoint to be substituted at run time, so the same step can target different resources without rewriting it. Placing a data pill in the query parameter value makes the parameter itself dynamic, allowing the step to pass different values based on earlier steps or inputs in the flow. This combination keeps the REST call flexible and reusable, adapting to varying data without hard-coding endpoints or parameters. For example, if you need to fetch a specific record, you can bind the record id to the path, and if you want to filter results or pass a variable, bind that value to a query parameter. Hard-coding values fixes the step to one resource and one parameter, making it inflexible. Using a script to alternate values adds unnecessary complexity and moves away from the declarative, data-driven approach Flow Designer encourages. A static payload also misses dynamic fields, preventing the step from adapting to different scenarios.

Dynamic REST calls in Flow Designer come from binding flow data to the REST step using data pills. By placing a data pill in the resource path you enable parts of the endpoint to be substituted at run time, so the same step can target different resources without rewriting it. Placing a data pill in the query parameter value makes the parameter itself dynamic, allowing the step to pass different values based on earlier steps or inputs in the flow. This combination keeps the REST call flexible and reusable, adapting to varying data without hard-coding endpoints or parameters.

For example, if you need to fetch a specific record, you can bind the record id to the path, and if you want to filter results or pass a variable, bind that value to a query parameter. Hard-coding values fixes the step to one resource and one parameter, making it inflexible. Using a script to alternate values adds unnecessary complexity and moves away from the declarative, data-driven approach Flow Designer encourages. A static payload also misses dynamic fields, preventing the step from adapting to different scenarios.