Administrative tools for Veeva Network are accessible via an administrative web tab which points to a custom Veeva page called Network Integration Admin.
The network admin page contains two sections that allow the user to manage credentials; Veeva Network credentials and Salesforce credentials. Each section is modeled as a standard detail page layout with its own row of buttons. Only Administrators have access to the tools and are able to enter any information.
Veeva Network Credentials
The Edit button opens the Veeva Network credentials entry window. The user must enter the URL, username, and password they use to access Veeva Network. If the credentials are valid, the window closes and the Credential Status field displays as Valid. If the authentication fails, then an error message displays inline in the window. The error is defined by the NETWORK_ADMIN_PAGE_UPDFAILURE_ALERT;;Network Veeva message.
The Validate button refreshes the value of the Credential Status field. When the user clicks the button, the field value becomes either Valid or Invalid based on the outcome of the operation.
The user clicks Cancel to close the window without saving. The button caption is defined by the CANCEL;;Common Veeva message.
Salesforce Credentials
When the user clicks Edit in the SFDC Credentials section, the SFDC credentials entry window displays. This window behaves identically to the network credentials entry window, except there is no URL field.
The Validate button refreshes the value of the Credential Status field. When the user clicks the button, the field value becomes either Valid or Invalid based on the outcome of the operation.
When clicking Submit, the system automatically sets the Sandbox? field if the authentication is successful.
Network Integration User
The Network Integration user needs FLS visibility on the Network_Admin_vod__c field on the Salesforce User object.
Deprecating Hard-coded System Identification
In order to allow for more flexible data subscription process, CRM can be identified according to system names configured in Network. This lifts the restriction of the system name being hard coded and including the CRM OrgId (VCRM-[ORGID]).
System Name is used in several key Network Integration processes, most notably the CRM-NTW custom key association process. It is important to understand the implications of changing the CRM system name for live implementations. Although the older methods of system identification are still supported, it is a best practice, when enabling the integration, to use the new method of identifying the system.
A new section in the Network Administration console called 'System Identification' manages the system name. Clicking the edit button in this section displays a system name edit dialog that contains dialog all of the configured system names in Network. This information comes directly from Network. There is no way to type in the system name. Once selected, clicking Submit commits the change.
