Documentation for HR-XML - Human Resources XML
Definition Type: ComplexType
Name: SyncScreeningPackageOrderType
Namespace: http://www.hr-xml.org/3
Type: oa:BusinessObjectDocumentType
Containing Schema: SyncScreeningPackageOrder.xsd
Abstract
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.
Collapse XSD Schema Diagram:
Drilldown into DataArea in schema syncscreeningpackageorder_xsd Drilldown into ApplicationArea in schema meta_xsd Drilldown into languageCode in schema meta_xsd Drilldown into systemEnvironmentCode in schema meta_xsd Drilldown into versionID in schema meta_xsd Drilldown into releaseID in schema meta_xsd Drilldown into BusinessObjectDocumentType in schema meta_xsdXSD Diagram of SyncScreeningPackageOrderType in schema syncscreeningpackageorder_xsd (HR-XML - Human Resources XML)
Collapse XSD Schema Code: 
<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>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
ApplicationArea oa:ApplicationArea (1) (1)
DataArea nsA:DataArea (1) (1)
Collapse Child Attributes:
Name Type Default Value Use
releaseID oa:releaseID Required
versionID oa:versionID Optional
systemEnvironmentCode oa:systemEnvironmentCode Production Optional
languageCode oa:languageCode en-US Optional
Collapse Derivation Tree:
Collapse References:
nsA:SyncScreeningPackageOrder
Documentation for HR-XML - Human Resources XML

Generated using Liquid Studio - Developer Bundle 21.0.0.0