# Managing Object eSignatures eSignatures provide a way for users to complete tasks and sign electronic records. You can enable eSignatures on an object to capture relevant details, including the _Signature Name_, _Signature Time_, and _Signature Meaning_, in a related list on the object record detail page. Vault captures these details when a user provides an eSignature through an object workflow. When you enable eSignatures on an object, Vault creates a related read-only _eSignature_ child object based the _eSignature_ object class. This adds an eSignature related list to the object's page layout. Note that you cannot disable eSignatures on an object if there is at least one eSignature record or references to the _eSignature_ object.
## About the eSignature Object Class Vault now manages eSignatures with the _eSignature_ object class to capture eSignatures on object records. When a user provides an eSignature, Vault creates a related _eSignature_ object record with the following fields:
Field Name Description
Name Vault-generated name for the object record
User ID (Hidden) The unique Vault identifier
Signature Name The first and last name of the signer at the time of signing
Signature Title The title of the signer at the time of signing
User Name The unique user name of the signer in Vault
Signature Time The date and time the signature was captured
Signature Meaning The capacity value the signer selected when completing an eSignature object workflow task
Verdict The object workflow task verdict label associated with the eSignature
Task Name The name of the object workflow task associated with the eSignature record
Workflow Name The name of the object workflow associated with the eSignature record
Parent The parent object record that was signed
Workflow Task ID The unique ID for the associated workflow task instance
Workflow Process ID The unique ID for the associated workflow process instance
Delegate Title The title of the delegate user at the time of signing; only captured for signatures completed by delegate users
Delegate Name The first and last name of the delegate user at the time of signing; only captured for signatures completed by delegate users
Delegate User The delegate user object record; only captured for signatures completed by delegate users
## Enabling eSignatures To enable eSignatures on a specific object: 1. Navigate to **Admin** > **Configuration** > **Objects** > **[Object]**. 2. Click **Edit** from the Details tab. 3. Select the **Enable eSignatures** checkbox. 4. Click **Save**.
## Defining Signature Types {#signature-types} After you enable eSignatures on a specific object, Vault automatically creates a _Signature Type_ picklist for that object. For example, if you enabled eSignatures on the _Product_ object, Vault creates a _Product Signature Type_ picklist. This picklist enables you to select a signature type when configuring an eSignature as part of a workflow task. You can add values to this picklist from the **Business Admin > Picklists > [Object] Signature Type** page. ## Configuring eSignatures in Object Workflows You can add an eSignature prompt to an object workflow task or a verdict to capture a user's eSignature as part of the workflow task. When you set up eSignatures in a workflow task, you can select the **Signature Type**. You'll need to define signature types (as described above) to select an option in this picklist. You can also define a workflow action step to automatically remove eSignatures from object records under certain conditions or upon workflow cancelation. ## Viewing Object eSignatures When a user completes an eSignature, Vault captures and stores its details in an object record. You can view eSignature records in a related list on the parent object record detail page. Additionally, you can click the eSignature record to view its details. ## Configuring to Make eSignatures Obsolete {#configuring-to-make-esignatures-obsolete} In some cases, captured eSignatures may no longer be relevant to your current process and need to be updated. You can configure the **Make signature records obsolete** object lifecycle entry action for each lifecycle state to determine when an eSignature records are out of date. When you configure this entry action, you use the **Preserve these signature types** drop-down to select all _Signature Types_ (described above) that are still valid in this state. When the object record moves to this lifecycle state, Vault checks its related eSignature records. Any eSignature records with a _Signature Type_ that you didn't preserve will move to the _Obsolete_ state automatically. ## Deleting Records & Related Signatures When eSignatures are enabled on an object, you can't delete a parent object record if it has related _eSignature_ records. Instead of manually deleting each child _eSignature_ record, you can enable a user action that allows users to delete a parent record and all related _eSignature_ records at once. ### Enabling the User Action The action to delete a parent record and its related _eSignature_ records is automatically available in Vault. To enable it, navigate to **Admin > Configuration > Objects > [Object] > Actions**. Select the **Delete Record and Related Signatures** action and set the **Status** to **Active**. You can also configure Atomic Security to control who can view and execute the action by lifecycle state and role. Learn more about configuring Atomic Security on object actions. If you disable eSignatures for the parent object, the action won't display in a parent record's **Actions** menu. ### Deleting eSignatures Once enabled, users with the _Delete_ permission on the parent object can select the **Delete Record and Related Signatures** action from the record's **Actions** menu. Vault automatically deletes the parent record and all related _eSignature_ records. ## Known Issue for Records in the Inactive State There is a known issue where completing a workflow task with an eSignature on a record in the _Inactive_ state causes an error.