Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Engage/Sign/RemoteSigAsync.htm

## Capturing Asynchronous Remote Signatures for BRC Samples Using Share Link (Sign Later)

End users can send asynchronous remote signature requests for BRC samples, allowing HCPs to provide remote signatures for BRC samples at their convenience. This provides the flexibility of paper-based sampling with the speed, accuracy, and accountability of remote signature capture.

When asynchronous signature capture is enabled, the existing [Share Link remote signature capture](RemoteSigSampling.htm) functionality is replaced. To capture Share Link signatures immediately, users can create a signature request using the asynchronous Share Link method, then select the [Check for Signatures](#PendingSig) button without syncing. If the HCP provided a signature, users can review and accept the signature as usual.

Asynchronous remote signature capture is only supported for BRC products on person account calls or [unique activities](../../../Call_Reporting_2/Executing/Activities/UniqueActivities.htm) child calls.

**Who can use this feature?**

* Business Admin Users - Browser
* [Modify the signature request expiration period](#Modifying)
* [Define custom iOS sharing options](#Defining)
* End Users - iPad, iPhone
* [Use remote signature capture asynchronously for BRC Samples](#Using)
* [View pending signature requests](#PendingSig)
* [Cancel pending signature requests](#Canceling)
* [Review HCP signatures](#Reviewing)
* Engage System Users - Browser
* HCPs - Browser
* [Provide remote signatures asynchronously](#Providing)
* Users require an Engage license

### Configuring Capturing Remote Signatures Asynchronously for BRC Samples for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

To configure asynchronous remote signatures for business admins:

1. Ensure the following are complete:
   * [Configuring Engage Meeting](../ConfiguringEngage/ConfigureEngageMeeting.htm)
   * [Configuring Sample Requests (BRCs)](../../../CallSampling/Config/ConfiguringBRCs.htm)
   * [Capturing Remote Signatures for BRC Samples Using Share Link (Sign Now)](RemoteSigSampling.htm)
2. Configure the following optional functionalities:
   * Ensure [Displaying Country-Specific Disclaimers](../../../CallSampling/SignatureCapture/CountrySpecific.htm) is enabled if the disclaimer text should display in available languages
3. Navigate to **Admin > Users & Groups > Permission Sets**.
4. Select the permission set for the appropriate user profile.
5. Navigate to **Objects**.
6. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permissions |
   | --- | --- | --- | --- | --- |
   | account\_\_v | R | n/a | name\_\_v | Read |
   | call2\_\_v | n/a | n/a | signature\_request\_uuid\_\_v (optional) | Read |
   | engage\_link\_settings\_\_v | RE | n/a | * call\_sign\_request\_expiry\_period\_\_v * call\_sign\_share\_sheet\_\_v * engage\_link\_apps\_\_v | Edit |
   | sent\_message\_\_v | CRE | call\_sample\_\_v | * account\_\_v * call\_\_v * capture\_datetime\_\_v * engage\_link\_\_v * object\_type\_\_v * sent\_from\_platform\_\_v * sent\_via\_\_v * shortened\_engage\_link\_\_v * transaction\_type\_\_v * user\_\_v * vexternal\_id\_\_v | Edit |
   | signature\_request\_\_v | R | n/a | call2\_mobile\_id\_\_v | Edit |
   | * account\_\_v * call2\_\_v * call\_date\_\_v * engage\_last\_modified\_datetime\_\_v * modified\_date\_\_v * name\_\_v * owner\_\_v * object\_type\_\_v * request\_canceled\_datetime\_\_v * request\_expired\_date\_\_v * requested\_datetime\_\_v * signature\_accepted\_datetime\_\_v * signature\_captured\_datetime\_\_v * signature\_declined\_datetime\_\_v * signature\_request\_uuid\_\_v (optional) * status\_\_v | Read |
7. Navigate to **Admin > Configuration > Objects > Call (call2\_\_v) > Layouts**.
8. Place the **signature\_request\_uuid\_\_v** field on the call2\_\_v object layouts for troubleshooting or reporting purposes (optional).

   When unique activities are enabled, the signature\_request\_uuid\_\_v must be in the unique\_person\_fields\_vod\_\_c section or in an attendee-specific control section. For more information, see [Defining Child Only Fields](../../../Call_Reporting_2/Executing/Activities/UniqueActivities.htm#ChildOnly).
9. Navigate to **Admin > Configuration > Objects > Engage Link Settings (engage\_link\_settings\_\_v) > Layouts**.
10. Place the **call\_sign\_share\_sheet\_\_v** field on the appropriate layout.
11. Navigate to **Admin > Configuration > Objects > Signature Request (signature\_request\_\_v) > Layouts**.
12. Ensure fields on the **signature\_request\_\_v** layout are marked as read-only. Do not edit signature\_request\_\_v records directly. signature\_request\_\_v records should only be updated through the Engage integration or Veeva triggers.

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Engage System Users](#)

Engage System Users are created in Vault CRM instances and managed by Veeva for integration purposes. By default, these users are assigned the appropriate permission set. Customers cannot update the permission set.

To configure the Engage System User for Asynchronous Remote Signature capture, grant the system user Read permission for call2\_\_v object types used for capturing asynchronous remote signatures, and access to all user\_\_sys records:

* To grant Read permission for call2\_\_v object types, create a custom permission set and assign it to the Engage System User via an Application Role. See [Adding Permission Sets to Application Roles](https://platform.veevavault.help/en/gr/69197/#adding-permission-sets-to-application-roles) for more information.
* To ensure access to all user\_\_sys records, adjust any Sharing Rules implemented for the user\_\_sys object. See [System Owned Users in Vault CRM](../../../General/SystemUsers.htm) for more information.

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure asynchronous remote signatures for end users:

1. Ensure the following are complete:
   * [Configuring Sample Requests (BRCs)](../../../CallSampling/Config/ConfiguringBRCs.htm)
   * [Capturing Remote Signatures for BRC Samples Using Share Link (Sign Now)](RemoteSigSampling.htm)
2. Configure the following optional functionalities:
   * Ensure [Displaying Country-Specific Disclaimers](../../../CallSampling/SignatureCapture/CountrySpecific.htm) is enabled if the disclaimer text should display in available languages
3. Ensure [Creating Sample Transactions on Sign Save](../../../CallSampling/SubmitCallwSamples/SignSaveTransactions.htm) is not enabled. Creating Sample Transactions on Save is not supported in combination with asynchronous remote signature capture.
4. Navigate to **Admin > Users & Groups > Permission Sets**.
5. Select the permission set for the appropriate user profile.
6. Navigate to **Objects**.
7. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | call2\_\_v | CRED | All appropriate object types | signature\_request\_uuid\_\_v  Ensure this field is active for the appropriate object types. | Edit |
   | engage\_link\_settings\_\_v | R | n/a | * call\_sign\_request\_expiry\_period\_\_v * call\_sign\_share\_sheet\_\_v * engage\_link\_apps\_\_v | Read |
   | sent\_message\_\_v | CRE | call\_sample\_\_v | * account\_\_v * call\_\_v * capture\_datetime\_\_v * engage\_link\_\_v * object\_type\_\_v * sent\_from\_platform\_\_v * sent\_via\_\_v * shortened\_engage\_link\_\_v * transaction\_type\_\_v * user\_\_v * vexternal\_id\_\_v | Edit |
   | signature\_request\_\_v | R | call\_sample\_\_v | * modified\_date\_\_v * name\_\_v * signature\_request\_uuid\_\_v * status\_\_v | Read |
   | message\_\_v | n/a | R | user\_language\_code\_\_v | Read |
8. Navigate to **Business Admin > Objects > VMobile Object Configurations (vmobile\_object\_configuration\_\_v)**.
9. Ensure VMOCs are enabled for the following objects:
   * engage\_link\_settings\_\_v
   * signature\_request\_\_v
10. Remove the WHERE clause for **engage\_link\_settings\_\_v** VMOCs.

### Modifying the Signature Request Expiration Period as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

By default, pending signature requests remain active for seven days. To change the number of days a signature request link should remain active:

1. Navigate to **Business Admin > Engage Link Settings > Global Engage Link Settings (engage\_link\_settings\_\_v)**.
2. Edit the value in the **call\_sign\_request\_expiry\_period\_\_v** Engage Setting. Use an integer between one and fifteen.

When users create a signature request, an expiration date for the signature request is automatically calculated. The expiration date is the number of days in the call\_sign\_request\_expiry\_period\_\_v Engage Setting, plus the current date in Coordinated Universal Time (UTC), minus one day. For example, if you record a call at 5:00 PM on March 31 in the U.S. Pacific Time zone (12:00 AM on April 1 in UTC) and the call\_sign\_request\_expiry\_period\_\_v Engage Setting is set to 1, the signature request expires on April 1.

To ensure HCPs have adequate time to submit their signatures, requests expire in a batch job at 12 AM or 12 PM (UTC) on the day after the expiration date. After a batch job runs, up to 12 additional hours may pass before the next batch of signatures expires. The minimum time a signature request remains active is 24 hours.

### Defining Custom iOS Sharing Options as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

By default, end users on the iPad and iPhone platforms select from standard iOS sharing options when sharing asynchronous BRC signature links. Business admins can control which sharing options are available to end users and the order in which they display in a custom sharing modal.

To enable custom sharing options for users on the iPad and iPhone platforms:

1. Navigate to **Business Admin > Objects > Engage Link Settings (engage\_link\_settings\_\_v)**.
2. Select the appropriate **engage\_link\_settings\_\_v** record.
3. Populate the **call\_sign\_share\_sheet\_\_v** Engage Setting with the number 1.
4. Ensure the **engage\_link\_apps\_\_v** Engage Setting is populated with the ENGAGE\_LINK\_APPS Veeva Message.
5. Navigate to **Business Admin > Objects > Veeva Messages (message\_\_v) > ENGAGE\_LINK\_APPS**.
6. Edit the list in the **ENGAGE\_LINK\_APPS** Veeva Message to include the appropriate options in the desired order, separating each option using double semicolons. The following options are available for asynchronous BRC signature capture:
   * CopyURL - This also enables QR Code® functionality.
   * EngageChat - Ensure [Engage chat](../Connect/EngageTab.htm) is configured. When this sharing option is enabled, Engage Chat always displays first in the custom sharing modal.
   * LINE
   * LINEWORKS
   * Messages
   * QRCode
   * WhatsApp

Editing the list in the ENGAGE\_LINK\_APPS Veeva Message affects the sharing options for the following features, which also rely on this Veeva Message:

* [Scheduling and Starting Microsoft Teams Meetings](../Meet/MSTeams.htm)
* [Sending Engage Connection Invites to HCPs](../Connect/SendConnectionInvite.htm)
* [Sharing CLM Content via Web Link](../Share/ShareCLMLink.htm)
* [Presenting CLM Content Remotely](../Share/PresentRemotely.htm)

The engage\_link\_account\_selection\_\_v Veeva Setting is not respected for asynchronous BRC signature links, since the HCP signing for BRCs must be the account selected on the call report.

### Using Remote Signature Capture Asynchronously for BRC Samples as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To capture a remote signature asynchronously:

1. Create a call report with BRC samples. If any other sample or promotional product is on the call report, the Share Link signature capture option is not available.

   ![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/AddBRC.PNG)

   Signature capture must be required in order to use asynchronous remote signature capture. Asynchronous remote signature capture is not supported on calls where signature capture is optional or disabled.
2. Select the **Sign** button.

   ![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/SigSetup.png)
3. Select the disclaimer text language. This step is only available if [Displaying Country-Specific Disclaimers](../../../CallSampling/SignatureCapture/CountrySpecific.htm) is enabled.
4. Select **Share Link** for the Signature Method.

Only Share Link and QR Code® display as available signature methods on CRM Desktop (Windows).

5. Select **Next**.

   ![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/SelectApp.PNG)
6. Select the appropriate application to share the generated link with the HCP. If an acceptable application is not available, select Copy Link to copy the link to the device’s clipboard.

Once users share the link, the call report displays. Users do not need to remain in the Vault CRM application while waiting to capture the signature.

#### Capturing Asynchronous Signatures Using Custom iOS Sharing Options

When the call\_sign\_share\_sheet\_\_v Engage Setting is enabled, iPad and iPhone users select from custom sharing options defined in the ENGAGE\_LINK\_APPS Veeva Message, instead of selecting from standard iOS sharing options.

The following custom sharing options are available:

* Copy Link
* QR Code®
* Engage Chat
* LINE
* LINE WORKS
* Messages
* WhatsApp

When end users select a sharing option, a sent\_message\_\_v record is created with the following information:

| Field | Value |
| --- | --- |
| account\_\_v | The account requesting samples |
| call\_\_v | Reference to the associated call2\_\_v record. For unique activity group calls, this is the attendee child call for the account. |
| capture\_datetime\_\_v | The datetime at which the user selected the sharing option in the link sharing modal |
| engage\_link\_\_v | The signature request URL sent to the recipient |
| mobile\_id\_\_v | A system generated ID |
| object\_type\_\_v | call\_sample\_\_v |
| sent\_from\_platform\_\_v | The platform from which the link was shared:   * crm\_ipad\_\_v * crm\_iphone\_\_v |
| sent\_via\_\_v | The app used to share the link:   * copy\_url\_\_v * engage\_chat\_\_v * line\_\_v * lineworks\_\_v * messages\_\_v * qr\_code\_\_v * whatsapp\_\_v |
| shortened\_engage\_link\_\_v | The shortened signature request URL. This may be empty if the system fails to generate the shortened URL. |
| to\_\_v | The account phone number or ID of the app where the link is shared. This field is only populated if an account phone number or app ID is available when the user selects a sharing option. |
| user\_\_v | Reference to the user who sent the message |
| vexternal\_id\_\_v | The unique identifier for the shortened URL |

### Viewing Pending Signature Requests as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

A yellow banner displays on the Sample and Promotional Items section of the call report to highlight pending signature requests. To check whether the HCP has submitted a signature, select the **Check for Signature** link from the blue banner.

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/PendingRequest.png)

For call reports with pending signature requests, users cannot:

* Submit the call report
* Delete the call report
* Capture another signature for the same call using a different method—for example, QR Code® signature request
* Edit fields related to sampling and BRCs, or fields placed in the sample and promotional items section. When there is a pending signature request, fields related to [signature capture and sampling](../../../CallSampling/SignatureCapture/SigCap.htm) are read-only.

Users cannot delete or submit [unique activities](../../../Call_Reporting_2/Executing/Activities/UniqueActivities.htm) group calls where one or more of the child calls have a pending request. Signature request status displays in the attendee section for each attendee.

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/Copy of UAcalll.PNG)

### Canceling Pending Signature Requests as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

Users can cancel pending signature requests until the HCP provides a signature. To cancel a pending request, select **Cancel Request** from the yellow signature request banner and confirm the cancellation.

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/PendingRequest.png)

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/ConfirmCancel.PNG)

### Providing Remote Signatures Asynchronously as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)HCPs](#)

HCPs receive the remote signature request link through the application the end user selected. Selecting the link opens an internet browser, where the signer can review the BRC details and submit their signature. The signature\_captured\_datetime\_\_v field on the signature\_request\_\_v object is set to the date and time when the HCP selects the Accept button on the signature capture screen.

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/HCPSamplesReview.png)

![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/HCP3.png)

### Reviewing HCP Signatures as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

When HCPs submit their signatures, users receive an email that notifying them a signature is ready for review. There is no time limit for accepting a signature. Users can accept the signature at any time after the HCP provides it.

To review and accept HCP signatures:

1. Navigate to the call report.

   ![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/SignatureReady.png)
2. Select **Review Signature**. The signature review screen displays.

   ![](../../../../Resources/Images/Activities/CallReporting/CallReportSampling/Advanced/AsyncBRC/ReviewSignature.png)
3. Select **Accept**.

To ensure accurate, compliant signature capture data, the following occurs when users accept a signature:

* The signature\_request\_\_v record is updated to a Signature Accepted status
* The Signature Accepted Datetime field is populated with the current date and time
* [Signature capture information](../../../CallSampling/SignatureCapture/SigCap.htm) is locked on the call2\_\_v record
* The signature\_captured\_share\_link\_\_v field is stamped on call2\_\_v, and sample\_order\_transaction\_\_v records. For more information on signature\_captured\_share\_link\_\_v, see [Reviewing Remote Signatures](RemoteSigSampling.htm#Reviewing).

For asynchronous signature capture, sample and product limits are recalculated when users accept the HCP’s signature. When [Creating Sample Transactions on Sign Save](../../../CallSampling/SubmitCallwSamples/SignSaveTransactions.htm) is enabled and users save the call report, the lot quantity, sample and product limits, and sample transaction records are only updated if there is a captured signature on the call report.

If users do not want to accept the submitted signature, the following options are available:

* Cancel - Cancels the submitted signature. The HCP’s signature is not saved to the call report. To capture the HCP’s signature, the user must generate a new signature request link. For example, Dr. Ackerman contacts Sarah Jones after he submits his signature and asks her to send fewer Cholecap BRCs than he signed for. Sarah cancels the submitted signature and creates a new signature request with Dr. Ackerman’s preferred quantity of BRCs.
* Review Later - Return to the call report without canceling or accepting the signature. The HCP signature remains available for the user to review and accept.
* Request Again - Generates a new signature request link for the user to share

### Related Topics

[Capturing Remote Signatures for BRC Samples Using Share Link (Sign Now)](RemoteSigSampling.htm)

[Capturing Remote Signatures for BRC Samples During Engage Meetings](RemoteSig.htm)

[Capturing Electronic Signatures for Sampling](../../../CallSampling/SignatureCapture/SigCap.htm)