A projection call that requires a Path Parameter (which works fine when tested via Postman) can't be configured the same way in a Workflow's Call/Update task — putting the value into a regular 'Parameter' field instead of a distinct path-parameter field throws an error. How do you actually pass a Path Parameter to a projection from a workflow?

All FAQ questions / Workflows and automation

Answer

Read the entity first (to get its current ETag/state) before the Update call, then in the subsequent Update task, pass both the path parameter values and the regular update parameters together in the same call, rather than trying to configure a separate distinct 'path parameter' input the way Postman's UI exposes one. Workflows don't have a dedicated path-parameter field the way Postman does, but combining everything (path-identifying values plus the actual fields being updated) into the Update task's parameters, after a preceding Read, gets the same result.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions