Decoupled Data Change Requests
To edit account data that must be validated or verified by a data steward, Vault CRM customers can use native Data Change Request functionality on the account__v, address__v, and child_account__v objects. This feature is available independent of a Veeva Network subscription (decoupled). However, for organizations without a Veeva Network subscription, admins must separately configure processes for decoupled DCR review, approval, and integration into Vault CRM and other systems.
If an HCP moves to a new office, a user can submit a DCR to change the address on his account. An admin approves the request according to the organization’s address change process, and updates the HCP’s address using an external software system integrated with Vault CRM.
Who can use this feature?
- End Users — Browser, iPad
- Editing Account Information with Decoupled DCRs
- Users do not require an additional license
Configuring Decoupled Data Changes for
Business Admin Users
To configure this feature:
- Ensure Configuring Accounts and Configuring Data Change Requests are complete.
-
Grant users the following permissions:
Object Object Permission Object Type Fields Field Permission data_change_request__v
CRE
- account__v
- address__v
- child_account__v
n/a
n/a
data_change_request_line__v
CRE
all
n/a
n/a
dcr_field_type__v
CRE
n/a
n/a
n/a
network_settings__v R n/a All fields Read - For DCR users, remove Create access from the following objects:
- account__v
- address__v
- child_account__v
- Enable the data_change_request_mode__v Veeva Setting with a value of 1.
- Verify the network_customer_master_mode__v Network Setting is 0, which is the default value.
- Create or activate existing VMOC records for the following objects:
- data_change_request__v
- data_change_request_line__v
- dcr_field_type__v
When DCRs are created independently of Veeva Network, they are created with the status Submitted. How these DCRs are reviewed, approved, and flow into Vault CRM and other systems must be separately configured based on your organizational master data processes.
End Users
To enable this feature:
- Ensure Account configuration and Configuring Data Change Requests are complete.
-
Grant users the following permissions:
Object Object Permission Object Type Fields Field Permission network_settings__v R n/a All fields Read - Verify the network_customer_master_mode__v Network Setting is 0, which is the default value.
When DCRs are created independently of Veeva Network, they are created with the status Submitted. How these DCRs are reviewed, approved, and flow into Vault CRM and other systems must be separately configured based on your organizational master data processes.
Editing Account Information with Decoupled DCRs as
End Users
Users edit account information with decoupled DCRs using the same interface as they would for regular DCRs, although admins must process the request separately.
To edit account information using decoupled DCRs:
- Select the Edit action on the appropriate Account Detail page.
- Edit the desired fields. The lock icon indicates which fields are DCR controlled.
- Select Save.
- Enter any applicable Notes describing the reason for the DCR.
- Select Submit.
The DCR status is automatically set to Submitted. For decoupled DCRs, admins must configure separate processes for reviewing, approving, and updating records with the suggested change.
For more information on using DCRs, see Edit Account DCR (iPad) or Edit Account DCR (Browser).
Support for multi-country users does not apply to Decoupled DCRs.
