[
https://issues.apache.org/jira/browse/SYNCOPE-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076146#comment-18076146
]
Oleg Zimakov edited comment on SYNCOPE-1718 at 4/25/26 5:49 AM:
----------------------------------------------------------------
As I understand it, the Flowable engine works for now. The problem is modeler
is pinned to 6.8.1 (Angular 1) and depends on the flowable-leftovers fork for
JSON conversion — both are maintenance liabilities. I see no good OSS
alternative for the bpmn editor that can replace the outdated Flowable one.
Alternatively, since OOTB Syncope workflows use only ~6 BPMN node types
(service/user/script tasks, exclusive gateways, start/end events) with no
advanced constructs, I'd like to propose replacing it with a purpose-built
editor using maxGraph (Apache 2.0, draw.io lineage) that covers exactly
Syncope's dialect — with a validation gate that detects unsupported BPMN
constructs and falls back to the existing XML editor (in case users already
have a complicated workflow).
I can prototype this if there's interest.
was (Author: JIRAUSER313063):
As I understand it, the Flowable engine works for now. The problem is modeler
is pinned to 6.8.1 (Angular 1) and depends on the flowable-leftovers fork for
JSON conversion — both are maintenance liabilities. Since OOTB Syncope
workflows use only ~6 BPMN node types (service/user/script tasks, exclusive
gateways, start/end events) with no advanced constructs, I'd like to propose
replacing it with a purpose-built editor using maxGraph (Apache 2.0, draw.io
lineage) that covers exactly Syncope's dialect — with a validation gate that
detects unsupported BPMN constructs and falls back to the existing XML editor
(in case users already have a complicated workflow).
I can prototype this if there's interest.
> Consider Flowable replacement
> -----------------------------
>
> Key: SYNCOPE-1718
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1718
> Project: Syncope
> Issue Type: Task
> Components: console, core
> Affects Versions: 4.0.0-M0
> Reporter: Francesco Chicchiriccò
> Priority: Major
> Labels: flowable
> Fix For: 5.0.0
>
>
> As [recently reported in Flowable
> forum|https://forum.flowable.org/t/module-flowable-json-converter-and-flowable-ui-modeler-frontend-missing-in-7-0-0-m1/10061]
> at least two important modules, currently used for Console support, e.g.
> JSON Converter and UI Modeler, were not included into their next major
> release 7.0.0.
> Alternatives considered:
> * [Activiti|https://www.activiti.org/] (adopted in the past and later
> discarded in favor of Flowable); changing the user workflow adapter
> implementation is straightforward, but forms (for user requests) and web
> editor are barely not any more available from the open source releases.
> * [Operaton|https://operaton.org/], a.k.a. "the fork of the fork" (since it
> comes from Camunda which originally came from Activiti); while it seems a
> real open source project with its community, forms will need to be mostly
> re-implemented and likely not covering all use cases currently implemented.
> * [Apache Kie|https://kie.apache.org/] e.g. jBPM / Drools now at The ASF;
> after [reaching out to their users mailing
> list|https://lists.apache.org/thread/r4nn7gbfsm2zpgl4ybd8qcxj4djdfx45] it
> seems that a few key items are missing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
