HCO Icons

Future Release

Target Subscriptions

Future Release

Data Maintenance

Source Rankings

Veeva Connector

Geocodes

External Credentials

Profiles - Affiliations

Data Managers

Data Privacy Opt-Out

21R1

Integration Users

Click a point on the timeline to view features released in that version.

Veeva OpenData Subscriptions

Network Portal

Administrators

Affiliation Widget

Cluster Management

Network Integrations

Performance Improvements

Search Widget

API

Network Users

Standard Users

Inbox

Network Portal and Widgets

20R3.1

Data Model

All Users

Data Stewards

Matching Opted-Out Records

User Groups

View Docs

The Affiliation widget is now generally available. It was introduced in version 19R3.0 for early adopters. Use the widget to create influence maps for your health systems. The widget is not available by default. Contact Veeva Support to enable the widget configuration for your Network instance. ViewsThe Affiliation widget now supports creating multiple views to provide more control and flexibility for your Influence Maps. Creating different views of your health care system enables you to customize your view without limiting other users.

Affiliation Widget - Relationship Details

Users can now capture more information about HCP-HCO and HCO-HCO relationships when they are created or edited in the Influence Map. Previously, only HCP-HCP relationships could be edited. This provides more information for users and enables you to report on connection types using Network reporting. This enhancement is available by default. Administrators can update the widget configuration to define custom fields that display when users create or edit relationships in the Influence Map.

You can now see metrics displayed for HCO objects in the Affiliation widget. Previously, metrics displayed only for HCPs. Using metrics enables you to visually understand custom defined metrics for HCOs. This enhancement is not enabled by default. Developers can enable the HCO metrics by including a property in the widget code.

Affiliation Widget - HCO Metrics

The Network Portal contains applications that are connected to Network widgets. Only applications that you have access to will be displayed in the Network Portal. Access to the Network Portal and each application is controlled by user and user group permissions. The Network Portal includes a predefined search application, Search Accounts, so users can find and edit HCP and HCO accounts in Veeva OpenData and your Network instance. The Network Portal is available in all Network instances, but it is disabled by default. System Administrators and System and Data Admin users can enable the Network Portal. 

Ten new icons have been added for HCOs to help you easily differentiate HCO types. For example, the new icons will help you to identify an HCO from search results when HCOs have the same name but different types. The icons are used for all record owner types (local, Veeva OpenData, third party data providers) and all record states. These new specific HCO icons will be used throughout the Network UI, the Network Portal, and Network widgets. They are enabled by default.

The date that the data privacy opt out flag is set to True is now captured in a new field so you can easily see the date in record profiles and use it in reporting queries. Previously, the date was only set in the revision history. Now, the date is explicitly captured and available in the new HCP field. This enhancement is enabled by default in your Network instance.

Data Privacy Opt-Out Date

New country supportA data model has been added for Singapore (SG). The reference data is based on the Other Countries (ZZ) data model. The data model also includes the alternate_last_name__v field. English translations will be used for the reference data in the Network UI. Formatted nameThe formula for the HCP formatted name is updated for some countries in Europe. Whenever records are loaded in your Network instance or DCRs are submitted, if there isn't a value for the formatted_name__v field, Network calculates the value using the available name fields. Internal rules are defined to identify the fields that are used to calculate the formatted name for a specific country. For example, most countries use the first name and last name but some countries also include a middle name, prefix (Hr.), or medical degree for an HCP. These changes are enabled in your Network instance by default.

Administrators can now prevent users from downloading HCPs that have been unsubscribed from OpenData. When records are unsubscribed, they are no longer available in your Network instance. However, if the Search against OpenData feature is enabled, the records display in the search results and include the Download from OpenData icon; users can unknowingly subscribe to HCPs again. You can now specify a reason when you unsubscribe HCPs and then those records can be filtered from OpenData search results based on that reason using data visibility profile permissions. HCP records can be resubscribed in your local Network instance using search or if an incoming record from an add request matches a Veeva OpenData record. Records can also be resubscribed through other applications that integrate with Network using the API; for example, Veeva CRM (Network Account Search), Network search widget, and Veeva Concur Connector. Using this feature, users can be restricted from unsubscribed HCPs so they cannot be resubscribed through any of these ways. This feature is not enabled by default. Administrators must enable the feature for your Network instance.

System managed user groups To help you easily manage and maintain user groups, Network now provides a number of system managed groups. Custom user groups must be manually maintained, so managing them for larger Network instances with many users can be time consuming. The system managed-user groups are read-only; Network dynamically adds and removes users based on their user type, status (active or not active), and security policy. You can use the system managed user groups to easily assign permission to the Network Portal and its applications. These system managed user groups are enabled in your Network instance by default. User group improvements Enhancements have been made to custom user groups so you can easily add and remove users in bulk. Usability enhancements have been made to user groups on the User Groups page, the Dynamic Access Control feature, and the Field Restrictions feature to help you find and select groups. These enhancements are enabled to your Network instance by default.

