<!--
The notices below are provided with respect to licensed content incorporated herein:
Copyright HR-XML Consortium. All Rights Reserved. http://www.hrxmlconsortium.org and http://www.hr-xml.org. Terms of license can be found in license.pdf.
Copyright (c) 1997-2009 Open Applications Group, Inc. All Rights Reserved. http://www.openapplications.org
-->
<xsd:schema targetNamespace="http://www.hr-xml.org/3" xmlns:oa="http://www.openapplications.org/oagis/9" xmlns="http://www.hr-xml.org/3" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:annotation>
<xsd:documentation>
Name: SyncScreeningPackageOrder.xsd
Status: 3.0 Public Release
Date this version: 2009-Sep-23
</xsd:documentation>
</xsd:annotation>
<xsd:include schemaLocation="../Nouns/ScreeningPackageOrder.xsd"/>
<xsd:import namespace="http://www.openapplications.org/oagis/9" schemaLocation="../../../../org_openapplications_platform/1_1/Common/OAGi/Components/Meta.xsd"/>
<xsd:element name="SyncScreeningPackageOrder" type="SyncScreeningPackageOrderType"/>
<xsd:complexType name="SyncScreeningPackageOrderType">
<xsd:annotation>
<xsd:documentation>
SyncScreeningPackageOrder is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncScreeningPackageOrder does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture. The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input.
ScreeningPackageOrder This is a subset of the full ScreeningOrder. It is intended to support an "OrderByPackageID" scenario. As the name implies, the "order by package" pattern involves bundling all screening service options within predefined packages that are known to the customer and to the screening provider. This enables services to be ordered simply by referencing an associated "PackageID." When using this pattern, details about specific screening services do not have to be communicated within the order. This simplifies order creation significantly and provides the opportunity to use an interoperable subset of the full ScreeningOrder noun.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="oa:BusinessObjectDocumentType">
<xsd:sequence>
<xsd:element name="DataArea" type="SyncScreeningPackageOrderDataAreaType">
<xsd:annotation>
<xsd:documentation>The DataArea is the part of the BOD that contains business information. This information consists of a verb and one or more noun instances.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="SyncScreeningPackageOrderDataAreaType">
<xsd:sequence>
<xsd:element ref="oa:Sync"/>
<xsd:element ref="ScreeningPackageOrder" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
|
XSD Schema Code: