Creating Unverified Records
To maintain a clean Vault CRM data set, Veeva Network data stewards review new record creation and existing record edits. Most of the time, the reviews take under 24 hours to return changes to Vault CRM. However, sometimes the information is required immediately to record a call report or to take other action and cannot wait for validation from a steward.
To address this issue, the integration between Vault CRM and Veeva Network supports creating unverified records. The records are created simultaneously in Vault CRM and Veeva Network and labeled as Under Review. Users can take action immediately on the account or address. Data stewards can review the records at a later time and the reconciled data is pushed back into Vault CRM.
For example, a user meets an HCP at a medical event and details multiple products. The user immediately creates a new account to record the call, and submits it, allowing data stewards to review the record and reconcile the data.
Who can use this feature?
- Browser, iPad Users
- Users do not require an additional license
- Business Admin Users, End Users, Integration Users
Configuring Unverified Records for
Integration Users
To enable this feature:
- Grant Edit permission to the customer_master_status__v fields on the account__v, address__v, and child_account__v objects.
Create permission is not required on the account__v, address__v, and child_account__v objects unless using a CRM managed account.
- Ensure the Create Unverified setting is enabled in Network.
- Grant CRUD access to all mapping objects.
-
Grant CRUD access to the following objects:
- data_change_request__v
- data_change_request_line__v
To enable creation of unverified child accounts, grant the integration user edit permission to the customer_master_status__v field on the following objects:
- account__v
- address__v
- child_account__v
This field does not need to be on the layout. Picklist values include the following:
- valid__v
- under_review__v
- rejected__v
Business Admin Users
Vault CRM
To enable this feature:
-
Change the Data Change Request Mode Veeva Setting to 2 in Vault CRM.
-
Set the Network Customer Master Mode Network Setting to 1.
- Grant Edit permission to the customer_master_status__v fields on the account__v, address__v, and child_account__v objects.
Create permission is not required on the account__v, address__v, and child_account__v objects unless using a CRM managed account.
Veeva Network
Ensure the Create Unverified setting is enabled.
End Users
Vault CRM
To enable this feature:
-
Change the Data Change Request Mode Veeva Setting to 2 in Vault CRM.
-
Set the Network Customer Master Mode Network Setting to 1.
- Grant Edit permission to the customer_master_status__v fields on the account__v, address__v, and child_account__v objects.
Create permission is not required on the account__v, address__v, and child_account__v objects unless using a CRM managed account.
- Grant Read access to all mapping objects.
-
Grant CRU access to the following objects:
- data_change_request__v
- data_change_request_line__v
To enable the creation of unverified child accounts, ensure there is an active VMOC entry for the child_account__v object.
Veeva Network
Ensure the Create Unverified setting is enabled.
Creating Unverified Accounts as
End Users
Creating Unverified Child Accounts
Users can create unverified child accounts in the Parent Account Wizard or the Object Type Wizard. Users who make calls on business accounts need unverified child accounts created and displayed in the Call Attendee section.
Unverified record creation respects validation rules. If there is a validation rule violation when creating unverified records, an error occurs.
Unverified child accounts can also be created via the following:
- Members related list
- Members Of related list
- Data Loader
- Integration
Processing of Unverified Records
When a user creates an unverified account or address, data change request records are immediately created and sent to Network.
After the DCRs are sent to Network, Network processes them as follows:
- Auto-match the user-created records with existing records - In this case, the master record is aligned and pushed down to the user for immediate use.
- Flag as a suspected match - In this case, the user-submitted data is created as an “unverified” record in Network and is pushed back to the user for immediate use. A Data Steward reviews the user-submitted records and either rejects them, accepts them as new data, or merges them with existing records.
- Created as new records - If no auto matches or suspected matches are found, the user-submitted data is created as an “unverified” record in Network, and is pushed back to the user for immediate use. A Data Steward reviews the user-submitted records and either rejects them, accepts them as new data, or merges them with existing records.
Data Stewards perform the following post-processing reconciliation:
- Auto matches do not require any post-processing reconciliation as no new data is created
- For suspected matches and net-new records, the Data Steward can either accept, reject, or merge the new data
- If the Data Steward accepts new data, the record state in Network is changed to “valid” and pushed back to the customer_master_status__v field in Vault CRM
- If the Data Steward merges user-submitted records with existing records, Vault CRM also performs a merge when the next subscription runs
- If the Data Steward rejects user-submitted records, the behavior in Vault CRM varies by object:
- For Account records, rejected accounts have all territories removed, the Customer Master Status is set to “rejected”, and the owner is changed to the integration user
- For Address records, the inactive flag is selected, the Customer Master Status is set to “rejected”, and the owner is changed to the integration user
For Child Account records, the user-submitted records are deleted
