Hi Izac,
What's not working? What's the response you get?
What might be confusing is the documentation states that the Execute action, when used with Chore, there isn't a payload (read: n/a) which, technically isn't true, but the server excepts an empty payload to mean and empty, JSON, object (read: {}) as in, there are no parameters. If your process has parameters, most notably required once, then you'll have to put those into the payload that you pass to the Execute action. If none of the parameters are required (you specified default values for all of them) then just passing {} might be enough.
BTW Ted's suggestion to use ExecuteWithReturn, for processes, is indeed the preferable way to execute processes.
------------------------------
Hubert Heijkers
------------------------------
Original Message:
Sent: Mon May 18, 2020 04:39 PM
From: Izac Horne
Subject: Execute Process With REST
/api/v1/Processes('RESTProcessCall')/tm1.Execute
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_rest_api.2.0.0.doc/t_tm1_rest_api_chores.html
The syntax is the same as chore which is listed in the docs but it does not work, if I remove the tm1.Execute it retrieves the process.
Thanks
Izac
------------------------------
Izac Horne
------------------------------
#PlanningAnalyticswithWatson
#PlanningAnalytics
#processes
#REST