HR-XML 3.0 Standards, 2009  September  23.

Menu: [ Home  |  Guidelines  |  BODs  |  Nouns  |  Global elements  |  WSDL  |  Packages  |  Code Lists  |  Master Index ]

Trace back: » ch25s04 | ch26 | ch26s04 | ch27 | ch27s04 »

Screening Package: Examples

Example 27.1. NotifyScreeningPackageReport - Example 1

Source


<?xml version="1.0" encoding="UTF-8"?>
<NotifyScreeningPackageReport 
			systemEnvironmentCode="Production" 
			releaseID="3.0"  
			languageCode="en-US" 
			xsi:schemaLocation="http://www.hr-xml.org/3 ../Developer/BODs/NotifyScreeningPackageReport.xsd" 
			xmlns="http://www.hr-xml.org/3" 
			xmlns:oa="http://www.openapplications.org/oagis/9" 
			xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<oa:ApplicationArea>
		<oa:CreationDateTime>2009-10-17T10:09:02.01Z</oa:CreationDateTime>
	</oa:ApplicationArea>
	<DataArea>
		<oa:Notify>
			<oa:ActionCriteria>
				<oa:ActionExpression actionCode="Add">/NotifyScreeningReport/DataArea/ScreeningReport</oa:ActionExpression>
			</oa:ActionCriteria>
		</oa:Notify>
		<ScreeningPackageReport>
			<!-- This is the identifier for the entity being managed. In this case, a ScreeningReport. 
                       This is the recommended ID to reference for further action upon this entity (for example, 
                       to change or replace the report, etc.).  -->
			<DocumentID>1111-000-111-R-2009-10-17</DocumentID>
			<CustomerParty>
				<PartyID>111-00-333-000</PartyID>
				<!-- This block is for customer references that are to be passed through to 
                       support billing, audit, or reporting requirements -->
				<PartyReportingIDs agencyRoleCode="Customer" schemeID="ABC Billing IDs">
					<ID schemeID="DepartmentID">Eng901</ID>
					<ID schemeID="AccountID">1478111</ID>
					<ID schemeID="ProjectID">Eng 2009-1401</ID>
				</PartyReportingIDs>
			</CustomerParty>
			<PackageResult>
			    <!-- Note that in this example, the OrderID corresponds with the DocumentID
                       returned by the screening service provider in its order acknowledgement. 
                 -->
				<ScreeningID>1111-000-111-2009-10-15</ScreeningID>
				<PackageID schemeID="ScreeningCo. Inc PackageIDs" validFrom="2008-09-11">111-334444</PackageID>
				<ScreeningSubject>
				<!-- ScreeningSubject/ID is the identifier used to uniquely distinquish the ScreeningSubject. 
                       In this case, a CandidateID that is set or controlled by the Customer. -->
					<ScreeningSubjectID schemeID="Candidate ID" agencyRoleCode="Customer">1111-000-111</ScreeningSubjectID>
				</ScreeningSubject>
				<!-- A code classifying the type of report or information provided. In this case, a 
                       Summary Result is communicated. --> 
				<ScreeningResultTypeCode>Summary Result</ScreeningResultTypeCode>
				<!-- A code indicating the status of the order,  in this case "Complete" -->
				<ScreeningOrderStatusCode>Complete</ScreeningOrderStatusCode>
				<!-- This is the over all order result (Pass, Fail, Record Found, etc.) as determined 
                        by the screening vendor based on the client’s criteria. -->
				<ScreeningResultCode>Record Found</ScreeningResultCode>
				<!-- A description or message content explaining or related to the 
                       state indicated by the above codes. -->
				<oa:Description>The requested package of services has been fulfilled. 
                                       A record is available for your review. This may or
                                       may not contain disqualifying information.
				</oa:Description>
				<AccessPoint>
				    <!-- This is the URL provided by the screening vendor to the user (a recruiter for example) about where and how 
                           to access the complete screening result report stored on the screening vendor's system. -->
					<oa:URI>http://www.screeningcoinc.com/results/1111-000-111-R-2009-10-17</oa:URI>
					<UserID>SamRecruiter@abc.com</UserID>
				</AccessPoint>
			</PackageResult>
		</ScreeningPackageReport>
	</DataArea>
</NotifyScreeningPackageReport>
<!--


Copyright The HR-XML Consortium. All Rights Reserved. http://www.hr-xml.org 
Copyright (c) 1997-2009 Open Applications Group, Inc. All Rights Reserved 
-->



Example 27.2. ProcessScreeningPackageOrder - Example 1

Source


