-
Notifications
You must be signed in to change notification settings - Fork 62
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
Comments
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 |
Hi, same problem here. I'm loosing all |
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](#5 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AA6Mffx_0p5-OdNQe3O0U-g6xQuyBou4ks5sva4agaJpZM4M9tAt).
|
Please replace all "activiti" to "flowable" to keep consistency. |
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 asxmlns:activiti="http://activiti.org/bpmn"
:whereas the Modeler App puts it in the
flowable
namespace which is defined asxmlns:flowable="http://flowable.org/bpmn"
:The text was updated successfully, but these errors were encountered: