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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Document of Record E-Signature Validation
Summary:
Document of Record E-Signature Validation
Content (please ensure you mask any confidential information):
Hi,
We have setup one Journey with Task Type as Document of Record with E-Signature (Type = Native) validation. The configuration is working as expected. The DOR is getting created for employee after completion of task.
Need two clarifications on DOR parameter.
1) User details are getting validated against 'Display Name' and 'Password' field data entered by user. Both details have to be correct to generate signed DOR. But Email details are not validated. Here only syntax is validated. If user enters incorrect email address then also signed doc gets generated. So, What is the purpose of this email field here?
0