Skip to content

TEE.md

Latest commit

 

History

History
73 lines (55 loc) · 3.69 KB

TEE.md

File metadata and controls

73 lines (55 loc) · 3.69 KB

Taleo Enterprise Edition (TEE)

FAQ

Why are there more candidates in TEE than in MyCandidates?

Not all candidates will be uploaded. If the candidate does not meet the requirements stated here, they will not be found in MyCandidates. This can sometimes be a large percentage (think 50%, not 5%). See the filters described later in this document.

Why does a query in TEE not produce the same candidates as in myCandidates?

In general we do not recommend comparing search results from TEE to search results in myCandidates. If you are trying to compare results, please try to limit such searching to matching an email address for a candidate. Differences can exist for several reasons. The primary difference is that the filters applied in our search interface may not match those in TEE. Another reason is that the data in myCandidates reflects the most recent candidate and the client may have had newer data for a particular candidate from another source.

Integration Overview

Taleo offers a set of APIs utilized by myCandidates, known commonly as the "Bulk APIs" but technically referred to as the Integration Management Service.

The TEE integration works by sending a query to the Taleo server. The server then builds a document consisting of all of the "entities" that match the query. The integration then requests this document by pages, and then traverses the document page, creating a candidate from each row in the document. The candidate is then sent to the MyCandidates upload API. In other words:

  1. query is sent
  2. document is built
  3. document is retrieved a page at a time
  4. each row in the page is turned into a candidate
  5. the candidate is uploaded to MyCandidates

Technical Details

The endpoints used by the integration are:

  • GetMessageByKey
  • SubmitLargeDocument
  • GetLargeDocumentByKey

The Taleo queries used are fairly complex, but have the effect of only importing candidates that meet the following:

  • must have an attachment
  • attachment must be marked as type RESUME, or have the word “resume” or “CV” in the title (case-insensitive)

Further, MyCandidates requires for all candidates:

  • The document must be at least 100 characters long
  • An email must either be on the candidate or successfully parsed from the resume Some resumes will fail to parse, in which case the candidate will be rejected.

Supported Queries

The integration is configured to allow each client to have a specific query. The queries determine what data can be populated on the candidate for the client.

Currently there are two supported queries, Profile Entity and Candidate Entity. The Profile Entity query provides the ability to use the pasted resume text in the event that a candidate does not have an attachment. The validity of this query will vary per client (a client may not have data in this node, the node may not exist, or it may not be valid resume data).

Candidate Entity

  • Number
  • FirstName
  • LastName
  • EmailAddress
  • MobilePhone
  • HomePhone
  • WorkPhone
  • ZipCode
  • LastModifiedDate
  • AttachedFiles
  • AttachedFiles,Attachment,FileContent
  • AttachedFiles,Attachment,FileName
  • AttachedFiles,Attachment,AttachmentType,Code
  • AttachedFiles,Attachment,LastModificationDate

Profile Entity

  • Candidate (all projections shown for the Candidate Entity)
  • ApplicationText,PastedResume

Needs for a New Fulfillment

In order to access the IMS APIs, MyCandidates needs an account created with the following "rights":

  • User type = Integration
  • User permissions:
    • Allow this user to perform integration tasks
    • Allow batch export
    • Allow batch import

MyCandidatesIntegrationDocumentation Copyright 2017 CareerBuilder, LLC This product includes software developed at CareerBuilder, LLC (http://www.careerbuilder.com)