Aron's Tech Blog

So more of the fun of projecting candidate answers to diversity questions is actually figuring out what the form, question and answers can be. So to make our lives easier here is the export file to glean this information.

Create an empty file named: DiversityPossibleAnswerExport_sq.xml

Copy this information into the file, build the config and run and all questions (and answers) will be revealed.

<?xml version="1.0" encoding="UTF-8"?>
<quer:query productCode="RC1401" model="http://www.taleo.com/ws/tee800/2009/01" projectedClass="DiversityPossibleAnswer" locale="en" mode="CSV" csvheader="true" csvdelimiter="|" csvquote="&quot;" largegraph="true" preventDuplicates="false" xmlns:quer="http://www.taleo.com/ws/integration/query"><quer:subQueries/><quer:projections><quer:projection><quer:field path="Question,DiversityQuestion.RegulationForm,Number"/></quer:projection><quer:projection><quer:field path="Question,DiversityQuestion.RegulationForm,Code"/></quer:projection><quer:projection><quer:field path="Question,DiversityQuestion.RegulationForm,Name"/></quer:projection><quer:projection><quer:field path="Question,DiversityQuestion.RegulationForm,Active"/></quer:projection><quer:projection><quer:field path="Question,DiversityQuestion.RegulationForm,Status,Code"/></quer:projection><quer:projection><quer:field path="Question,Number"/></quer:projection><quer:projection><quer:field path="Question,Code"/></quer:projection><quer:projection><quer:field path="Question,Name"/></quer:projection><quer:projection><quer:field path="Question,Active"/></quer:projection><quer:projection><quer:field path="Question,Status,Code"/></quer:projection><quer:projection><quer:field path="Number"/></quer:projection><quer:projection><quer:field path="Description"/></quer:projection></quer:projections><quer:projectionFilterings/><quer:filterings/><quer:sortings/><quer:sortingFilterings/><quer:groupings/><quer:joinings/></quer:query>

Sometimes you get to export a field where someone could have placed CR/LF’s, which is an enter in a text area sending carriage return line feed. This is the replace statement that will removed it and replace it with a blank:

<quer:projection alias="OfferNotes" projectedValueType="string" xmlns:quer="http://www.taleo.com/ws/integration/query">
  <quer:replace>
    <quer:replace>
      <quer:field path="CurrentOffer,Notes"/>
      <quer:customFunction name="CHR">
        <quer:integer>10</quer:integer>
      </quer:customFunction>
      <quer:string/>
    </quer:replace>
    <quer:customFunction name="CHR">
      <quer:integer>13</quer:integer>
    </quer:customFunction>
    <quer:string/>
  </quer:replace>
</quer:projection>

In advanced export options:
Check Prevent Duplicates
Add pageindex with a value of 1 for the first page, 2 for the second, etc.
Add pagingsize with a value of the number of records to be returned.

Saw this on the KX and thought it would serve me well one day (Doc ID 1045362.1)

One of the more troublesome aspects of EEO is trying to figure out what a candidate entered as it’s masked on the front end and it’s really hard to tell.

Create a file called CandidateDiversityAnswers_sq.xml

Copy and paste the following to get everything that they’ve entered for EEO (please note this is from the standard EEO questions, not custom):

<?xml version="1.0" encoding="UTF-8"?>
<quer:query productCode="RC1401" model="http://www.taleo.com/ws/tee800/2009/01" projectedClass="Candidate" locale="en" mode="CSV" csvheader="true" csvdelimiter="|" csvquote="&quot;" largegraph="true" preventDuplicates="false" xmlns:quer="http://www.taleo.com/ws/integration/query"><quer:subQueries/><quer:projections><quer:projection><quer:field path="Number"/></quer:projection><quer:projection><quer:field path="FirstName"/></quer:projection><quer:projection><quer:field path="LastName"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,Question,DiversityQuestion.RegulationForm,Number"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,Question,DiversityQuestion.RegulationForm,Code"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,Question,DiversityQuestion.RegulationForm,Name"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,Question,Number"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,Question,Code"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,Question,Name"/></quer:projection><quer:projection alias="CreationDate" projectedValueType="string" projectedField="DiversityAnswers,RuntimeString:CreationDateFormatted"><quer:customFunction name="TO_CHAR"><quer:field path="DiversityAnswers,CreationDate"/><quer:string>yyyy-MM-dd</quer:string></quer:customFunction></quer:projection><quer:projection><quer:field path="DiversityAnswers,PossibleAnswer,Number"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,PossibleAnswer,Sequence"/></quer:projection><quer:projection><quer:field path="DiversityAnswers,PossibleAnswer,Description"/></quer:projection></quer:projections><quer:projectionFilterings/><quer:filterings><quer:filtering><quer:equal><quer:field path="Number"/><quer:long>348272</quer:long></quer:equal></quer:filtering></quer:filterings><quer:sortings/><quer:sortingFilterings/><quer:groupings/><quer:joinings/></quer:query>

I’ve run into situations many times where the integration is not built around touchpoints. I had always assumed that if you didn’t use the touchpoints for the integration that you were unable to set the symbols that are to be used with the integration. About a month ago TCC started doing something funky, it created a weird new endpoint and I wasn’t sure why. I then noticed my stock TCC was acting like it was using the touchpoints (e.g. it was using a config board). After a little more research I realized that the TaleoConnectClient.ini had been changed and there were now symbols, something unheard of when not using touchpoints. It turns out that it somehow wrote them into the ini file, not sure why or how but this is what was in there and it looks to be pretty promising for fixing some issues I run into when folks aren’t using the touchpoints.
read more »

This is the standard base import for a user defined selection element merge, it does not contain OLF links but that’s simple enough to add
Create file called UDSElementMerge_ld.xml
User the following for the content:

<?xml version="1.0" encoding="UTF-8"?>
<load:load productCode="RC1501" model="http://www.taleo.com/ws/tee800/2009/01" root="UDSElement" operation="merge" locale="en" header="true" delimiter="," quote="&quot;" xmlns:load="http://www.taleo.com/ws/integration/load">
 <load:columns>
 <load:column type="IDENTIFIER" header="Identifier" path=""/>
 <load:column parameter="1" type="DATA" path="Code" searchType="SEARCH_AND_VALUE" searchTarget="." localeType="NONE"/>
 <load:column parameter="1" path="Description" searchType="NONE" localeType="DEFAULT" type="DATA"/>
 <load:column parameter="1" type="DATA" path="UserDefinedSelection,Code" searchType="SEARCH" searchTarget="." localeType="NONE"/>
 <load:column parameter="1" type="DATA" path="UserDefinedSelection,Code" searchType="SEARCH" searchTarget=".." localeType="NONE"/>
 <load:column parameter="1" path="Active" searchType="NONE" localeType="NONE" type="DATA"/>
 <load:column parameter="1" path="Complete" searchType="NONE" localeType="NONE" type="DATA"/>
 <load:column parameter="1" path="Sequence" searchType="NONE" localeType="NONE" type="DATA"/>
 </load:columns>
 <load:processingInstructions/>
</load:load>

For the next time I need this because my editor is buggy:

<quer:projection alias="Ident" xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:concatenate>
<quer:field path="Candidate,Number"/>
<quer:string>_</quer:string>
<quer:field path="Requisition,Number"/>
</quer:concatenate>
</quer:projection>

One thing about TCC is that you do have to deal with export limits, now 500k records a day sounds like a lot but you have to break those down into 100k chunks and therein lies the rub.  Fortunately there is a way around that, check out this document in the MOS for directions on dealing with this.