REST API - Initiating a workflow with attributes (string and numeric)

HFCDev · 2025-04-02T21:27:51+00:00

There was an error rendering this rich post.

HFCDev

Hi,

I believe I have WF init via the REST API working, except for setting attributes.

I start the process with a call to get a draft process. That is, a POST of

http://{{cshost}}/{{cshosturi}}/api/v2/draftprocesses

Then I call the draft process again using a PUT:

http://{{cshost}}/{{cshosturi}}/api/v2/draftprocesses/{{draftprocid}}

With the put, I put all my JSON into a body tag (I can't believe we still have to do that). It looks like this:

{"action" : "formUpdate",

"comment":"Testing",

"values": {"WorkflowForm_Title":"Remotely executed WF",

"WorkflowForm_2":"2025-04-02 16:00:00.000", "WorkflowForm_3":"37",

"WorkflowForm_4":"Exception",

"WorkflowForm_5":"21519"}}

Then I can initiate it with another call to the same URL as a PUT with payload

{"action":"Initiate","comment":"WF Remotely started"}

My problem is that on step 2, it returns OK, but in fact, there was an error with one of the attributes so it didn't submit any. WorkflowFOrm_3 is an integer attribute but in CSIDE, it is still being explicitly cast to String, even wrapped in quotes. Str.StringToInteger(37) works, Str.StringToInteger('37') doesn't.

Anyone know how you pass explicitly integer (or date, or user) fields in the draft process payload?

-Hugh Ferguson

Find more posts tagged with

Content Server

Comments

appuq

@HFCDev

The best avenue is to do the same workflow in smartui and observe the payload. If smartui does it correctly then steal that for your rest api I had created a sample in my blog doing that, and with postman screencaps

HFCDev

And that is exactly what I did! I launched a similar workflow that had an integer attribute. I know in earlier versions it was saving the attribute to the draft process each time, but later versions seem to do one big submit. But according to Fiddler, Smart UI does the steps I outlined above. THe main thing is when you are constructing your url-encoded form for key named body, you don't put any quotes around the value you send in your PUT request. The body looks like this for example to update a string field with ID 2 and integer attribute with ID 3:

body={"action":"formUpdate","values":{"WorkflowForm_2":"Someting","WorkflowForm_3":123}}

-Hugh