Administrators can now quickly find user profiles by filtering the Users page by status or user type. Now, only active users display by default. Performance improvements have been made to load users to list faster. These enhancements are enabled in your Network instance by default.

Network Users - Managing Users

A new user type called Portal User enables you to create users that have access only to the Network Portal and Network Widgets. This user is also useful if your organization doesn't use single sign-on. Portal Users will access the Network Portal directly from the login page. This user is available in your Network instance by default.

Network Users - Portal User

The External Credentials feature is enhanced to provide more information about the environment that the external credential is linked to. It also provides warnings if you are potentially connecting to the wrong environment; for example, if the credentials connect your Sandbox Network instance to a Production CRM org. This enhancement is enabled by default in your Network instance.

Administrators and Data Managers will see noticeable improvements in the page loading times for the following Network UI pages:List of Job Triggers pageTarget subscription page and individual configuration pagesNetwork Bridge page and individual configuration pagesAdditionally, the Job Triggers sections on subscription configurations now load more quickly. These enhancements are enabled by default in your Network instances.

The Network Portal system, network_portal__v, can no longer be selected in the Source Rankings.The system does not apply to source rankings, so it has been removed from the list of available sources.

Source Rankings - Network Portal

Network Bridge Addresses with the record state, Merged_Into, that were associated to DEA licenses are now deleted in Veeva CRM. Previously, addresses associated to DEA licenses were not deleted. Enable Merged_Into address deletion The CRM setting, NETWORK_ADDRESS_DELETION_PROCESS_vod__c, must be set to is set to 1 or 2. When NETWORK_ADDRESS_DELETION_PROCESS_vod__c is set to 2, the last address or primary address on the account is not deleted.

View Additional Affiliations in Profiles

On an OpenData record profile, you can now view affiliations that have not yet been downloaded to your Network instance. You can download the HCOs using the Show additional OpenData HCOs link. Additional HCOs can display in the Parent HCO Affiliations section on HCP profiles and the Parent HCO Affiliations and Child Affiliations sections on HCO profiles.This feature is supported only on OpenData record profiles that are downloaded in your Network instance. This feature is not enabled by default. Administrators can enable this feature for their Network instance.

Latitude and longitude fields are now populated and persisted for addresses in Spain.This enhancement is enabled by default for addresses in Spain when address cleansing is enabled in your Network instance. These values will display on address records after they are loaded, or after they have been updated. The Latitude and Longitude fields are available using the Extended Info link on an address in a record profile.

Data Maintenance - Custom Object Records

Administrators and data managers can soft-delete custom object records using a data maintenance job. When records are deleted, the associated sub-objects and relationship objects are also deleted or inactivated. The data maintenance job soft-deletes the records, so you can update downstream systems if records were previously exported before you hard delete them in Network. The data maintenance job deletes custom object records by object type. All main custom object records can be deleted. Sub-objects and relationship object records cannot be deleted on their own. This feature is enabled by default in your Network instance.

Customers can enrich addresses in additional countries by adding cluster codes. In this release, Network has included support for the following country/third party cluster provider combination:Spain - IQVIA™A TPA must be signed with the third party cluster provider to use the cluster management feature.

Cluster Management

Integration User

Administrators can now provide Integration Users with additional permissions for the target subscription and metadata API. This enhancement supports Nitro's Veeva Network Intelligent Sync Connector. For more information about this integration, see the Nitro Online Help.With the new permissions, Integration Users will have the following access: Visibility to all fields in the Metadata API regardless of their data visibility profile.Users can use the new ALL countries option in the metadata fields API with this permission. The permission is not enabled by default.

Match to Opted-Out Records

Administrators can now choose to include opted-out HCP records in matching for incoming records from add requests and source subscriptions. By default, opted out records are excluded from matching.This feature supports records that you have opted out in your Network instance (customer opt outs) and records that have been opted out from Veeva OpenData and have previously been downloaded to your Network instance. You can determine the opt out setting by country. This feature is available by default in your Network instance.

Custom keys can now be generated when new records are created in Salesforce™ using the CRM Upsert Connector. Previously, the keys of Salesforce records were not stored in Network so it was difficult to track the records in Salesforce. Also, if you used the Export by VID feature with custom key filters for the target subscription, the newly created records were not regularly updated because there was no custom key. Now, the key can be stored when records are created, just as it is stored when records are created through the Network Bridge and Network widgets. This enhancement is available by default in your Network instance.

Veeva Connector - CRM Upsert

The Network API is updated to v23.0.As with all version updates, integration users should continue to use v22.0 until there is a change for v23.0 that they want to apply. Metadata APITo support Nitro's Veeva Network Intelligent Sync Connector, a new value is available for the countries parameter. The ALL value enables Integration Users to retrieve metadata access to all enabled fields for all countries. For example, if an Integration User has access to US data only, using this option allows them metadata access to all fields for all countries. This option is supported in v23.0 of the Network API.

