Inserting fields into Journey Documents, not organic to Oracle provided XML
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:
0