<!--
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: ProcessScreeningPackageOrder.xsd
Status: 3.0 Public Release
Date this version: 2009-Sep-23
Purpose: Used to request processing of the ScreeningPackageOrder noun by a receiving application or party.
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.
Process is an "Action Verb". ActionExpression(s) represent and communicate data management
instructions. XPath is the default expression language. The actionCode attribute (Add, Change, Delete,
Replace) specifies the action to be taken by the receiver. The data entities being managed
are represented as elements of the ScreeningPackageOrder noun in the BOD instance.
</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="ProcessScreeningPackageOrder" type="ProcessScreeningPackageOrderType"/>
<xsd:complexType name="ProcessScreeningPackageOrderType">
<xsd:annotation>
<xsd:documentation>
Used to request processing of the ScreeningPackageOrder noun by a receiving application or party.
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.
Process is an "Action Verb". ActionExpression(s) represent and communicate data management
instructions. XPath is the default expression language. The actionCode attribute (Add, Change, Delete,
Replace) specifies the action to be taken by the receiver. The data entities being managed
are represented as elements of the ScreeningPackageOrder noun in the BOD instance.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="oa:BusinessObjectDocumentType">
<xsd:sequence>
<xsd:element name="DataArea" type="ProcessScreeningPackageOrderDataAreaType">
<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. In the case of the ProcessScreeningPackageOrder, the verb Process indicates the action to be performed on the noun ScreeningPackageOrder.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ProcessScreeningPackageOrderDataAreaType">
<xsd:sequence>
<xsd:element ref="oa:Process"/>
<xsd:element ref="ScreeningPackageOrder" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
|
XSD Schema Code: