SilkRoad Logo Print topic
 

HRIS integration and compliance functionality > HRIS integration > Data from SilkRoad Recruiting to an internal system

Previous Topic

Next Topic

Data from SilkRoad Recruiting to an internal system

SilkRoad Recruiting provides a web-based interface for retrieving data. This interface allows retrieval of pre-defined data sets over a secure HTTPS connection in several industry-standard file formats. If your organization is retrieving hired candidate data automatically from SilkRoad Recruiting, it is likely that the data is being obtained via this interface.

Our interface uses pre-defined SQL procedures to produce file output. Our implementation services team works with the customer to determine what data fields need to be included on the extraction file and then writes a procedure that will extract the fields. The procedure can be written to accept various parameters to control which records are output by the procedure. In this way, it is possible to create an extraction of any user-accessible information from the SilkRoad Recruiting database including:

  • Candidate Demographic Information (including EEO data)
  • Candidate EEO Data
  • Candidate Offer and Hired Form Information
  • Candidate eForm Information
  • Job Information

For data to get from SilkRoad Recruiting to your internal system, the following steps must occur. If you are finding an issue with the data on your internal system and you are sure that the data originates in SilkRoad Recruiting, the best way to troubleshoot is to start at the top of this list and work your way downwards, ensuring that each step has occurred as it should. While our technicians are very knowledgeable about our products, they are not knowledgeable about your internal systems. That is why troubleshooting the process one step at a time is so critical. The issue could be on either side of the integration.

  1. Customer process makes a request to SilkRoad Recruiting server for data.
  2. SilkRoad Recruiting system responds to requests and serves up file for download.
  3. Customer process accepts file and downloads.
  4. Customer process places file in internal directory.
  5. Customer process manipulates file to make it ready for load into internal system.
  6. Customer process loads file into internal system.