<?xml version="1.0" encoding="UTF-8"?>
<ProcessScreeningPackageOrder systemEnvironmentCode="Production" releaseID="3.0" languageCode="en-US" xsi:schemaLocation="http://www.hr-xml.org/3 ../Developer/BODs/ProcessScreeningPackageOrder.xsd" xmlns="http://www.hr-xml.org/3" xmlns:oa="http://www.openapplications.org/oagis/9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<oa:ApplicationArea>
		<oa:CreationDateTime>2009-10-15T10:09:02.01Z</oa:CreationDateTime>
	</oa:ApplicationArea>
	<DataArea>
		<oa:Process acknowledgeCode="Always">
			<oa:ActionCriteria>
				<oa:ActionExpression actionCode="Add">/ProcessScreeningPackageOrder/DataArea/ScreeningPackageOrder</oa:ActionExpression>
			</oa:ActionCriteria>
		</oa:Process>
		<ScreeningPackageOrder>
			<ScreeningUser>
				<!-- This is a UserID. This typically would be for an authorized person acting in a role such 
                    as recruiter, HR manager, etc. -->
				<UserID>SamRecruiter@abc.com</UserID>
			</ScreeningUser>
			<CustomerParty>
				<PartyID>111-00-333-000</PartyID>
				<!-- This block is for customer references that are to be passed through to 
                    support billing, audit, or reporting requirements -->
				<PartyReportingIDs agencyRoleCode="Customer" schemeID="ABC Billing IDs">
					<ID schemeID="DepartmentID">Eng901</ID>
					<ID schemeID="AccountID">1478111</ID>
					<ID schemeID="ProjectID">Eng 2009-1401</ID>
				</PartyReportingIDs>
			</CustomerParty>
			<PackageOrder>
				<!-- This illustrates "order by PackageID. The specific screening services included within the order
       are encapsulated within a "Package" referenced by a PackageID that is known to requester
      and screening service supplier. Under this implementation pattern, separate "Screening"  elements 
      are not used. Screening details would be disallowed at the level of :
       /ProcessScreeningOrder/DataArea/ScreeningOrder/ScreeningOrder/ScreeningPackageOrder/Screenings
-->
				<PackageID schemeID="PackageID" schemeAgencyID="ScreeningCo. Inc." validFrom="2008-09-11">111-334444</PackageID>
				<ScreeningSubject>
					<ScreeningSubjectID schemeID="Candidate ID">1111-000-111</ScreeningSubjectID>
					<PersonLegalID schemeID="SSN">222-99-1111</PersonLegalID>
					<ScreeningSubjectName>
						<ScreeningPersonName>
							<ID>01</ID>
							<PersonName validFrom="2006-05-03" nameTypeCode="CurrentName">
								<oa:GivenName>Sue</oa:GivenName>
								<MiddleName>A</MiddleName>
								<FamilyName>Johnson</FamilyName>
							</PersonName>
						</ScreeningPersonName>
						<ScreeningPersonName>
							<ID>02</ID>
							<PersonName validFrom="1975-05-01" validTo="2006-05-03" nameTypeCode="Birth Name">
								<oa:GivenName>Sue</oa:GivenName>
								<MiddleName>A</MiddleName>
								<FamilyName>Smith</FamilyName>
							</PersonName>
						</ScreeningPersonName>
						<FatherName>
							<FamilyName>Smith</FamilyName>
						</FatherName>
					</ScreeningSubjectName>
					<!-- This is a current address for the screening subject. -->
					<Communication sequence="1" preferredIndicator="true" validFrom="2006-05">
						<oa:AreaDialing>919</oa:AreaDialing>
						<oa:DialNumber>555-1212</oa:DialNumber>
					</Communication>
					<Communication sequence="1" preferredIndicator="false" validFrom="2006-05">
						<ChannelCode>Telephone</ChannelCode>
						<UseCode>Personal</UseCode>
						<oa:AreaDialing>919</oa:AreaDialing>
						<oa:DialNumber>555-1213</oa:DialNumber>
					</Communication>
					<Communication sequence="1" preferredIndicator="true" validFrom="2006-05">
						<Address>
							<oa:StreetName>Elm Street.</oa:StreetName>
							<oa:CityName>Morehead City</oa:CityName>
							<oa:CountrySubDivisionCode>NC</oa:CountrySubDivisionCode>
							<CountryCode>US</CountryCode>
							<oa:PostalCode>28557</oa:PostalCode>
						</Address>
					</Communication>
					<!-- This is a prior address. -->
					<Communication validTo="2006-05">
						<Address currentAddressIndicator="false">
							<oa:StreetName>Elm Street.</oa:StreetName>
							<oa:CityName>Main St. Blvd, Ave.</oa:CityName>
							<oa:CountrySubDivisionCode>NC</oa:CountrySubDivisionCode>
							<CountryCode>US</CountryCode>
							<oa:PostalCode>28557</oa:PostalCode>
						</Address>
					</Communication>
					<RaceCode>White</RaceCode>
					<GenderCode>Female</GenderCode>
					<FreeFormBirthDate>
						<FormattedDateTime>1985-04-01</FormattedDateTime>
					</FreeFormBirthDate>
				</ScreeningSubject>
				<AdmittedCharges>
					<!-- This section is for the candidate's admission of charges that are likely to be 
                            found in the Screening. -->
					<AdmittedChargesSummary>Arrested for DUI, 1996, Macon, GA</AdmittedChargesSummary>
				</AdmittedCharges>
				<SearchLicense>
					<License>
						<LicenseID>2248-8881</LicenseID>
						<LicenseTypeCode>Motor Vehicle Personal</LicenseTypeCode>
						<IssuingAuthority>
							<LocationSummary>
								<oa:CountrySubDivisionCode listID="US State Code">NC</oa:CountrySubDivisionCode>
								<CountryCode>US</CountryCode>
							</LocationSummary>
						</IssuingAuthority>
					</License>
				</SearchLicense>
			</PackageOrder>
		</ScreeningPackageOrder>
	</DataArea>
</ProcessScreeningPackageOrder>
<!--


Copyright The HR-XML Consortium. All Rights Reserved. http://www.hr-xml.org 
Copyright (c) 1997-2009 Open Applications Group, Inc. All Rights Reserved 
-->



Comment on this Component


Use the form below to submit your question or comment about "ch27s04"

By submitting you indicate that you are accepting HR-XML's Feedback Policy


  * = required field
First/Given Name: *
Last/Family Name: *
Position Title:
Organization:
Country:
Website:
E-mail: *
Topic:

  Please use the area below to write your comment or question: