Hi Steve,
You guessed right, it is all about the fact that the ExecuteWithReturn action is bound to a Process entity whereas the ExeucteProcessWithReturn action is not and as such requires the process to be passed as one of the parameters. This has to do with composability and the resource on which the action is performed is identified by the URL already or not. But instead of me trying to explain it in detail here you can find anything and everything you ever wanted to know about actions and function in the
Protocol specification and
URL conventions of the OData specification.
For existing processes, you'd typically use the bound version (albeit perfectly valid to use the unbound flavor and specify the ID/URL to that process as the first parameter as well). The unbound action however allows you to specify the process to be executed, and additional processes that can be used by such process, inline;-).
Hope that helps!
------------------------------
Hubert Heijkers
------------------------------
Original Message:
Sent: Thu July 01, 2021 11:13 PM
From: STEVE BOROSH
Subject: REST API - re The difference between Process.ExecuteWithReturn and ExecuteProcessWithReturn
I'm looking to understand the difference between
Process.ExecuteWithReturn
IsBound: true
and
ExecuteProcessWithReturn
IsBound: false
The only distinction in the manual is the status of IsBound
What does IsBound mean? Is this a reference to Java IsBound?
Thanks
Steve
------------------------------
STEVE BOROSH
------------------------------
#PlanningAnalyticswithWatson