Any time a user adds or edits information for a contact that is in the firm’s list or creates a new contact, Data Change Management may be used to process the change.
Data Change Management can handle the following types of user actions:
- When a User Changes Information for a User Contact
- When a User Adds a Contact Type to a Contact
- When a User Changes Information for a Firm Contact
When a User Changes Information for a User Contact
Each user can maintain contacts in his or her own contact list. The contacts in this list are called user contacts. For each of the user contacts, users can maintain their own versions of the contact’s name, phones, and addresses. If the contact in the user’s contact list is connected to a contact in the firm’s contact list, the firm contact is updated when the user updates his or her information, provided it is not a confidential field. For example, Brian Roberts can have a contact, Darvin Hamm, in his user contact list that is connected to the contact for Darvin Hamm in the firm’s contact list. When Brian changes Darvin's job title, that change is also made to the firm’s version of Darvin's job title. Then, Data Change Management rules determine whether Brian's update is automatically applied to the firm’s data for Darvin or if his change must first be reviewed by a data steward before it is applied.
When a User Adds a Contact Type to a Contact
Contact types are used to categorize contacts. Some contact types provided with InterAction+ include Our Personnel, Alumni, Client, and Prospect. Users can apply contact types to contacts in the InterAction+ Client Insights when they create new contacts or edit existing contacts.
Depending on which contact type the user applies to the contact, Data Change Management rules determine whether the change is automatically applied or if it must be reviewed by a data steward. For example, Brian Roberts applies the Client contact type to Darvin Hamm. Because your organization wants to maintain careful watch over the contacts categorized as clients, instead of immediately applying the Client contact type to Darvin, a Data Change Management ticket is created. This lets the data stewards responsible for monitoring clients verify that Darvin should really be designated as a client.
When a User Changes Information for a Firm Contact
In addition to changing the contact information they maintain in their own contact lists, users can change the contact data maintained on the firm version of a contact. For example, Brian Roberts can edit the organization’s business phone number for Darvin Hamm instead of updating his own information for him. When Brian attempts to edit the phone, Data Change Management rules determine whether his change is automatically applied or if it must be reviewed by a data steward first.