The designer saves the User Task Form Key to activiti:formKey. The engine expects it in: flowable:formKey.
To replicate:
Open a process with a User Task
Set the Form Key
Open the diagram in an XML editor
Inspect the userTask - activiti:formkey will be set to the value not flowable.formKey
tijs
May 29, 2017, 6:36am
2
Hi,
The engine accepts both activiti:formKey as well as flowable:formKey.
Best regards,
Tijs
It actually only accepts the flowable:formKey - that is how I ran into
the issue… activity:formKey was not returned in the API call after we
switched to Flowable.
tijs
May 30, 2017, 7:03am
4
That must be related to another issue, because we do parse both activiti as well as flowable namespace prefixes. Can you share the BPMN XML that wasn’t working for you with the activiti:formKey attribute?
Best regards,
Tijs
Here is what the plugin generates:
<userTask id="conciergeDashboardUserTask" name="Concierge Dashboard " activiti:formKey="concierge-dashboard"></userTask>
This is not returned by the api call:
taskInstance.getFormKey()
Where as if I change the userTask element to:
<userTask id="conciergeDashboardUserTask" name="Concierge Dashboard " xmlns:flowable="http://flowable.org/bpmn" flowable:assignee="$INITIATOR" flowable:formKey="concierge-dashboard"></userTask>
it works but you have to manually set flowable:formKey using an xml editor.
joram
June 6, 2017, 9:52am
6
I tried it here, but can’t reproduce.
What’s the xml namespace configured at the top of the xml file?