 AlternateDocumentID | The DocumentID serves as an identifier of an entity corresponding to the noun instance (i.e., the entity being managed in an interaction). In many cases, trading partner requirements may make it necessary to associate multiple indentifiers for an entity. Only a single DocumentID is permitted within any noun instance, but multiple AlternateDocumentIDs are permitted. |
| CustomerParty | Contains the set of information about a Customer Party necessary to execute and administer orders or requests. The Customer Party usually would be an "ultimate" customer versus an intermediary. |
 DocumentID | |
| DocumentSequence | Intended as an identifier on different instances of a noun in a BOD message instance. It is possible to have a single BOD message instance with both multiple nouns instances and multiple ActionExpressions. In support of this need, every noun is defined with DocumentID and DocumentSequence property elements. The DocumentID serves as an identifier of an entity corresponding to the noun. The DocumentSequence serves as an identifier on the different instances of a noun in a message instance; the sequence numbers are specific to the message instance (i.e. in the case of a message instance with two noun instances, the first noun instance may have a DocumentSequence of "1" and the second noun instance would have a DocumentSequence of "2". |
| PackageID | The "package" concept is used within both the employment screening and assessment domains. A package is a screening or a collection of screenings (or assessment or a collection of assessments) that are referenced when ordering services. The package concept greatly simplifies the ordering process. A PackageID is a unique identifier for the package. PackageIDs are developed and assigned by the service provider. Packages can be customized per client or standardized for offerings for multiple clients. |
| RequesterParty | The Requester Party usually is an intermediary, such as an Applicant Tracking System or Vendor Management System. |
| ScreeningCatalogOrderScope | Indicator to identify the scope of work to be reported on for this Screening Catalog Order.Contains a set of details about compliance requirements, prerequisites, or other similar conditions that apply to the particular screening. |
| ScreeningCatalogTypeCode | Classifies the type of catalog order to be performed. |
| SupplierParty | Contains the set of information about a Supplier Party necessary to execute and administer orders or requests. The Supplier Party usually might be a staffing supplier, assessment provider, etc. |
| UserArea | Allows the implementer to extend the base HR-XML specification.
This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.
Allows the implementer to extend the base HR-XML specification.
This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.
|