You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

{Requisition.LocationStructure} variable in Taleo 12B

edited Jan 8, 2013 4:53AM in Taleo Enterprise

Content

Hello.  Does anyone know of an alternative to the {Requisition.LocationStructure} variable in Taleo 12B that could be used in correspondences instead to make the location information populate in a more user friendly manner?  This variable has the information displayed as a long string complete with arrows in between each part (Country>State>City>Work Location).  So for example, in one of our decline correspondences, the location information for our Chicago office is presented to the candidate as:  United States>Illinois>CHICAGO_IL>Chicago:8410 W Bryn Mawr Ste 700. 

Obviously, this looks a little strange when presented in a correspondence.  I haven't been able to find any other variables that can be used and have asked the question to Oracle.  But I'm curious if any other clients have been concerned about this.  Currently, our recruiters are manually editing the correspondences to make it look like you would expect a street address to look.  Thank you in advance for any thoughts or ideas.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!