I think you should probably do this for every zone your in but if you need to make an attachment a resume. You must use attache-file-to-profile-by-type or application by type and use one of the types listed here:

Read More

Took a while to figure this out so figured I’d better put it here for safe keeping…

<quer:projection alias="SSN2" xmlns:quer="http://www.taleo.com/ws/integration/query">
	<quer:replace>
		<quer:replace>
			<quer:field path="Title"/>
			<quer:string>,</quer:string>
			<quer:string/>
		</quer:replace>
		<quer:string>|</quer:string>
		<quer:string/>
	</quer:replace>
</quer:projection>

Needed this for a project and seemed to work pretty well for nesting operations.

<quer:projection alias="SSN2" xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:substring>
<quer:toChar>
<quer:customFunction name="REGEXP_REPLACE">
<quer:field path="Candidate,SocialSecurityNumber"/>
<quer:string>[^[:digit:]]</quer:string>
<quer:string/>
</quer:customFunction>
</quer:toChar>
<quer:integer>6</quer:integer>
<quer:integer>4</quer:integer>
</quer:substring>
</quer:projection>

So I’ve recently been dealing with a Linux installation with TCC and truth be told, don’t try to play this tune unless you can install the (deprecated) 1.6 JRE. Considering they are now Oracle, your would think that they would fix it. NEVER try to use 1.7.X with TCC on Linux, you will have a bad day…

If you’ve used TCC for any length of time, you’ll know that the best way to develop is in the touch points. That being said you’ll have to write a batch or shell script to execute. Here is the formulation of the export:

taleoconnectclient.bat [cfg file to be called] [sq file to be called] [Where the output file goes]

The import is as such:
taleoconnectclient.bat [cfg file to be called] [file to be sent] [response file]

Got this right for exporting a new password based on the last 4 of social as related to information directly in the system:

<quer:projection alias="NewPassword" xmlns:quer="http://www.taleo.com/ws/integration/query">
  <quer:concatenate>
    <quer:string>Taleo</quer:string>
    <quer:substring>
      <quer:toChar>
        <quer:customFunction name="REGEXP_REPLACE">
          <quer:field path="Candidate,SocialSecurityNumber"/>
          <quer:string>[^[:digit:]]</quer:string>
          <quer:string/>
        </quer:customFunction>
      </quer:toChar>
      <quer:integer>6</quer:integer>
      <quer:integer>4</quer:integer>
    </quer:substring>
  </quer:concatenate>
</quer:projection>

If you ever get this on an export it may be because you used the keyword ‘Initial’ someplace as an alias.  Not much fun tracking that down…

This subject has come up time after time so I’m going to attempt to document.  In order to pull this off you have to create about a dozen integrations.  They aren’t elaborate but it does require some inside information.  I’m attempting to document it here for future reference.

Read More

So digging through the full export of questions I had to consult the data dictionary and was pleasantly surprised that I came upon a new to me table called TypeOfQuestion. If you filter on the value in this table from your export, you can just return the type of questions that you are looking for. Here are the look up values:

Every time that I run across the diversity answer export it gives me trouble. So I suppose it’s time to document it. To find the variables do an export on DiverstityAnswers targeting the Question and PossibleAnswer related tables. You can then sub them into this projection:

<quer:projection id="idGender" alias="USAEEO2Gender" xmlns:quer="http://www.taleo.com/ws/integration/query">
  <quer:query projectedClass="Candidate" alias="EEO2b_Gender">
    <quer:projections>
      <quer:projection alias="EEO2b_Gender">
        <quer:decode>
          <quer:field path="DiversityAnswers,PossibleAnswer,Sequence"/>
          <quer:integer>2</quer:integer>
          <quer:string>M</quer:string>
          <quer:integer>3</quer:integer>
          <quer:string>F</quer:string>
          <quer:integer>4</quer:integer>
          <quer:string>U</quer:string>
        </quer:decode>
      </quer:projection>
    </quer:projections>
    <quer:filterings>
      <quer:filtering>
        <quer:equal>
          <quer:field path="DiversityAnswers,Question,Code"/>
          <quer:string>EEO2b Gender</quer:string>
        </quer:equal>
      </quer:filtering>
      <quer:filtering>
        <quer:equal>
          <quer:field path="Number"/>
          <quer:field ownerQuery="NewHire" path="Candidate"/>
        </quer:equal>
      </quer:filtering>
    </quer:filterings>
  </quer:query>
</quer:projection>