Unexpected behavior calling a suspended process as a called activity

Description

According to the activiti user guide "When a process definition is suspended, new process instance can�t be created (an exception will be thrown).". We find, however, that a suspended process definition, when referenced in a call-activiti (as an external sub-process) WILL indeed be instantiated, and will run to completion.
Checking in the Activiti code we see that the check for ProcessDefinition.isSuspended is made in StartProcessInstanceCmd when processes are initiated - and indeed an exception is thrown, but when createSubprocessInstance is called in CallActivityBehaviour, no such check is made, which explains what we see. (Nor does a check seem to be made in StartProcessInstanceByMessageCmd but that's not at issue).

Environment

None

Assignee

Tijs Rademakers

Reporter

Greg Harley

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure