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.

Inserting fields into Journey Documents, not organic to Oracle provided XML

edited Aug 29, 2023 9:08AM in Journeys 2 comments

Summary:

I have received requests to insert HCM content into journey documents that are not part of the sample XML file provided by Oracle. Curious to know if others have successfully done this and if so - any tips to share?

Content (required):

I have received a couple of requests to create journey documents that would require eSignature, where the document would need to include detail from the existing PERSON file or the PERSON OFFER such as:

  • Emergency Contact First Name
  • Emergency Contact Last Name
  • Sign On Bonus
  • etc.

Per SR, I've been informed this isn't possible. Wondering if anyone has found a way around this?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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