Suggested Approach

  1. Add User Interface (UI) and backend to support self-configuration of the interface by ATS/PMS admin user
    • Ability to choose TazWorks’ InstaScreen as the Interface
    • Field to configure CRA’s unique URL
    • Field(s) to configure Package Name(s) available for ordering. For additional flexibility, and complexity, also support fields to support individual Searches per available Package. [The easiest approach is to have your system order by package name (see attached) and send in all applicant’s relevant resume data with every order. Our system will discard any data unnecessary for the package ordered.]
    • Option to request TazWorks’ QuickApp feature (When checked it will need to simply include an additional XML flag in the submission)
    • Ability to manage background screening credentials (user name and password).
      • Fields for entering credentials for a single “XML user” account. (requires the IP address(es) of the order requesting servers, but does not expire)
      • Or to better track, the requestor and compliance accountability the background screening credentials can be stored in the profile of each user’s ATS account. Practical only if the user can update their own password on demand.
      • Or the background screening credentials can be required at order submission time (best security practice). Note: Any background screening password stored in the ATS software must be encrypted and not readable by anyone including the development team. We will need the IP address(es) of your order requesting servers.
  2. User Interface and backend to support posting XML requests for background checks and interpreting submission response status (error or pending).
  3. User Interface and backend to support querying report status or receiving XML status updates posted from TazWorks’ InstaScreen (preferred method). Completed background checks can be viewed using the Report View Link returned in response XML messages.
  4. Option: Include Application/Authorization form as an attachment with each XML order. [Coming Soon]
  5. Option: Consume our Report Decision value in the same XML message as (3) above and display it in the applicant’s file. Our Report Decision returns values of Approved (green), Decline (red), or Review (yellow).
  6. tenant Screening Option: Consume our Scorecard value in the same XML message as (3) above and display it in the applicant’s file. Our Scorecard returns values of Pending Review, Pass, Fail, or Conditional .