All posts by tt_staff

The definitive upgrade protocol for TCC is spelled out in Doc ID 1907629.1, here’s the answer:

Read More

I’m always trying to make sense of TCC versions and found this article on MOS that addresses it SD6004 – TCC Version (Doc ID 1047569.1)

Read More

Another piece of documentation buried in the docs of a TCC installation.

As we know the [NOW] is a symbol that translates the current date and time as such:
The default date format is: NOW(“yyyyMMdd’T’HHmmss”) = 20080702T10:12:00

You can specify the time format by using any supported date and time pattern: NOW(“EEE, MMM d, yyyy”) = Wed, Jul 2, 2008

For more information on supported date and time patterns, please refer to: http:// java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html

This is strait out of the manual…

Read More

This is for new hire exports where you only want the most recent offer to be returned.  Remember to set the ownerQuery name.

<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:equal>
<quer:field path="Offers"/>
<quer:query projectedClass="Offer" alias="My_Offer_Subquery">
<quer:projections>
<quer:projection alias="MaxOffer">
<quer:maximum>
<quer:field path="Offers,Number"/>
</quer:maximum>
</quer:projection>
</quer:projections>
<quer:filterings>
<quer:filtering>
<quer:equal>
<quer:field path="Application,Offers"/>
<quer:field ownerQuery="NewHire" path="Offers,Number"/>
</quer:equal>
</quer:filtering>
</quer:filterings>
</quer:query>
</quer:equal>
</quer:filtering>

You are correct, normally a record that is dropped from a net-change data file will result in it being deleted or de-activated in the zone by following net-change run.  However if there was a net-change setup run before the next ‘normal’ net-change than this wouldn’t happen.   This is because the net-change setup will delete the current net-change data repository and then re-populates it with zone values, but only for those records in the data file.  I’ve recently written an example for this scenario that may make this more clear.

Read More

Here’s how:

Add this to the environment file:
SET RESPONSE_FOLDER=..\..\data\response

Then add this to the tcc.bat:
SET JAVA_OPTS=%JAVA_OPTS% -Dcom.taleo.client.symbol.RESPONSE_FOLDER=”%RESPONSE_FOLDER%”

Then add this to the TCC_GUI.bat:
call :makeAbsoluteShortName RESPONSE_FOLDER
>>”%TCC_HOME%\TaleoConnectClient.ini” echo -Dcom.taleo.client.symbol.RESPONSE_FOLDER=%RESPONSE_FOLDER%

Configuration, export and import files refer to product integration packs through an alpha-numeric code.|

Read More

Found a great explanation on the subject here, posted it here for posterity.

This is an unfortunate misnaming perpetrated by Windows.

Because Windows uses UTF-16LE encoding internally as the memory storage format for Unicode strings, it considers this to be the natural encoding of Unicode text. In the Windows world, there are ANSI strings (the system codepage on the current machine, subject to total unportability) and there are Unicode strings (stored internally as UTF-16LE).

This was all devised in the early days of Unicode, before we realised that UCS-2 wasn’t enough, and before UTF-8 was invented. This is why Windows’s support for UTF-8 is all-round poor.

This misguided naming scheme became part of the user interface. A text editor that uses Windows’s encoding support to provide a range of encodings will automatically and inappropriately describe UTF-16LE as “Unicode”, and UTF-16BE, if provided, as “Unicode big-endian”.

(Other editors that do encodings themselves, like Notepad++, don’t have this problem.)

If it makes you feel any better about it, ‘ANSI’ strings aren’t based on any ANSI standard, either.

Ran across this and it took me a while because of the dot notation that they are using in the path, seems you can just ignore it and use it as part of the path.

<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:or>
<quer:equal>
<quer:field path="Candidate,History,ApplicationTrackingHistoryItem.CreationDate"/>
<quer:query projectedClass="Application" alias="histItemSubQuery">
<quer:projections>
<quer:projection>
<quer:maximum>
<quer:field path="Candidate,History,ApplicationTrackingHistoryItem.CreationDate"/>
</quer:maximum>
</quer:projection>
</quer:projections>
<quer:filterings>
<quer:filtering>
<quer:equal>
<quer:field ownerQuery="histItemSubQuery" path="Number"/>
<quer:field ownerQuery="NewHire" path="Number"/>
</quer:equal>
</quer:filtering>
</quer:filterings>
</quer:query>
</quer:equal>
<quer:isNull>
<quer:field path="Candidate,History,ApplicationTrackingHistoryItem.CreationDate"/>
</quer:isNull>
</quer:or>
</quer:filtering>