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.
Legacy Onboarding Data Extraction - Best Practice for capturing eSignatures when they are passwords
Content
We are working on extraction of Legacy Onboarding Data that were part of User-defined forms that will be gone at the end of the year. As part of our extraction, we are capturing data around the Electronic Signature (eSignature). In our case these forms the eSignature was candidate’s password.
When we extract the data for this field’s it scrambled/encrypted. I know this is expected behavior, considering we can’t see it in reporting or through the user interface. That said, we are interested in knowing what your other are doing (or have done) to deal with this? Are you still extracting the encrypted signature as proof or are you relying on other field(s) like IP Address? Below is a fake example .
Tagged:
0