Passing in workflow variables from JSON API vs Run Process Link

Confluence User - 26 Oct, 2016

When I start a process using the JSON API and pass in Workflow Variables, I can display them in fields on the first Activity form (by defaulting those fields to Hashed Workflow Variables) and can pass those workflow variables into a Custom HTML field (also using Hashed Workflow Variables within the HTML). However, when I start a process using the Run Process Link and pass in Workflow Variables in the query string they still also display in fields on the first Activity form (by defaulting those fields to Hashed Workflow Variables) but those Workflow Variables do not get passed into the same Custom HTML (using Hashed Workflow Variables within the HTML). What is the difference?

forms

1


27 Oct, 2016
confluenceUser
confluenceUser

Hi,

When you call the JSON API, the process is started first before the form is displayed so the variable value is available. However, when you use the Run Process link and pass it in the query string, the process has not started yet hence the variable values are not set yet. This is assuming that in your app you mapped "Run Process" to that form.

RELATED QUESTIONS

Your answer


To answer a question you'll need an account.

Print