search

flowable / flowable-designer

93 stars 62 forks source link

ServiceTask extensionElements are removed at Process Definition edit #17

Open remibantos opened 4 years ago

remibantos commented 4 years ago

Describe the bug When a process definition file having an extensionElements element within a serviceTask element is edited, extensionElements are removed from the XML. For example, when you edit a Process Definition with a serviceTask having a failedJobRetryTimeCycle setting like bellow:

<serviceTask id="test" name="Test" flowable:async="true" flowable:expression="${someBean}"> <extensionElements><flowable:failedJobRetryTimeCycle>R60/PT1M</flowable:failedJobRetryTimeCycle></extensionElements> </serviceTask>

The corresponding xml file will just contain the following:

<serviceTask id="test" name="Test" flowable:async="true" flowable:expression="${someBean}"></serviceTask>

Expected behavior extensionElements should not be dropped from process definition as this is an official Flowable feature. See documentation here: https://flowable.org/docs/userguide/index.html#failRetry

remibantos commented 4 years ago

Note that, since Flowable 6.5.0 & #2009 PR, Flowable Modeler (not this designer) allows to edit and preserves existing failedJobRetryTimeCycle values configured within asynchronous service tasks.

sagar-kalburgi-ripcord commented 1 year ago

@remibantos What is Flowable modeler? I use Flowable design to design workflows and I did not see an option to specify failedJobRetryTimeCycle on Flowable design.

remibantos commented 1 year ago

@remibantos What is Flowable modeler? I use Flowable design to design workflows and I did not see an option to specify failedJobRetryTimeCycle on Flowable design.

It is the Flowable webapp on which you can build/ design business processes too.