MultiPartyCollaboration

More than two roles - Defines the interaction between more than two top-level or abstract partner roles. Binary Collaboration is a choreographed state of more than two Business Collaboration roles. This collaboration is being deprecated.

Element Information

Model

Documentation* , Role{3,unbounded} , TimeToPerform , Start , BeginsWhen* , PreCondition* , PostCondition* , EndsWhen* , (BusinessTransactionActivity{0,1} | CollaborationActivity{0,1} | ComplexBusinessTransactionActivity{0,1} | Success{0,1} | Failure{0,1} | Transition{0,1} | Fork{0,1} | Join{0,1} | Decision{0,1})

Children: BeginsWhen, BusinessTransactionActivity, CollaborationActivity, ComplexBusinessTransactionActivity, Decision, Documentation, EndsWhen, Failure, Fork, Join, PostCondition, PreCondition, Role, Start, Success, TimeToPerform, Transition

Attributes

QName

Type

Fixed

Default

Use

Inheritable

Annotation

isInnerCollaboration

xsd:boolean

false

optional

Indicates whether or not this Business Collaboration definition
can only be used within a Business Collaboration activity (as a sub
collaboration) or initiated directly by a party.

name

xsd:string

required

A designation that may be relevant to a business analyst but is
not intended for referencing.

nameID

xsd:ID

required

Used for referencing, for example, for identification of elements
within an ebBP instance.

pattern

xsd:anyURI

optional

May point to the pattern on which an activity or collaboration is
based. This attribute is used only when not using the concrete BT
patterns provided.

Wildcard: ANY attribute from ANY namespace OTHER than 'http://docs.oasis-open.org/ebxmlbp/ebbp-2.0'

Used By

Complex Types	PackageType, ProcessSpecificationType
Elements	Package, ProcessSpecification

Source