1. Create a DCR Field Type record for each DCR-managed field on the account, child account, or address object.

   Four categories of fields can be used. This table describes all supported configurations. Configurations not listed in this table are not supported.

   For DCRs of type New sent to Network, additional data_change_request_line__v records are created for non-DCR Field Types. This allows Vault CRM to retain the information on the record when it is created.

Field Description/Category	Network		Field Type	Configuration Options
	Field	Approval		Object Edit	Field Permission	Page Layout Rules	Inline Edit
Editable Network Field: Field can be modified by user. Changes trigger creation of DCR in the background.	Yes	No	dcr_editable__v	Y	Visible	Editable	Disabled
				Y	Visible	Read Only	Enabled
Editable Required Network Field: Field can be modified by user. Value cannot be empty. Changes trigger creation of DCR in the background.	Yes	No	dcr_editable_required__v	Y	Visible	Required	Disabled
				Y	Visible	Read Only	Enabled
DCR Controlled Network Field: Field cannot be modified by user. User needs to create a DCR in order to modify a field value. Changes are performed only after receiving approval from Network.	Yes	Yes	dcr__v	Y	Read only*	NA	NA
				Y	Visible	Read only	NA
				N	NA		NA
				Y	Visible	Editable	Disabled
DCR Controlled Required Network Field: Field cannot be modified by user. User needs to create a DCR in order to modify a field value. Changes are performed only after receiving approval from Network. Value cannot be empty when creating a DCR.	Yes	Yes	dcr_required__v	Y	Read only*	NA	NA
				Y	Visible	Read only	NA
				N	NA	NA	NA
				Y	Visible	Editable	Disabled

*It is not possible to remove field permission for the Name field of any object. This configuration option cannot be used for these fields.

There is a risk concerning Inline Editing when using DCR Editable fields. To configure DCR Editable fields without disabling Inline Editing, mark them as read only on the page layout. DCR Editable fields can be modified based on a user's field permission and not on the page layout setting.

The Editable and Read Only DCR field types are not supported. Refer to the following sections for configuration options.

DCR Field Type Configuration Examples

Combined with different page layouts and field permissions, DCR Field Types can be leveraged to achieve different business goals. Here are some examples.

Enforce verification before change is applied to data

Changes made on some attributes of customer data may deserve more attention than other attributes, like the specialty or credentials of a physician. For license related attributes, it is likely any changes need to go through the approval process to maintain compliance. In these cases, it is recommended to define these attributes/fields to be dcr__v or dcr_required__v (if it is a mandatory value) in the DCR Field Type. When changing the value of a field defined as dcr__v in the DCR Field Type, the user is able to change the value, however, there is a key icon (a key icon with a red star for dcr_required__v) displayed beside the field indicating changing this field needs to go through a data change request process. When the user clicks Save, a DCR confirmation window displays a list of the current values and intended new values of each field in the DCR process. The new value of the field is not applied until the corresponding DCR is approved.

Configuration checklist:

Field Permission	Page Layout	DCR Field Type	Object Type in DCR Field Type
Visible	Editable	dcr__v (or dcr_required__v)	null

Enforce verification before change is applied to data, but only to a certain object type

If the customer wants to enforce verification only on a particular object type when the end user tries to update data, the record_type__v field on the dcr_field_type__v object should be specified when defining the DCR Field Type for fields.

Configuration checklist:

Field Permission	Page Layout	DCR Field Type	Object Type in DCR Field Type
Visible	Editable	dcr__v (or dcr_required__v)	[Object Type that needs to be enforced]

Enforce verification while new value can be used right away

A customer may want the changes made to some attributes to be applied right away, but still want the change to go through the DCR process. The benefit is the end user can use the new value without waiting, and the DCR can be verified by a separate team at the same time. For example, a user may want to change an HCP's email address and send Approved Email to the doctor immediately. In this case, the email field can be defined as dcr_editable__v (or dcr_editable_required__v if it is a mandatory value). When changing the value of a field that is defined as dcr_editable__v in the DCR Field Type, the user is able to change the value on UI. When the user selects Save, the new value of the field is applied immediately for use, and a DCR record is generated in the background to go through the verification process.

Field Permission	Page Layout	DCR Field Type	Object Type in DCR Field Type
Visible	Editable	dcr_editable__v (or dcr_editable_required__v)	[Object Type that needs to be enforced]

Enforce verification while new value can be used right away, but only to some users

If the customer only wants some users to be able to modify the value, for this group of users, define dcr_editable__v for these fields in the DCR Field Type. The page layout setting for these fields can be set to Editable.

For another group of users where they are not allowed to modify the value, set field permission to Read-Only for that security profile. The field is read-only and is not available for editing on the DCR Edit page.

Field Permission	Page Layout	DCR Field Type	Object Type in DCR Field Type
Read-only	Read-only	dcr_editable__v (or dcr_editable_required__v)	[Object Type that needs to be enforced]

The Read-Only page layout setting and field permission do not override the dcr__v or dcr_required__v.

Do not use dcr_editable_required__v or dcr_required__v to designate a check box as required.