Enforce transition names?

[heiko.braun]

I've realized that Transition.getName() can be null. Even though the designer creates transition names, manually created process definitions may not contain transition names.

The only case where you can signal without a transition name is activities w. a single out transition. Shouldn't the names be enforced? Or at least be created by the engine at deploy time, when no names a re provided?

[tom.baeyens]

names should not be enforced.

users should only be forced to specify transition names if it has a meaning/purpose for the user.

even in case of multiple outgoing transitions, names should not be enforced. e.g. in case of a fork, we don't want to force process modellers to name all the outgoing transitions.

[heiko.braun]

How do I signal when the transition doesn't have a name?

[tom.baeyens]

signal without parameter signalExecutionById(String executionId) or signalExecutionById(executionId, (String)null)

[kukeltje]

users should only be forced to specify transition names if it has a meaning/purpose for the user.

When is that? For me in almost any case. Certainly in decisions (at least without guarded transitions, but that is impossible in xsd's) but also in tasknodes, so for me it is better to enforce it always. Forks in my experience were limited to 4 legs so it is not a real problem. Besides that it is very easily enforced in an xsd.