flowable
Form key not working, probably due to erroneous 'activiti' namespace
A form key set in the properties of a start event or user task in the Eclipse modeler does not trigger the form to be presented. Inversely, a form key set in the Modeler App does work, but does not show in the properties view when the model is viewed in the Eclipse modeler.
Looking at the XML, the likely cause is that the Eclipse modeler (incorrectly) places the formKey attribute in the activity namespace, defined as xmlns:activiti="http://activiti.org/bpmn":
<startEvent id="startevent1" name="Start" activiti:formKey="startForm"></startEvent>
whereas the Modeler App puts it in the flowable namespace which is defined as xmlns:flowable="http://flowable.org/bpmn":
<startEvent id="startevent1" name="Start" flowable:formKey="startForm"></startEvent>
The namespace difference is not causing the issue, both are supported. The likely problem is that the process definition is not deployed as an app, but in a separate deployment. Currently the forms are resolved within the same app deployment.
Hi Tijs, I'll try sticking it in an App and see. Note however that a BPMN exported from the Modeler App when read in the Eclipse modeler doesn't show (at least) the form key, the async attribute, execution listeners, and service task classes. These are all typical flowable:* attributes.
Hi, same problem here. I'm loosing all flowable:* attributes when saving from eclipse flowable designer plugin. This is really annoying. Any workaround to fix this? Thanks!
I've switched to the Modeler App altogether. Doesn't have all features, but has all I need hitherto.
Sent from ProtonMail mobile
-------- Original Message -------- On 24 Oct 2017, 12:30, christiantb wrote:
Hi, same problem here. I'm loosing all flowable:* attributes when saving from eclipse flowable designer plugin. This is really annoying. Any workaround to fix this? Thanks!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
