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

Native Electronic Signature - Physical Signature parameter

edited May 3, 2024 5:04AM in Journeys 8 comments

Summary:

For the physical signature support feature in 24B

Is there a specific parameter which needs to be provided in the Report path of the task configuration ( on the lines of P_SIGNER_NAME / P_SIGN_DATE ) so that the physical signature entered in the signature pad can be rendered on the generated pdf? The assumption is this parameter which will have to be used on the RTF so that the physical signature gets stored in the generated pdf DoR.

The 24B documentation does not list out the details regarding this, how the physical signature from the signature pad is to be passed on to the report.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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