This document provides information for constructing and sending data to TBW utilizing the HR-XML standard for exchange of information relevant to an Order Request.
TBW currently utilizes HR-XML version 2.5 specifications.

This section details the mechanism of transferring HR-XML formatted files to and from TBW as part of the ordering process.

TBW Web Service is SOAP-based and will accept HR-XML documents via HTTPS POST to the following URL:

https://www.tbwonline.com/TBW_WebServices/IntegrationService.asmx
Requests for service should be sent as data in the HTTPS POST (i.e. data = HR-XML request).

Process of placing orders to TBW by “VerificationApiIntegration.exe” are explained as follows,

Fetch the verification records from salesforce on basis of some condition, are as follows,
TBW_Sent__c should be false, Approved_to_Send_to_TBW__c should be true, PreEmploy_Case__c should not be null, Background_Search__c should not be null,
Applicant_First_Name__c should not be null, Applicant_Last_Name__cshould not be null, PreEmploy_Case__r.Government_ID_Number__c should not be null, Owner.
Name should be 'Sent to TBW', Type__c should be one of the 'Employment Verification', 'Degree Verification', 'Reference Verification'

Required fields for placing order verification as per verification type are as follows,
A) Common Fields for all Verification Type

=> Any one from below three fields should be filled for Reference Verification

HR-XML Background Request Response : HR-XML Background Results Response Processing by the web service “TBWBackgrounWarehouseWs.asmx”

Step 1: This is secured web service, so it is necessary to have the credentials in result XML for authentication.
Step 2: After authentication this result XML is getting saved to sql db in table “VerificationApiIntegrationStatusUpdates” having 'nt_request_from'
field value as “webservice”
Step 3: Getting all the values from result xml by querying on it and going to save these value to salesforce verified fields. Values will be saved
only in particular verification type for which the result is received. Question and answers are also getting saved to salesforce verification.
Step 4: For a single verification, web service getting hit many times by diff. result conversation XMLs having action code according
its status of conversation.
Last XML and second last XML plays important role to have responsibility to complete that search. Second last XML have action code “40” and
action type “complete”, “27” for “Cancel” and also others as the current status at that time. On the basis of that action we are updating the fields in salesforce.
In case of action code “40” we are updating all the fields of salesforce accordingly.
Last XML have the action code 38 which is responsible to close the search. In this case integration updates the value of the field “TBW Complete” as “true”
which gone complete the search.
In case of action codes other than 40 and 38, integration updates only limited fields in salesforce.
The process “Automatic Close from TBW ” triggers when final results are returned from TBW, so far it looks like they do two “final” updates where they say report
complete, one has an action code of 40 which means it's complete, but in their internal review (so we don’t get data) then the final review XML with the data
has code 38. The process of closing the search is not trigger on code 40 to avoid the search being closed out and preventing the update 38 from happening.
Note : If any update comes after search is closed, in that case script doesn't update Salesforce and send out an email to it group.

TBW-PreEmploy Integration Field Mapping of fields from Request XML to Fields in salesforce