Decoupled Unverified Records
Users can create and immediately use decoupled unverified accounts, addresses, and child account records to log a call, or use decoupled unverified new records for an existing account.
For example, a user wants to submit a call for an HCP, but one of the attendees is not an existing account. After searching for the attendee, the user selects the New Account action and enters all the required data for the New Account wizard, which immediately adds the decoupled unverified account and allows the user to add the attendee to the call.
This feature is available from the following entry points:
- New Account wizard
- New Account from Global Account Search
- New Child or New Parent action from the Members list on the Account Detail page
- New Address from the Account Detail page
Considerations
- When CRM Managed Acct Types is configured, Vault CRM does not create a DCR for the account object type specified in the CRM Managed Acct Types setting, but the account is still created and available for immediate use
- Third party account object types are not supported. All other object types are supported.
Who can use this feature?
- Browser, iPad Users
- Users do not require an additional license
- Business Admin Users, End Users
Configuring Decoupled Unverified Records for

To enable this feature:
-
Grant users the following permissions:
Object Object Permission Object Type Fields Field Permission data_change_request__v
C
- account__v
- address__v
- child_account__v
n/a
n/a
data_change_request_line__v
C
all
n/a
n/a
dcr_field_type__v
C
n/a
n/a
n/a
- Remove Create access from the following objects for DCR users:
- account__v
- address__v
- child_account__v
Do not remove Create access to these objects if the user is also configured to use CRM Managed Account Types. Users require create access to these objects to create records without submitting a DCR.
- Populate the Data Change Request Mode Veeva Setting with a value of 2 to allow creation of DCRs.
- Populate the Network Customer Master Mode Network Setting with a value of 0 to prevent user DCRs from being sent to the Veeva Network.

To enable this feature:
-
Grant users the following permissions:
Object Object Permission Object Type Fields Field Permission data_change_request__v
C
- account__v
- address__v
- child_account__v
n/a
n/a
data_change_request_line__v
C
all
n/a
n/a
dcr_field_type__v
R
n/a
n/a
n/a
- Remove Create access from the following objects for DCR users:
- account__v
- address__v
- child_account__v
Do not remove Create access to these objects if the user is also configured to use CRM Managed Account Types. Users require create access to these objects to create records without submitting a DCR.
- Grant Edit permission to the Customer Master Status field on the account__v, address__v, and child_account__v objects.
Unverified records are created with a Customer Master Status of Under review.
- Populate the Data Change Request Mode Veeva Setting with a value of 2 to allow creation of DCRs.
- Populate the Network Customer Master Mode Network Setting with a value of 0 to prevent user DCRs from being sent to the Veeva Network.
Using Decoupled Unverified Records as

When users in offline mode search for an account and do not find the account in the results, they can select the New Account action and use the New Account wizard to enter account details. Users can also enter a new address from the Addresses section of the Account Detail screen. Vault CRM creates a Data Change Request. The new decoupled unverified account or address record is immediately available for use in calls.
Internet access is required on the iPad platform to create the unverified records and make them available to the user.