Activities

Spec Page	Spec Rule Text	RuleId
150	The value [of the startQuantity attribute of Activity] MUST NOT be less than 1.	BPMNR020
151	The value [of the completionQuantity attribute of Activity] MUST NOT be less than 1.	BPMNR021
190	In order to initialize a valid multi-instance, either the loopCardinality Expression or the loopDataInput MUST be specified	BPMNR022
210	Not every Activity type defines inputs and outputs, only Tasks, CallableElements (Global Tasks and Processes) MAY define their data requirements. Embedded Sub-Processes MUST NOT define Data Inputs and Data Outputs directly, however they MAY define them indirectly via MultiInstanceLoopCharacteristics.	BPMNR023

Spec Page

Spec Rule Text

RuleId

150

The value [of the startQuantity attribute of Activity] MUST NOT be less than 1.

BPMNR020

151

The value [of the completionQuantity attribute of Activity] MUST NOT be less than 1.

BPMNR021

190

In order to initialize a valid multi-instance, either the loopCardinality Expression or the loopDataInput MUST be specified

BPMNR022

210

Not every Activity type defines inputs and outputs, only Tasks, CallableElements (Global Tasks and Processes) MAY define their data requirements. Embedded Sub-Processes MUST NOT define Data Inputs and Data Outputs directly, however they MAY define them indirectly via MultiInstanceLoopCharacteristics.

BPMNR023