AnsweredAssumed Answered

Best way to make variables of processes configurable

Question asked by thilka on Oct 24, 2012
Latest reply on Oct 29, 2012 by thilka

we use Activiti in our Product and we want to be able to declare properties in the process definition which can later be changed by the admin user using our UI.
Example: We have a simple process:

start  ->  Do something (Service Task) ->  Do something else (Service Task) ->  end

We want to be able to configure the property (what to do) on the process basis and reference the value in the Service tasks.
One solution would be to pass the variable as parameter when starting the process and reference it using ${what_to_do}. This would work, but the administrator deploying the process has no idea which properties are "mandatory" for this process. So we want to have some kind of definition on a process basis (which properties should be set), read out the information from the process definition when deploying the process, and then ask the admin user to set the "mandatory" properties.

I tried to use ioSpecification/dataInput, but it is not meant to be used like this, I guess. Then I tried to use <property …> but it seems that Activiti does not read out this value from the XML.
What can we do? We do not want to extend the schema. Is there a way to make it work using the default BPMN / Activiti features?