Implementation considerations for background check requests
-
The BackgroundCheck node builds the XML file to submit to a vendor.
Additional XML nodes in the process are appended to this XML file.
-
The ResourceScreening node determines which types of screening data is
submitted to the vendor. Additional queries in the process retrieve the supporting data
for each screening type. For example, if the type is Education, the Branch8560 node
queries EmployeeEducation and XML9370 appends this data to the XML file.
-
Assign6210 performs URL encoding, which may be required depending on
the vendor of choice. The WebService uses the encoded String as its input
-
The WebSvc8180 node is a WebService. The URL/WSDL must be modified to
use the web service for customer’s vendor of choice.
-
After the vendor specific WSDL is defined, the remaining nodes should
be evaluated based on the vendor’s requirements.
-
Determine if the vendor has acknowledged or completed the request and what response information should be stored on the Resource Screening Package. The template shows an example of how the output of a WebService can be used for this evaluation.
-
The output of the WebService is parsed in the Response node.
-
The Branch2020 node uses the output from the Response node to
determine if the Resource Screening Package can be updated.
-
If the output returns an Order Status of Open, the Acknowledgment
node invokes the Infor HR Talent ReceiveAcknowledgement action,
updates the Resource Screening Package with the response information returned from the
vendor, and changes the status to In Progress.
-
If the output returns an Order Status of Completed, the
ReceiveResults node invokes the Infor HR Talent
ReceiveResults action, updates the Resource Screening Package with the response
information returned from the vendor, and changes the status to Completed.
-
If the output returns an Order Status that is neither Completed nor
Open, the process ends and the Resource Screening Package is not updated. The status
remains as Proposed.