Tests start to have a lot of repeting steps, so it is a good idea to make those steps explicit

currently:

• type
• repetition rule

the extension is read when the process starts and is stored in the caseProcessDefinition variable.

om.write value as string does not work well

• camunda 7.11.3-ee
• spring boot 2.1.7
• starter 3.3.4
• orchid 0.17.4

I can mark a task as mandatory and the outer process will not finish before it is completed

I can mark a task as non-repeatable and thus execute it only once.

to ensure formatting across diverent dev machines

The sentry was true, thus the execution has state ENABLED. It was not manually started, so now, when the sentry turns false, it is set to state DISABLED.

We will have multiple, parallel sub process executions, so using one variable on top "processInstance" level will lead to accidential overwrites.

Idea: Start with transient variable and copy to local scope.

Breakthrough: using a statemodel in processvariables and execution listeners on the process and each subprocess, a case execution can be manually started and stopped.

For a task with repetition rule

• complete - the end listener sets the follow up to disabled if the sentry is false

• startManual - since the task can be started, we assume that the follow up task can also be started

just because

A case activity without repetition rule can only be run once.

An event based subprocess via signal will start whenever a signal is received.

Solution idea:

• remove eventSubscription manually

values was introduced for easy access to caseTasks, but it is now part of the json.

Switch to set instead of map

Redirect to runtime service

I just copied the required code, since jgiven-addons is junit5 only, but it's a good idea to enhance the addons and then replace the code with the official extension.

/extension/src/test/kotlin/_test/JGivenKotlin.kt

The definitionId will stay the same for all bpmnCaseExecutions, so it would be a good idea to move it to the CaseTaskDefinition.

This will influence the way the model is parsed because the function will need to have access to the definition (for example by passing the delegateExecution).

https://docs.gradle.org/5.6/userguide/java_testing.html#sec:java_test_fixtures

drop slf4j-simple

(slf4j-simple prints red-on-black on my machine)

I can start another instance of a task anytime I want.

I can start a task again once its predecessor has finished.

instead of requiring a wrap() method, use a factory field

motivation: separation of concerns: the factory might have to hold some dependencies that are only needed to create the wrapped instance, not for the process itself. with the wrap() method, the process is required to hold all those dependencies.

send start command on PostDeployEvent

When a case process is started, the configured cmmn extensions are read and the caseExecutions are created.

Steps:

• Hello Letter
• Telephone Call
• Send Claim Letter

To define a sentry on part condition on a case task subprocess, I want to define an expression as bpmn extension element.

cmmnOnPartExpression = ${mySentryResolver.doSomething(execution)}

I can then run a listener (or delegate) that resolves this expression based on instances registered on camundas expressionManager (Mocks.register, CamundaMockito.registerInstance, later spring/cdi)

request ownership change in jangalinski repo

ManualStart executions are "parked" in DISABLED state when the sentryCondition is false on process start.

If the sentry evaluates false, new executions have state available.

Idea:
use json map caseTaskDefKey to boolean to store state in variables

the sentry was false, so the execution is in state DISABLED.
when the sentry turns true again, the execution is in state ENABLED.

nt