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.

HCM Communicate - Token with Known As

We need to have a token for 'Known As' in Communicate, and if there is no 'Known As' filled, it should use 'First_Name'. Alternatively, this condition can be handled directly in the 'First_Name' token, prioritizing 'Known As' and defaulting to 'First_Name' if 'Known As' is not available.
This customer values diverse communication practices and prefers using only first names in their email communications. Using the "Full_Name" works because it shows the Display Name in the message (Display Name is configured to exhibit "Known As" OR "First Name" + "Last Name"). But using the First Name token it shows their birth name.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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