Administrators can configure search widgets to use a specific profile layout for add requests that can be different than record profiles and change requests. This gives you more flexibility over the forms that display for users. Using a limited profile layout can generate better add requests because you can include only the fields that are essential for creating a new record. This enhancement is enabled by default in your Network instance.

Add requests that have created a suspect match task now contain a link to that task. Data Stewards can click the task ID link in the Status section to open the suspect match's task. This enhancement is enabled by default. The suspect match task links display only on requests created after this enhancement is released.

Add Requests

Enhancements have been made to suspect match tasks to remove the ability to make field value choices that do not need to be processed for specific scenarios.Hide field buttons for Under_Review records - Suspect match tasks that originate from add requests now only display the option to match or not match. Dim field buttons for HCP opt outs - If an opted-out HCP record is the winner of a suspect match, the only field value that can be actioned is the Customer Data Privacy Opt Out? field. The buttons to accept all other field values will be dimmed. Opted-out records are read-only, so the Customer Data Privacy Opt Out? field is the only field that should be available to update. These enhancements are enabled by default in your Network instance.

Suspect Match

My Request Widget

A new Network widget is available so business users can view the data change requests that they've submitted. Administrators can configure the My Request widget in their Network instance and add it to a Network Portal application so all users, except Integration Users, can check the status of their requests without logging into Network. The My Request widget configuration is available by default in Network instances. Administrators can create a widget and add it to a Network Portal application.

Affiliation Widget Branding

The Affiliation widget now provides the ability to customize the Influence Map branding so you can distinguish object types and highlight relationship details. This enables you to visualize specific business information; for example, to differentiate HCO types and business professionals from other HCP types, or to better understand the patient journey in the health system.These enhancements enable you to do the following: Override existing icon mappings and color branding.Customize relationship details such as labels and colors.Use new Influence Map tools to filter on relationships.These enhancements are not enabled by default. To add custom branding for objects and relationships, contact Veeva Support.

Record profile sections that contain no field values are automatically collapsed so users can more easily scan for relevant data.You can manually collapse or expand any sections on the record profiles.

Veeva OpenData country subscriptions now contain an option to update all of your records.Each time your subscription runs, only the records that have been changed in OpenData since the last time the subscription ran are included. This means that records in your working set will trickle into your Network instance as they are changed by OpenData, so some of them might not be downloaded to your Network instance. Using this new option, all of the records in your working set are forced to be downloaded and any records that you have already downloaded will be updated to their latest version. This option is available in your OpenData country subscriptions. It is not enabled by default.

Veeva OpenData - Update All Records

You can now request updates for specific HCP or HCO records from Veeva OpenData. This enables OpenData to ensure that you have the most current version of a record. It's also helpful when you subscribe to new record components. For example, if you subscribe to emails or enable an existing OpenData field, the data is only included in the OpenData delta export if the record has been changed by OpenData.Using this feature, you can provide a list of entity IDs (VIDs) to the OpenData team. When your OpenData country subscription runs, the updates will be included in a separate export. The counts for records in the targeted export will be included in the subscription counts on the job page. This feature is controlled by Veeva OpenData. To request updates for specific records, contact Veeva OpenData.

Request Targeted Record Updates

The Geo Subdivision 2 subscription is now available for France and Monaco. The subscription contains sales data that is organized into small geographic areas.If the subscription is added to your OpenData subscription for France or Monaco, the following fields are automatically enabled on the address object: geo_subdivision_2__vgeo_subdivision_2_label__vThe subscription will be available for the 21R1.0 Production release.

Geo Subdivision Subscriptions

Export All Objects

Administrators and data managers can configure target subscriptions to automatically export all objects and fields. This ensures that any new objects and enabled fields are included in the export job; you do not have to update each target subscription configuration when new objects are added to your Network instance.This enhancement supports the integration with Nitro's Veeva Network Intelligent Sync Connector to reduce configuration issues and implementation time. For information about this integration, see the Nitro Online Help.

DCR Exports

DCR exports can now include the master key of the parent HCO when a DCR with a relationship is exported. Previously, the exported file included only the Veeva ID of the parent HCO and the custom key of the object (HCP or HCO) that owned the relationship. Now, the custom key can be included so third party masters can easily identify the parent HCO and process the DCR.This option is available in DCR export target subscriptions, but it is disabled by default. Administrators and data managers can enable it in the subscription configuration. When the option to export the parent HCO custom key is enabled, three additional columns are appended to the end of the DCR export file: PARENT_ENTITY_CUSTOM_KEY_SOURCEPARENT_ENTITY_CUSTOM_KEY_TYPEPARENT_ENTITY_CUSTOM_KEY_VALUE