Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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.

Fluid - Use Current Date variable instead of Offer Extend date

edited Jul 8, 2020 7:33AM in Taleo Enterprise 3 comments

Content

Hi,

We are currently using the variable {Offer.ExtendDate} to capture the date of offer extension in offer letter. This works fine in Legacy recruiting, where warning message is displayed about unresolved variable before offer is extended, recruiter can ignore the warning, extend the offer letter and extension date gets populated after the offer is extended.

 

However in fluid recruiting, recruiter will not be able to extend offer with unresolved variable. Please let me know if you have come across this issue.

I have tested the following scenario using {Other.CurrentDate} instead of  {Offer.ExtendDate}:

  • Offer created and extended on Day 1. Candidate views the offer on Day 2. The date in offer letter is Day 1 as expected

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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