Mandatory Native eSignature Signing Pad

You now have to electronically sign on the signature pad in a Native eSignature task to mark the task as done. The Done button is enabled only when you sign in the signature pad.

Done Button Disabled Until You Electronically Sign

Done Button Enabled After You Sign

This feature ensures that users sign off to prevent legal complications with a policy document not containing a signed acknowledgement. Also, some documents need to be electronically signed without just entering the display name.

Steps to Enable

To make the signature pad as a required field, refer to this topic: How do I make the signature pad mandatory for a native eSignature task?

Key Resources

For more information about journeys, refer to the Implementing and Using Journeys guide on Oracle Help Center.

Access Requirements

This table shows the duty, aggregate, and functional privileges that support this feature and the predefined roles that inherit them:

Job Role	Duty Privilege	Aggregate and Function Privilege
Human Resource Specialist	ORA_PER_JOURNEY_BUILDER_DUTY Journey Builder Duty	ORA_PER_MANAGE_JOURNEY_TEMPLATE Manage Journey (Aggregate Privilege) PER_MANAGE_JOURNEY_INTEGRATIONS Manage Journey Integrations (Function Privilege)

If you are using the predefined roles, no action is necessary. However, if you are using custom versions of these roles, you must add these aggregate privileges to your custom roles to use this feature. See the Release 13 Oracle Human Capital Management Cloud Security Upgrade Guide on My Oracle Support (Document ID 2023523.1) for instructions about implementing new functions in existing roles. If you are using Cloud My Oracle Support (CMOS), you can search for the document by using the ID KB30912.

For information about existing security privileges, refer to the Security Reference for Common Features guide on the Oracle Help Center.