element <tns:sub-process>
Namespace:
Type:
anonymous complexType
Content:
complex, 6 attributes, 6 elements
Defined:
Includes:
definitions of 3 attributes and 6 elements
XML Representation Summary
<tns:sub-process
    continue
 = 
("async" | "sync" | "exclusive") : "sync"
    g
 = 
string
    name
 = 
string
    outcome
 = 
string
    sub-process-id
 = 
string
    sub-process-key
 = 
string
    >
   
Content: 
(tns:parameter-in*, tns:parameter-out*, tns:timer*, tns:on*, tns:swimlane-mapping*, tns:transition*)*
</tns:sub-process>
Content model elements (6):
Included in content model of elements (2):
tns:group (type anonymous),
Definition Locations
Annotation
Waits while a sub process instance is being executed and continues when the sub process instance ends.
XML Source (see within schema source)
<element name="sub-process">
<annotation>
<documentation>
Waits while a sub process instance is
being executed and continues when the sub process instance ends.
</documentation>
</annotation>
<complexType>
<sequence maxOccurs="unbounded" minOccurs="0">
<element maxOccurs="unbounded" minOccurs="0" name="parameter-in" type="tns:parameterType"/>
<element maxOccurs="unbounded" minOccurs="0" name="parameter-out" type="tns:parameterType"/>
<element maxOccurs="unbounded" minOccurs="0" ref="tns:timer"/>
<element maxOccurs="unbounded" minOccurs="0" ref="tns:on">
<annotation>
<documentation>Events on which listeners can be registered.</documentation>
</annotation>
</element>
<element maxOccurs="unbounded" minOccurs="0" name="swimlane-mapping">
<complexType>
<attribute name="swimlane" type="string" use="required"/>
<attribute name="sub-swimlane" type="string" use="required"/>
</complexType>
</element>
<element maxOccurs="unbounded" minOccurs="0" name="transition">
<complexType>
<complexContent>
<extension base="tns:transitionType">
<sequence maxOccurs="unbounded" minOccurs="0">
<element name="outcome-value">
<complexType>
<group ref="tns:wireObjectGroup"/>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
</element>
</sequence>
<attribute name="sub-process-id" type="string">
<annotation>
<documentation>
Identifies the sub process by the id. This means that a specific
version of a process definition is referenced
</documentation>
</annotation>
</attribute>
<attribute name="sub-process-key" type="string">
<annotation>
<documentation>
Identifies the sub process by the key. This means that the latest
version of the process definition with the given key is referenced. The latest version
of the process is looked up each time the activity executes.
</documentation>
</annotation>
</attribute>
<attribute name="outcome" type="string">
<annotation>
<documentation>
Expression that is evaluated when the sub process
instance ends. The value is then used for outcome transition mapping.
</documentation>
</annotation>
</attribute>
<attributeGroup ref="tns:activityAttributes"/>
</complexType>
</element>
Attribute Detail
continue
Type:
Use:
optional
Default:
"sync"
Defined:
locally, within tns:activityAttributes attributeGroup
To specify async continuations. sync is the default.
XML Source (see within schema source)
<attribute default="sync" name="continue" type="tns:continueType">
<annotation>
<documentation>
To specify async continuations.
sync is the default.
</documentation>
</annotation>
</attribute>

g
Type:
string, predefined
Use:
optional
Defined:
locally, within tns:activityAttributes attributeGroup
Graphical information used by process designer tool.
XML Source (see within schema source)
<attribute name="g" type="string">
<annotation>
<documentation>
Graphical information used by process designer tool.
</documentation>
</annotation>
</attribute>

name
Type:
string, predefined
Use:
optional
Defined:
locally, within tns:activityAttributes attributeGroup
The id of this activity. The name should be unique in the complete scope of the process.
XML Source (see within schema source)
<attribute name="name" type="string">
<annotation>
<documentation>
The id of this activity. The name should be unique
in the complete scope of the process.
</documentation>
</annotation>
</attribute>

outcome
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) tns:sub-process element
Expression that is evaluated when the sub process instance ends. The value is then used for outcome transition mapping.
XML Source (see within schema source)
<attribute name="outcome" type="string">
<annotation>
<documentation>
Expression that is evaluated when the sub process
instance ends. The value is then used for outcome transition mapping.
</documentation>
</annotation>
</attribute>

sub-process-id
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) tns:sub-process element
Identifies the sub process by the id. This means that a specific version of a process definition is referenced
XML Source (see within schema source)
<attribute name="sub-process-id" type="string">
<annotation>
<documentation>
Identifies the sub process by the id. This means that a specific
version of a process definition is referenced
</documentation>
</annotation>
</attribute>

sub-process-key
Type:
string, predefined
Use:
optional
Defined:
locally, within (this) tns:sub-process element
Identifies the sub process by the key. This means that the latest version of the process definition with the given key is referenced. The latest version of the process is looked up each time the activity executes.
XML Source (see within schema source)
<attribute name="sub-process-key" type="string">
<annotation>
<documentation>
Identifies the sub process by the key. This means that the latest
version of the process definition with the given key is referenced. The latest version
of the process is looked up each time the activity executes.
</documentation>
</annotation>
</attribute>
Content Element Detail
tns:on
Type:
anonymous, complex content
Defined:
by reference, within (this) tns:sub-process element
Events on which listeners can be registered.
XML Source (see within schema source)
<element maxOccurs="unbounded" minOccurs="0" ref="tns:on">
<annotation>
<documentation>Events on which listeners can be registered.</documentation>
</annotation>
</element>

tns:parameter-in
Type:
tns:parameterType, empty content
Defined:
locally, within (this) tns:sub-process element
XML Source (see within schema source)
<element maxOccurs="unbounded" minOccurs="0" name="parameter-in" type="tns:parameterType"/>

tns:parameter-out
Type:
tns:parameterType, empty content
Defined:
locally, within (this) tns:sub-process element
XML Source (see within schema source)
<element maxOccurs="unbounded" minOccurs="0" name="parameter-out" type="tns:parameterType"/>

tns:swimlane-mapping
Type:
anonymous, empty content
Defined:
locally, within (this) tns:sub-process element
XML Source (see within schema source)
<element maxOccurs="unbounded" minOccurs="0" name="swimlane-mapping">
<complexType>
<attribute name="swimlane" type="string" use="required"/>
<attribute name="sub-swimlane" type="string" use="required"/>
</complexType>
</element>

tns:timer
Type:
anonymous, complex content
Defined:
by reference, within (this) tns:sub-process element
XML Source (see within schema source)
<element maxOccurs="unbounded" minOccurs="0" ref="tns:timer"/>

tns:transition
Type:
anonymous (extension of tns:transitionType), complex content
Defined:
locally, within (this) tns:sub-process element
XML Source (see within schema source)
<element maxOccurs="unbounded" minOccurs="0" name="transition">
<complexType>
<complexContent>
<extension base="tns:transitionType">
<sequence maxOccurs="unbounded" minOccurs="0">
<element name="outcome-value">
<complexType>
<group ref="tns:wireObjectGroup"/>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
</element>

This XML schema documentation has been generated with DocFlex/XML RE 1.7.2 using DocFlex/XML XSDDoc 2.1.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • To remove this very advertisement text
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/