Designating a client data integration handler
Sometimes ContactManager cannot create new contacts that PolicyCenter sends to it. Examples of problems that prevent creation include bad IDs, incomplete information, and duplicate contacts. Whenever ContactManager fails to create a new contact, ContactManager notifies PolicyCenter, which assigns an activity to a user whom you designate to follow up and resolve such issues.
The user who receives these activities from PolicyCenter must have permissions that enable working with contacts. The following table shows the set of permissions that are required in the base configuration.
Permission name |
Permission code |
|---|---|
Create address book contact |
|
Create contact with any tag |
|
Create local contacts |
|
Delete address book contacts |
|
Delete contact with any tag |
|
Delete local contacts |
|
Edit address book contacts |
|
Edit contact with any tag |
|
Edit local contacts |
|
View address book contacts |
|
View address book contact search pages |
|
View contact with any tag |
|
View local contacts |
|
These privileges grant the designated user access to local contacts and to contacts in ContactManager. To ease administration for changes to the designated user, create a user role, such as Client Data Integration Handler. Then, assign your designated user to that role. Assign only one user to that role at any time.
Before PolicyCenter can assign activities to your designated integration handler, you must configure the PolicyCenter method ABContactSystemPlugin.getAdminUserForIntegrationHandling to use the designated user’s PolicyCenter login name. If you change the designated user in PolicyCenter, manually reconfigure this method with the newly designated user’s login name.
See also
- To learn how to configure
ABContactSystemPlugin.getAdminUserForIntegrationHandlingwith a login name, see Integrate PolicyCenter with ContactManager.
