Split & Joins - condition feature

[chrisw14]

Hi,
I'm using the Split & Joins plugin and want to ask if it's possible to start a new subprocess with the plugin if and only if a specific condition (a value of a workitem is set) is fulfilled?
Thanks!
Chris

[rsoika]

Yes - you first create a conditional event where you decide the follow up event. One contains the Create-Split instruction, the other one dose nothing.

[chrisw14]

Wouldn't it be nice to introduce a condition-tag in the workflow result?

<item name="subprocess_create">
    <condition>workitem.startSubProcess[0] == true</condition>
    ...
</item>

Because if there are more subprocesses to start there could be lots of combinations to check.

But the nicest way would be to introduce the bpmn element "Sub Process" that you can combine the conditional event with the subprocess element. Why doesn't imixs support that?
Or is it possible to change the icon of the imixs workflow event? Maybe this would be an easier solution.

[rsoika]

The idea with the condition is good. We need to look into this as a new feature.
The bpmn element "Sub Process" does not convince me. It hides more than it makes a model transparent.

[rsoika]

This is how we typically design a process with a sub process:

[rsoika]

This is the corresponding model file:
https://github.com/imixs/imixs-workflow/blob/master/imixs-workflow-core/src/test/resources/bpmn/collaboration_messageflow_complex.bpmn

[rsoika]

[rsoika]

Just to separate things:

• Conditional-Events are just evaluating a rule and did not create a new instance
• Split-Events are creating a new process instance based on the current process instance within the same model

So both events are running in the same model and same model-group

In difference the SplitAndJoinPlugin is used to create a new process instance (named sub process) which can be part of a complete different model. And for that reason we expect a $modelversion, a $processid and a $activityid

<item name="subprocess_create">
    <modelversion>1.0.0</modelversion>
    <processid>100</processid>
    <activityid>10</activityid>
</item>

As we can place such an event after a conditional event we already have a working solution I think?

[rsoika]

It would look like this:

So I think we do not need the condition in a 'subprocess_create' definition ?

[chrisw14]

As we can place such an event after a conditional event we already have a working solution I think?

Yes I thought about that yesterday too and of course this is a good solution too.

Would it be possible in that case to change the icon of the imixs-workflow-event from the yellow circle to a sub process icon?