Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Form key not working, probably due to erroneous 'activiti' namespace #5

Open
zwets opened this issue Apr 14, 2017 · 5 comments
Open

Comments

@zwets
Copy link

zwets commented Apr 14, 2017

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>
@tijsrademakers
Copy link
Contributor

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.

@zwets
Copy link
Author

zwets commented Apr 14, 2017

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.

@christiantb
Copy link

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!

@zwets
Copy link
Author

zwets commented Oct 25, 2017 via email

@quaff
Copy link

quaff commented Nov 14, 2017

Please replace all "activiti" to "flowable" to keep consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants