Archives: December 28, 2016

When building an export and the spec calls for returning the preferred phone, you can use this decode to avoid all the mouse clicks.

<quer:projection alias="PreferredPhone" xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:decode>
<quer:field path="Candidate,PreferredPhone,Number"/>
<quer:integer>1</quer:integer>
<quer:field path="Candidate,HomePhone"/>
<quer:integer>2</quer:integer>
<quer:field path="Candidate,WorkPhone"/>
<quer:integer>3</quer:integer>
<quer:field path="Candidate,MobilePhone"/>
<quer:integer>4</quer:integer>
<quer:field path="Candidate,PagerPhone"/>
<quer:integer>5</quer:integer>
<quer:field path="Candidate,Fax"/>
</quer:decode>
</quer:projection>

In case you were wondering, here’s how it’s done:

Use the Unicode Hex character code value for the horizontal tabulation character.

Type 	 in CSV Value Delimiter.

I saw this while I was digging for some other information and it made me wonder if it will work with exporting issues we see with descriptions and qualifications.

Will have that answer soon…

Goal

When executing the sub-query result of a CLOB or BLOB projection, TCC returns the signature of the underlying object (e.g.: oracle.sql.BLOB@334693be), rather than the actual content.

To get the actual content the projections must use a data type cast, but the lob cast in Oracle has a 4000 characters limit, which is insufficient for many attached files.

Solution

In the complex projection, set the projectedValueType to “[B”, example as following

<quer:projection alias=”BLOB” projectedValueType=”[B” xmlns:quer=”http://www.taleo.com/ws/integration/query”>

See the attached sample for a complete example.

References

NOTE:1047850.1 – SD6210 – Exported Attached Files
NOTE:1047912.1 – SD6243 – Base64 String Decoding
BUG:18642011 – EXPORT FILECONTENT IN SUBQUERIES PROJECTIONS

One thing that’s really important to remember about TCC is that you have to synchronize the custom fields for any new installation or anytime a UDF has been created in the front end. The feature and product integration packs only have the dictionaries for the standard fields. The custom dictionary is located in the [TCC Installation Directory]\customdictionaries directory.

It is also important to point out that these dictionaries are set by product version.  I.E. if your script is on 13a, you will need to synchonize with 13a, if you synchronized with 15a in TCC you still wouldn’t see the custom fields.

Read More

User Types and Groups are collections in Taleo. If you need to clear them you can drag the parent entity over to the columns of an import and then you can see the reset the collection is available and checked.  This is a Boolean for the import file.

Read More

It always drove me crazy trying to figure out what the ISO codes were for locale, then the light came on and I realized I could export it from the language entity…

Read More

<quer:projection alias="TestRowNum" xmlns:quer="http://www.taleo.com/ws/integration/query">
  <quer:customValue>
    <quer:expression>rowNum</quer:expression>
  </quer:customValue>
</quer:projection>

In the URL when testing SSO, if something goes wrong you’ll get an errorReason=X, the reason codes are listed here:

Read More

A lot of times you need to make an update on a description or a text field. Let’s say you want to concatenate a new statement at the bottom for the requisition or template that specifies EEO compliance.

Now we all know what fun it is to try to manually do anything with those fields so I just say don’t do it.

Instead use Taleo GUI to craft what you are looking for in the filed you are looking to place it in within the staging zone (i.e. if you want change/add to JobInformation,DescriptionExternalHTML then create your content in the JobInformation,DescriptionExternalHTML field, although this isn’t needed it’s best practice down the road for the import, just trust me on this one)

So when you get your export it’s going to be the Taleo HTML that we all know and love, but how in the world are you supposed to get it into an export to update everything?

This is where our friend CDATA comes in. CDATA stands for Character Data and it means that the data in between these strings includes data that could be interpreted as XML markup, but should not be.

<quer:string>
<![CDATA[Taleo_HTML]]>
</quer:string>

You may also need to set the projectedValueType to string.

When testing before the standard login is shut off you may need to bypass which is such:

https://zone.taleo.net/smartorg/iam/accessmanagement/login.jsf?redirectionURI=https%3A%2F%2Fzone.taleo.net%2Fsmartorg%2FTaleoHomePage.jss&TARGET=https%3A%2F%2Fzone.taleo.net%2Fsmartorg%2FTaleoHomePage.jss