Support ad-hoc sub-processes

[nikku]

Is your feature request related to a problem? Please describe.

I'd like to be able to educate others about how ad-hoc sub-processes work, and would love token simulation to support me. Today, token simulation does not appropriately handle ad-hoc sub-processes, but instead executes them like normal sub-processes:

Describe the solution you'd like

• Be able to specify activities that should activate in an ad-hoc sub-process

• Token simulation accounts for / executes these activities

• ➡️ This way folks can learn about ad-hoc execution semantics, without diving too much into detail of different implementations (Camunda, ...)

• ❓ At any time you can decide to complete the ad-hoc sub-process (?)

• ❓ Does ad-hoc sub-process allow automatic execution / cancelRemainingActivities?

Describe alternatives you've considered

None.

Additional context

Related to this message

[barmac]

The way I imagine this to work is via human interaction:

• As a token simulation user, I decide which activities should run when ad-hoc subprocess is activated.
• As a token simulation user, I decide when the ad-hoc subprocess is completed.
• When ad-hoc subprocess is completed, cancelRemainingActivities is used to determine if inner tokens should be terminated.

[nikku]

We'd clearly need a separate state for toggling active elements. Poor mans sketch: