Skip to main content

I am having troubling setting up a http connector to pass a variable to my system flow. It is not working for me with either Thinkwise or insomnia. I made a system flow to make a certain process a true background process which is called by starting a system task to http connector in a process flow, that in turn starts the background system flow, this is all working fine. The only trouble I am having is I am a bit lost when it comes to setup the variable handoff from the process flow to the system flow. I have tried sending the content with and without wrappers (although insomnia give error 500 with the wrappers, 204 without). I have enabled deeplinking for the variable in the system flow. I am at my wits end.

 

I am using a task in the first process flow to fill the parameter: api_content_input ( i am filling with just 1 employee_id) then sending it to the http connector. Then in the system flow i am trying in the first process to pick up the api_content_input variable fill @employee_id with the content. But no luck so far. Any ideas? Tnx in advance

 

Hello Guido,

It is only possible to set values for process variables in the request body if the process flow allows deep linking:

 

Furthermore, you can only set the process variables that are available in deep linking:

 

Once configured properly, the variables can be set in the request body by means of a json object:

{
   "my_process_variable": "my_value"
}

I hope this helps.

Hello Guido,

Are you using the Windows/Web GUI to trigger the process flow or are you exclusively using the Universal GUI? Because if this only needs to work in the Universal GUI, then this is not the most optimal way to achieve your goal, it can be simplified a lot.

My colleague just helped me solve this problem. Everything was actually working perfectly, except where i misunderstood the process. I am outputting api_content_input and filling that with an employee_id. What i expected was that i had to manually fill @employee_id at the start of the system flow, but the only thing this did was emptying @employee_id. By removing set @employee_id, i could see that the api was doing exactly what it should, filling @employee_id with an id from the http_connector. Thank you for helping!

Terms & ConditionsCookie settings