Documentation for ebXML Electronic Business using eXtensible Markup Language
Definition Type: Element
Name: StatusVisibility
Namespace: http://docs.oasis-open.org/ebxml-bp/ebbp-2.0
Containing Schema: ebbp-2.0.4.xsd
Abstract
Documentation:
Information (which can be aggregated) returned by the subparties of an embedded Business Transaction Activity or ComplexBTA for visibility purposes to the outermost ComplexBTA. For example, a subparty (requester in an embedded BTA that is responder in ComplexBTA) returns aggregated supplier information to the ComplexBTA prior to the responder issuing an order response. The Status Visibility element specifies which status values and which Document Envelope events of the embedded processes are considered, if any, when returning the status value to the context of the ComplexBTA. If no status values or DocumentEnvelope events can be monitored, then both BusinessDocumentList and SubstateVisibility are omitted. Note, this element was added in v2.0.
Collapse XSD Schema Diagram:
Drilldown into SubstateVisibility in schema ebbp-2_0_4_xsd Drilldown into BusinessDocumentList in schema ebbp-2_0_4_xsd Drilldown into nameID in schema ebbp-2_0_4_xsd Drilldown into name in schema ebbp-2_0_4_xsd Drilldown into name in schema ebbp-2_0_4_xsdXSD Diagram of StatusVisibility in schema ebbp-2_0_4_xsd (ebXML Electronic Business using eXtensible Markup Language)
Collapse XSD Schema Code: 
<xsd:element name="StatusVisibility">
    <xsd:annotation>
        <xsd:documentation>Information (which can be aggregated) returned by the subparties of
				an embedded Business Transaction Activity or ComplexBTA for visibility purposes to
				the outermost ComplexBTA. For example, a subparty (requester in an embedded BTA that
				is responder in ComplexBTA) returns aggregated supplier information to the
				ComplexBTA prior to the responder issuing an order response. The Status Visibility
				element specifies which status values and which Document Envelope events of the
				embedded processes are considered, if any, when returning the status value to the
				context of the ComplexBTA. If no status values or DocumentEnvelope events can be
				monitored, then both BusinessDocumentList and SubstateVisibility are omitted. Note,
				this element was added in v2.0.</xsd:documentation>
    </xsd:annotation>
    <xsd:complexType>
        <xsd:sequence>
            <xsd:element name="BusinessDocumentList" type="BusinessDocumentValueList" minOccurs="0" />
            <xsd:element name="SubstateVisibility" type="ConditionGuardValueList" minOccurs="0" />
            <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
        </xsd:sequence>
        <xsd:attributeGroup ref="name" />
    </xsd:complexType>
</xsd:element>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
BusinessDocumentList nsB:BusinessDocumentList 0 (1)
SubstateVisibility nsB:SubstateVisibility 0 (1)
<xs:any> Allowed namespace: '##other' 0 unbounded
Collapse Child Attributes:
Name Type Default Value Use
name nsB:name Required
nameID nsB:nameID Required
<anyAttribute> Allowed namespace: '##other'
Documentation for ebXML Electronic Business using eXtensible Markup Language

Generated using Liquid Studio - Developer Bundle 21.0.0.0