Documentation for HR-XML - Human Resources XML
Definition Type: ComplexType
Name: ScreeningCatalogReportType
Namespace: http://www.hr-xml.org/3
Containing Schema: ScreeningCatalogReport.xsd
Abstract
Documentation:
Contains a set of information describing a screening provider's catalog of services. There a variety of use cases that might be served by the ScreeningCatalog. There may be the need to simply retrieve and display descriptive information about screenings or to check current availability or pricing. Retrieval of catalog information could also be a first step in the configuration of a recruiting system with the PackageIDs it needs to submit orders to the screening provider.
Collapse XSD Schema Diagram:
Drilldown into UserArea in schema fields_xsd Drilldown into ScreeningCatalogJurisdictionalScope in schema components_xsd Drilldown into ScreeningCatalogCustomerScope in schema components_xsd Drilldown into SupplierParty in schema components_xsd Drilldown into DocumentSequence in schema fields_xsd Drilldown into AlternateDocumentID in schema fields_xsd Drilldown into DocumentID in schema fields_xsd Drilldown into DocumentIDGroup in schema components_xsd Drilldown into validTo in schema fields_xsd Drilldown into validFrom in schema fields_xsd Drilldown into EffectiveDateAttributeGroup in schema fields_xsd Drilldown into languageCode in schema screeningcatalogreport_xsdXSD Diagram of ScreeningCatalogReportType in schema screeningcatalogreport_xsd (HR-XML - Human Resources XML)
Collapse XSD Schema Code: 
<xsd:complexType name="ScreeningCatalogReportType">
    <xsd:annotation>
        <xsd:documentation>Contains a set of information describing a screening provider's catalog of services. There a variety of use cases that might be served by the ScreeningCatalog. There may be the need to simply retrieve and display descriptive information about screenings or to check current availability or pricing. Retrieval of catalog information could also be a first step in the configuration of a recruiting system with the PackageIDs it needs to submit orders to the screening provider.</xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:group ref="DocumentIDGroup" minOccurs="0" />
        <xsd:element ref="DocumentSequence" minOccurs="0" />
        <xsd:element ref="SupplierParty" minOccurs="0" />
        <xsd:choice>
            <xsd:element ref="ScreeningCatalogCustomerScope" minOccurs="0" />
            <xsd:element ref="ScreeningCatalogJurisdictionalScope" minOccurs="0" maxOccurs="unbounded">
                <xsd:annotation>
                    <xsd:documentation>Contains jurisdictional requirements associated with screenings.</xsd:documentation>
                </xsd:annotation>
            </xsd:element>
        </xsd:choice>
        <xsd:element ref="UserArea" minOccurs="0" />
    </xsd:sequence>
    <xsd:attribute name="languageCode" type="LanguageCodeContentType" use="optional" />
    <xsd:attributeGroup ref="EffectiveDateAttributeGroup" />
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
DocumentID nsA:DocumentID (1) (1)
AlternateDocumentID nsA:AlternateDocumentID 0 unbounded
DocumentSequence nsA:DocumentSequence 0 (1)
SupplierParty nsA:SupplierParty 0 (1)
ScreeningCatalogCustomerScope nsA:ScreeningCatalogCustomerScope 0 (1)
ScreeningCatalogJurisdictionalScope nsA:ScreeningCatalogJurisdictionalScope 0 unbounded
UserArea nsA:UserArea 0 (1)
<xs:group> nsA:DocumentIDGroup 0 (1)
Collapse Child Attributes:
Name Type Default Value Use
languageCode nsA:languageCode Optional
validFrom nsA:validFrom Optional
validTo nsA:validTo Optional
Collapse Derivation Tree:
Collapse References:
nsA:ScreeningCatalogReport
Documentation for HR-XML - Human Resources XML

Generated using Liquid Studio - Developer Bundle 21.0.0.0