Ensure Configuring Data Change Requests is complete.

A New Account DCR can only be initiated from the Network Account Search results page by tapping the New button. Even if the user does not have permission to create new accounts, the New Account button displays on the Network Account Search results page because the user can create a DCR with this button by making edits to the Account.

After tapping the New button, the user creates the new account using the standard procedure. After saving the changes, the DCR notes window displays.

The Data Change Request Notes field is optional (notes__v field of the Data Change Request object). Enter the reason for the changes or other notes for the Data Steward or equivalent responsible person.

Do not enter emojis in the notes__v field.

Tapping the Submit button submits the DCR for processing at the next sync.

It is normal for the iPad platform to generate more supplemental DCR lines than the Vault platform. Each field on the page layout with a value (including default value, but excluding system fields like LastModifiedDate) is created by a DCR line. Only DCR lines mapped to Network fields are sent to Network.

When a user has access to the DCR object and the account__v object type, an Account Edit DCR page displays after the user taps the Edit button. DCR-controlled fields display with a lock icon on the right side. If the user changes a value on any DCR-controlled fields, a Data Change Request confirmation window displays when the user taps Save.

Non DCR-controlled fields can be edited normally and are stored when clicking Save.

Account DCR Confirmation page

The top section of the Data Change Request confirmation window is a Notes field (notes__v field of the Data Change Request object). Enter the reason for the changes or other notes for the Data Steward or equivalent responsible person. The Notes field is an optional field, but it can be made a Required field by enforcing it on the DCR page layout.

Only the DCR controlled fields on the account display in the bottom section of the Data Change Request confirmation window. The New Value displays along with the Field Name and Old Value, and is prepopulated based on Current Value. The New Value field highlights in orange.

Tapping the Submit button submits the DCR for processing at the next sync.

If a user without create permissions for the Address object clicks the New Address button, a DCR is created via the Address creation page. The user can edit information in the Address creation window. When tapping Save, the Data Change Request Notes window displays for the user to provide more information.

The Data Change Request Notes field is not required.(notes__v field of the Data Change Request object). It can be made a Required field by enforcing it on the DCR page layout. Enter the reason for the changes or other notes for the Data Steward or equivalent responsible person.

Tapping the Submit button submits the DCR for processing at the next sync.

When a user has access to the DCR object and the address__v object type, they can submit an Edit Address DCR. DCR-controlled fields display with a lock icon on the right side. The User can change the value as needed on the page. A Data Change Request confirmation window displays when the user taps Save.

Non DCR-controlled fields can be edited normally and are stored after clicking Save.

Address DCR Confirmation page

The top section of the Data Change Request confirmation window is a Notes field (notes__v field of the Data Change Request object). Enter the reason for the changes or other notes for the Data Steward or equivalent responsible person. The Notes field is an optional field, but it can be made a Required field by enforcing it on the DCR page layout.

Only the DCR controlled fields on the address are shown in the bottom section of the Data Change Request confirmation window. The New Value displays along with the Field Name and Old Value, and is pre-populated based on Current Value. The New Value field highlights in orange.

Tapping the Submit button submits the DCR for processing at the next sync.

There are two ways to create a new child account:

• Selecting the Member Of related list and tapping the + button on the person Account detail page
• Selecting the Member related list and tapping the + button on the organization Account detail page
  

If the user has permission to create new child accounts, the standard process is used. If the user does not have permission to create new child accounts, the user can still create DCRs via this method.

• The user must have access to the DCR object in order to create and view Data Change Requests

• The child_account__v object type should be visible for the user

To establish the parent/child relationship:

1. Select the Parent account.
2. Set the Parent account to Primary, if applicable.
3. Select the Child account.
4. Select Save. The Data Change Request Notes page displays.

The user can select the Parent account and set it to Primary, if applicable; the user can then select the Child account. The DCR Notes (notes__v field of the Data Change Request object) is not required. It can be made a Required field by enforcing it on the DCR page layout. Enter the reason for the DCR or other notes for the Data Steward or equivalent responsible person.

Selecting Submit submits the DCR for processing at the next sync.

Edit Child Account DCR

When a user has access to the DCR object and the child_account__v object type, they can submit an Edit Child Account DCR. DCR-controlled fields display with a lock icon on the right side. The user can change the value as needed on the page. A Data Change Request confirmation window displays when the user taps Save.

Non DCR-controlled fields can be edited normally and are stored when clicking Save.

Child Account DCR Confirmation page

The top section of the Data Change Request confirmation window is a Notes field (notes__v field of the Data Change Request object). Enter the reason for the changes or other notes for the Data Steward or equivalent responsible person. The Notes field is an optional field, but it can be made a Required field by enforcing it on the DCR page layout.

Only the DCR controlled fields on the child account are shown in the bottom section of the Data Change Request confirmation window. The New Value displays along with the Field Name and Old Value, and is pre-populated based on Current Value. The New Value field highlights in orange.

Tapping the Submit button submits the DCR for processing at the next sync.