Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/CallSampling/ShipBRC/CaptureAOC.htm

## Capturing Acknowledgement of Content

To ensure HCPs receive the products or sample requests/BRCs they ordered, users capture Acknowledgement of Content (AOC) signatures for products shipped directly to healthcare practitioners from a warehouse facility. Once a product request is initiated, typically through sample request/BRC products on calls, the sample or sample order records are sent to a fulfillment vendor. When the product is shipped, this information is loaded in to Vault CRM to begin the AOC process.

#### Validation Disclaimer

Call Sampling features in the 24R2.2 release are released without validation. Call Sampling requires enablement and does not affect other Vault CRM functionality. Call Sampling features were extensively tested by our QA team during the development and release process and will go through validation at a later date.

**Who can use this feature?**

* End Users — iPad
* [Capturing Signatures for AOC](#Capturin)
* Sample Admin Users — Browser
* [Manually Submitting AOC Signatures](#Manually)
* [Unlocking Completed AOC Records](#Unlockin)
* Users do not require an additional license

### Configuring Acknowledgement of Content for

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

To configure this feature for sample admin users:

1. Ensure the following configuration is complete:

   * [Configuring Call Sampling](../Config/ConfiguringCS.htm)
   * [Displaying the My Alerts Component](../../Getting_Started/MobileDeviceSetup/iOS/HomepageComponents/AlertsComponent.htm) (optional; for My Alerts entry point)
2. Navigate to **Admin > Users & Groups > Objects > Permission Sets**.
3. Select the appropriate permission set.
4. Grant sample admin users the following additional permissions:

   | Object | Object Permission | Object Types | Field | Field Permission |
   | --- | --- | --- | --- | --- |
   | content\_acknowledgement\_\_v | CRED | call\_\_v | * account\_\_v * alert\_created\_\_v * alert\_duration\_\_v * aoc\_due\_date\_\_v * call\_reference\_\_v * call\_text\_\_v * content\_acknowledgement\_status\_\_v * create\_alert\_\_v * created\_by\_\_v * created\_date\_\_v * credentials\_\_v * delivery\_date\_\_v * disclaimer\_\_v * external\_id\_\_v * global\_id\_\_sys * id * legacy\_crm\_id\_\_v * lifecycle\_\_v * mobile\_id\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v * not\_received\_\_v * object\_type\_\_v * order\_id\_\_v * ownerid\_\_v * received\_by\_\_v * received\_by\_firstname\_\_v * received\_by\_lastname\_\_v * received\_by\_middle\_\_v * received\_title\_\_v * request\_receipt\_\_v * ship\_address\_\_v * ship\_address\_line\_1\_\_v * ship\_address\_line\_2\_\_v * ship\_assmca\_\_v * ship\_cds\_\_v * ship\_city\_\_v * ship\_country\_\_v * ship\_date\_\_v * ship\_dea\_\_v * ship\_license\_\_v * ship\_location\_\_v * ship\_state\_\_v * ship\_state\_distributor\_\_v * ship\_zip\_4\_\_c * ship\_zip\_\_v * signature\_\_v * signature\_date\_\_v * state\_\_v * status\_\_v * unlock\_\_v | Edit |
   | * link\_\_sys * stage\_\_sys * state\_stage\_id\_\_sys | Read |
   | content\_acknowledgement\_item\_\_v | CRED | call\_\_v | * account\_\_v * aoc\_signature\_date\_\_v * content\_acknowledgement\_\_v * created\_by\_\_v * created\_date\_\_v * distributor\_\_v * external\_id\_\_v * id * legacy\_crm\_id\_\_v * lifecycle\_\_v * lot\_\_v * manufacturer\_\_v * mobile\_id\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v * object\_type\_\_v * product\_\_v * product\_name\_\_v * received\_quantity\_\_v * ship\_quantity\_\_v * state\_\_v * status\_\_v * tracking\_\_v * u\_m\_\_v | Edit |
   | * global\_id\_\_sys * link\_\_sys * stage\_\_sys * state\_stage\_id\_\_sys | Read |
5. Navigate to **Admin > Users & Groups > Permission Sets.**
6. Select the appropriate permission set.
7. Navigate to  **Objects > content\_acknowledgment\_\_v > Object Action Permissions**.
8. Grant sample admin users Execute access to the **aoc\_unlock\_\_v** action on the content\_acknowledgement\_\_v object.
9. Navigate to **Admin > Configuration > Tabs**.
10. Create a tab for the **content\_acknowledgement\_\_v** object and grant sample admin users access to the tab.

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

To configure this feature:

1. Ensure the following configuration is complete:

   * [Configuring Call Sampling](../Config/ConfiguringCS.htm)
   * [Displaying the My Alerts Component](../../Getting_Started/MobileDeviceSetup/iOS/HomepageComponents/AlertsComponent.htm) (optional; for My Alerts entry point)
2. Navigate to **Admin > Users & Groups > Objects > Permission Sets**.
3. Select the appropriate permission set.
4. Grant end users the following additional permissions:

   | Object | Object Permission | Object Types | Field | Field Permission |
   | --- | --- | --- | --- | --- |
   | content\_acknowledgement\_\_v | RE | call\_\_v - Read and Edit access only | * content\_acknowledgement\_status\_\_v * disclaimer\_\_v * not\_received\_\_v * received\_by\_\_v * received\_by\_firstname\_\_v (optional; needed for FDA sample transparency reporting requirements) * received\_by\_lastname\_\_v (optional; needed for FDA sample transparency reporting requirements) * received\_by\_middle\_\_v (optional; needed for FDA sample transparency reporting requirements) * received\_title\_\_v * request\_receipt\_\_v * signature\_\_v * signature\_date\_\_v | Edit |
   | * account\_\_v * alert\_created\_\_v * alert\_duration\_\_v * aoc\_due\_date\_\_v * call\_reference\_\_v * call\_text\_\_v * create\_alert\_\_v * created\_by\_\_v * credentials\_\_v * delivery\_date\_\_v * external\_id\_\_v * global\_id\_sys * id * legacy\_crm\_id\_\_v * lifecycle\_\_v * link\_\_sys * mobile\_id\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v * object\_type\_\_v * order\_id\_\_v * ownerid\_\_v * ship\_address\_\_v * ship\_address\_line\_1\_\_v * ship\_address\_line\_2\_\_v * ship\_cds\_\_v * ship\_city\_\_v * ship\_country\_\_v * ship\_date\_\_v * ship\_dea\_\_v * ship\_license\_\_v * ship\_location\_\_v * ship\_state\_\_v * ship\_state\_distributor\_\_v * ship\_zip\_4\_\_v * ship\_zip\_\_v * stage\_sys * state\_\_v * state\_stage\_id\_sys * status\_\_v | Read |
   | content\_acknowledgement\_item\_\_v | RE | call\_\_v - Read and Edit access only | received\_quantity\_\_v | Edit |
   | * account\_\_v * aoc\_signature\_date\_\_v * content\_acknowledgement\_\_v * created\_by\_\_v * created\_date\_\_v * distributor\_\_v * external\_id\_\_v * global\_id\_\_sys * id * legacy\_crm\_id\_\_v * lifecycle\_\_v * link\_\_sys * lot\_\_v * manufacturer\_\_v * mobile\_id\_\_v * modified\_by\_\_v * modified\_date\_\_v * name\_\_v * object\_type\_\_v * product\_\_v * product\_name\_\_v * ship\_quantity\_\_v * stage\_\_sys * state\_\_v * state\_stage\_id\_\_sys * status\_\_v * tracking\_\_v * u\_m\_\_v | Read |
5. Create content acknowledgement and content acknowledgement item layouts using the call\_\_v object type:
   * Navigate to **Admin > Configuration > Objects > content\_acknowledgement\_\_v > Layouts**
   * Create **content\_acknowledgement\_layout\_\_v** layouts using the call\_\_v object type on the content\_acknowledgement\_\_v object
   * Navigate to **Admin > Configuration > Objects > content\_acknowledgement\_item\_\_v > Layouts**
   * Create **content\_acknowledgement\_item\_layout\_\_v** layouts using the call\_\_v object type on the content\_acknowledgement\_item\_\_v object
6. Place the **Content Acknowledgements** related object section on Person Account layouts (optional; enables accessing AOC from an individual AOC record detail page):
   * Navigate to **Admin > Configuration > Objects > account\_\_v > Layouts**
   * Place the **Content Acknowledgements** related object section on layouts for Person Account object types
7. Navigate to **Business Admin > Objects > VMobile Object Configurations**.
8. Activate **content\_acknowledgement\_\_v** VMOCs for the appropriate mobile platforms.

   VMOCs for the content\_acknowledgement\_item\_\_v object are not needed, as long as the Content Acknowledgement Item (Samples Ordered) related object section is included on Content Acknowledgement layouts. This section is included on Content Acknowledgement layouts by default.
9. Restrict which product types may be added as content acknowledgment items (optional). By default, any type of product may be added as a content acknowledgment item.
   * Navigate to **Admin > Configuration > Objects > content\_acknowledgement\_item\_\_v**
   * Edit the **product\_\_v** lookup field on the content\_acknowledgement\_item\_\_v object to include only the appropriate product types
     ![](../../../Resources/Images/SampleManagement/AOC/ProductRestriction.png)
10. Navigate to **Admin > Configuration > Objects**.
11. Select the **Do not copy this field in Copy Record** checkbox to prevent field values from being copied across records, for fields on any object (optional). Selecting the checkbox for a field ensures the field values are not copied when users clone records. By default, the following fields are not copied:
    * content\_acknowledgment\_\_v object:
    * content\_acknowledgement\_status\_\_v
    * signature\_\_v
    * signature\_date\_\_v
    * disclaimer\_\_v
    * received\_by\_\_v
    * received\_title\_\_v
    * request\_receipt\_\_v
    * received\_by\_firstname\_\_v
    * received\_by\_middle\_\_v
    * received\_by\_lastname\_\_v
    * not\_received\_\_v
    * content\_acknowledgment\_item\_\_v object:
    * product\_name\_\_v
    * received\_qty\_\_v

    ![](../../../Resources/Images/SampleManagement/AOC/DoNotCopy.png)

#### Enabling AOC Home Page Alerts

To notify end users when AOC records are due for signature capture, enable home page alerts:

1. Navigate to **Admin > Operations > Job Definitions**.
2. Select **Create**.
3. Enter the following information:
   * Title - Create Content Acknowledgement Alerts
   * Name - create\_content\_acknowledgement\_alerts\_\_c
   * Status - Active
   * Type - SDK Job
   * Job Owner - Appropriate user owner or group
   * Schedule - Appropriate frequency for the job to run
   * Vault Time - Appropriate time for the job to begin
   * Job - com.veeva.vault.app.vaultcrm.core.contentacknowledgement.jobs.CreateContentAcknowledgementAlertsJob (Create Content Acknowledgement Alerts)
![](../../../Resources/Images/SampleManagement/AOC/AOCJob.png)4. Select **Save**.
5. Navigate to **Business Admin > Objects > content\_acknowledgement\_\_v**.
6. Select the checkbox for the **create\_alert\_\_v** field on the appropriate content\_acknowledgement\_\_v records to automatically create alerts for users when an AOC is due.
7. Enter the desired number of days for the alert to remain active in the **alert\_duration\_\_v** field on the content\_acknowledgement\_\_v record. The alert\_duration\_\_v field determines how long AOC alerts created via the create\_alert\_\_v checkbox display. If AOC home page alerts are enabled, the alert\_duration\_\_v field must be populated.
   ![](../../../Resources/Images/SampleManagement/AOC/CreateAlert1cropped.png)

#### Modifying the AOC Due Date

By default, the AOC due date is set to the date the order shipped, plus 14 days. When the due date is reached, a red notification bubble displays on the Acknowledgement of Content item in the All Actions menu. To modify the AOC due date for end users, edit the formula in the aoc\_due\_date\_\_v field on the content\_acknowledgement\_\_v object. For example, to set a due date that is seven days after the order ship date, edit the formula to read: ship\_date\_\_v + 7.

![](../../../Resources/Images/SampleManagement/AOC/AOCDueDate.png)

#### Additional Configuration for Custom Layouts

When creating custom layouts for content acknowledgment, complete the following additional configuration:

1. Navigate to >**Admin > Configuration > Objects > content\_acknowledgement\_\_v > Layouts.**
2. Select the appropriate layout.
3. Select **Layout Rules > Create**.
   ![](../../../Resources/Images/SampleManagement/AOC/LayoutRule1.png)
4. Create a layout rule to make the **content\_acknowledgement\_status\_\_v** field required:
   * Populate the IF this Layout Rule Expression is TRUE box with the expression 'true'
   * Apply the following display effects for the layout rule:
   * Effect: Display as required
   * Type: Field
   * Value: content\_acknowledgement\_status\_\_v
5. Create a layout rule to make the **signature\_date\_\_v** field read-only:
   * Populate the IF this Layout Rule Expression is TRUE box with the expression 'true'
   * Apply the following display effects for the layout rule:
   * Effect: Display as read-only
   * Type: Field
   * Value: signature\_date\_\_v

   ![](../../../Resources/Images/SampleManagement/AOC/LayoutRuleAfter1.png)
6. Create a layout rule to make **Received By fields** read-only, once a signature is captured:
   * Populate the IF this Layout Rule Expression is TRUE box with the expression 'Not(IsBlank(signature\_date\_\_v))'
   * Apply the following display effects for the layout rule:
   * Effect: Display as read-only
   * Type: Field
   * Value: received\_by\_\_v, received\_by\_middle\_\_v, received\_by\_lastname\_\_v, received\_by\_firstname\_\_v, received\_title\_\_v

   ![](../../../Resources/Images/SampleManagement/AOC/LayoutRuleAfter2.png)
7. Navigate to **Admin > Configuration > Objects > content\_acknowledgement\_item\_\_v > Layouts.**
8. Select the appropriate layout.
9. Select **Layout Rules > Create**.
   ![](../../../Resources/Images/SampleManagement/AOC/LayoutRule3.png)
10. Create a layout rule to make the **product\_\_v** field required:
    * Populate the IF this Layout Rule Expression is TRUE box with the expression 'true'
    * Apply the following display effects for the layout rule:
    * Effect: Display as required
    * Type: Field
    * Value: product\_\_v

    ![](../../../Resources/Images/SampleManagement/AOC/Copy of ContentAcknowledgmentItemLayoutRule2.png)
11. Create a layout rule to make the **received\_quantity\_\_v** field read-only, once a signature is captured:
    * Populate the IF this Layout Rule Expression is TRUE box with the expression 'Not(IsBlank(aoc\_signature\_date\_\_v))
    * Apply the following display effects for the layout rule:
    * Effect: Display as read-only
    * Type: Field
    * Value: received\_quantity\_\_v

    ![](../../../Resources/Images/SampleManagement/AOC/Copy of ContentAcknowledgmentItemLayoutRule1.png)

### Capturing Signatures for AOC as

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

Users can access AOC signature pages from the following entry points:

* Account Detail
* Call Reports
* My Alerts
* Acknowledgment of Content record detail

When accessing AOC from Account Detail, Call Reports, or My Alerts, all overdue AOC are available.

#### Accessing Acknowledgment of Content from Account Detail

When an AOC record is due for signature capture, a red indicator displays under the All Actions menu on the HCP’s Account Detail page.

To access AOC from the Account Detail page:

1. Select the **All Actions** menu in the upper corner.
   ![](../../../Resources/Images/SampleManagement/Advanced/AOCDetailAlert.PNG)
2. Select the **Acknowledgement of Content** option.

#### Accessing Acknowledgment of Content from the Call Report

On the call report, the Acknowledgment of Content option only displays in the All Actions menu when there is at least one overdue AOC record for the current user and account. AOC status is re-evaluated each time the user opens or edits the call report.

When an AOC record is overdue for signature capture, a red indicator displays on the Acknowledgment of Content option under the All Actions menu on the call report. For unique activity group calls, the indicator displays on child calls only.

AOC signature capture from the call report is only supported on individual calls or unique activity group calls. It is not supported for standard group calls.

To access AOC from the call report:

1. Select the **All Actions** menu on the call report.

   ![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/CallReport1.PNG)
2. Select the **Acknowledgement of Content** option.

#### Accessing Acknowledgment of Content from My Alerts

If the [My Alerts](../../Getting_Started/MobileDeviceSetup/iOS/HomepageComponents/AlertsComponent.htm) widget is configured and the Create Content Acknowledgement Alerts batch job is enabled, AOC alerts also display in the My Alerts widget on the home page. Home page AOC alerts only display for content\_acknowledgement\_\_v records where the user is the record owner.

To access AOC from My Alerts:

1. Select the **My Alerts widget**.
2. Select the record link from the appropriate AOC alert in the My Alerts list.![](../../../Resources/Images/SampleManagement/Advanced/AocRecordStep2.png)
3. Select the **Sign** icon.

#### Accessing Acknowledgment of Content from the Record Detail

Users can capture Acknowledgment of Content from record detail pages, wherever the Content Acknowledgements related object section is available on a layout.

To access AOC from a record detail page:

1. Navigate to an **Content Acknowledgements** related object section.

   ![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/ContentAcknowledgmentSection.PNG)
2. Select an **Acknowledgment of Content** record from the list.

   ![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/CADetail.PNG)
3. Select the **Sign** icon.

#### Capturing the Recipient Signature

After accessing Acknowledgment of Content from any one of the available entry points, the AOC signature page displays.

![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/SigPage.png)

If more than one AOC record requires a signature, the signature page for the oldest AOC by ship date is displayed first. If a [signature disclaimer](../SignatureCapture/SigDisclaimer.htm) is configured, the disclaimer displays on the signature page as usual.

On the AOC signature page, the following fields default to the account name and credentials from the corresponding account\_\_v record:

* received\_by\_\_v
* received\_by\_middle\_\_v
* received\_by\_firstname\_\_v
* received\_by\_lastname\_\_v
* received\_title\_\_v

The received\_quantity\_\_v field defaults to the ship\_quantity\_\_v field value from the content\_acknowledgment\_item\_\_v record. Users can edit these fields on the signature page until the AOC recipient’s signature is captured.

When the AOC information is correct, select the Accept action to accept the signature and lock the AOC signature record. If there are additional AOC records which require signatures, the signature page for the next-oldest AOC by ship date automatically displays after signature capture.

When users accept an AOC signature, the AOC record status is updated to completed\_\_v and the corresponding AOC alert no longer displays. Once the content\_acknowledgement\_status\_\_v and lifecycle\_state\_\_v fields are set to completed\_\_v, or the signature\_date\_\_v field is populated on a content\_acknowledgment\_\_v record, users cannot:

* Edit or delete the content\_acknowledgment\_\_v record and related content\_acknowledgment\_item\_\_v records
* Add content\_acknowledgment\_item\_\_v records to the content\_acknowledgment\_\_v record

#### Editing the Received Quantity

If the actual received quantity differs from the expected quantity, select the edit icon next to the received\_quantity\_\_v field. A keypad and case calculator display. Enter the appropriate quantity, then select Save.

![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/CaseCalculator.PNG)

#### Marking a Shipment as Not Received

To mark a shipment that was not received:

1. Select the **not\_received\_\_v** checkbox on the AOC signature page. When users select the not\_received\_\_v checkbox for an AOC, the received\_quantity\_\_v field for all line items on the AOC record is set to 0 and the not\_received\_\_v field is marked on the AOC record.
   ![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/SampleNotReceived.PNG)
2. Capture the expected recipient’s signature.
3. Select **Accept**.

#### Editing the AOC Recipient

If the HCP who ordered the shipment did not personally receive the package, users must edit the signature page to reflect the actual shipment recipient—for example, an office manager or front desk staff member. To edit the AOC recipient:

1. Select the edit icon in the AOC recipient row.
2. Enter the new recipient’s first name, last name, and title.
   ![](../../../Resources/Images/Activities/CallReporting/CallReportSampling/AOC/Copy (1) of AOCEditReceiver.PNG)
3. Select **Save**.

### Manually Submitting AOC Signatures as

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

If AOC signatures are captured on paper or outside of Vault CRM—for example, through a fax back process—sample admin users must update the AOC record’s content\_acknowledgement\_status\_\_v field to completed\_\_v. Otherwise, AOC alerts continue to display to users. Sample admin users can update the content\_acknowledgement\_status\_\_v field on AOC records manually or via data load to the content\_acknowledgement\_\_v object.

### Unlocking Completed AOC Records as

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

To unlock a completed AOC record as a sample admin:

1. Navigate to **Business Admin > Objects > content\_acknowledgement\_\_v**.
2. Select the appropriate record.
   ![](../../../Resources/Images/SampleManagement/AOC/Unlock1.png)
3. Select the **Unlock** action from the All Actions menu. This reverts the record to the Unlocked lifecycle state, so it is editable.

    ![](../../../Resources/Images/SampleManagement/AOC/Unlock2cropped.png)

   The Unlock action only displays for users with edit field permission to the unlock\_\_v field and view access to the unlock\_\_v object action on the content\_acknowledgement\_\_v object, when the record is in completed status and the lifecycle state is completed\_\_v. Only sample admin users should have access to the unlock\_\_v field on the content\_acknowledgement\_\_v object.

   A signed AOC record or an AOC record with a UUID cannot be deleted, even after unlocking the record.
4. Make the appropriate changes to the record.
5. Select **Save**.
   ![](../../../Resources/Images/SampleManagement/AOC/Unlock3.png)
6. Select the **Change State to Completed** action from the Change State menu to lock the record.

   ![](../../../Resources/Images/SampleManagement/AOC/Unlock4cropped.png)

When granted All Object Edit permission in the All Object Records section of their permission set, non-admin users can make changes to locked AOC records without unlocking the record, as needed for data loading or when using integrations.

### Related Topics

[Creating Sample Requests (BRCs)](../Disbursements/CreateBRC.htm)

[Shipping Sample Requests (BRCs) to Business Locations](ShipToBusiness.htm)