You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
After flowables removal of its modeler application from version 7.x of its open source edition, we are looking into polybpm for bmpn-modeling. However in three of our projects we make extensive use of dmn-tables which is currently only supported in the new flowable cloud solution. Flowable seems to have some sort of custom dialect which is not playing well with other editors out there.
Describe the solution you'd like
DMN-editor capabilities specifically supporting the flowable dialect.
Started a discussion here: valb3r/flowable-bpmn-intellij-plugin#374
Describe alternatives you've considered
Using the flowable cloud solution (not viable in a security perspective)
Using bpmn.io with a post-export "cleaning hack" since it seems to quote strings in a way thats not accepted by the flowable engine.
Edit the xml-files directly 😱
The text was updated successfully, but these errors were encountered:
Hello @billerby
May I suggest you a zoom call next week to discuss your request in details and how could we cooperate based on PolyBPMN plugin?
Please contact me via email [email protected]
Is your feature request related to a problem? Please describe.
After flowables removal of its modeler application from version 7.x of its open source edition, we are looking into polybpm for bmpn-modeling. However in three of our projects we make extensive use of dmn-tables which is currently only supported in the new flowable cloud solution. Flowable seems to have some sort of custom dialect which is not playing well with other editors out there.
Describe the solution you'd like
DMN-editor capabilities specifically supporting the flowable dialect.
Started a discussion here: valb3r/flowable-bpmn-intellij-plugin#374
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: