[RHPAM-4915] Allow to configure default abort parent behaviour

[albfan]

Behaviour after RHPAM 7.5 was modified. Any aborted subprocess will abort its parent.

This property allows to get the old behaviour so migrations from versions previous to RHPAM 7.5 behaves the same in recent RHPAM versions

[mareknovotny]

ok to test

[mareknovotny]

jenkins do fdb

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
66.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mareknovotny]

jenkins do fdb

[albfan]

@elguardian can you add a review here?

Just to explain the scenario. A subprocess calling a Rest WIH (in sync thread of start node) where the external rest service is down, will abort the subprocess and abort the parent if "abort parent is set".

As I show different behaviour on this for RHPAM 7.3 with RHPAM 7.13.2, so comparing

jbpm-flow/src/main/java/org/jbpm/workflow/instance/node/SubProcessNodeInstance.java

this could be the relevant change:

50a61c9018#diff-c08f01bff8c2ced14acdfbcbe934979871b5ee6edb08e7f59de7f4f4ed073566L228-R237

we are now handling the error on start of process too:

https://issues.redhat.com/browse/RHPAM-2782

Since RHPAM 7.7.1 I think, so before that change any error starting a subprocess is not handled and just goes up

"abort parent" unset just has same effect, ignore and send the exception up

For migrations before 7.7.1, this change might be allow easier migrations, while users are aware they need to modify their subprocess calls

[elguardian]

@albfan it does not have the same effect as boundary events will stop working more likely. I would suggest to create some sort of flag... legacybehaviour
50a61c9018#diff-c08f01bff8c2ced14acdfbcbe934979871b5ee6edb08e7f59de7f4f4ed073566R232 and do the check in there.

[albfan]

Will test a bit and let you know