Archives: September 21, 2015

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>