Reporting

Future Release

Future Release

Data Components

OpenData Subscriptions

Security Settings

Custom Objects

Network Integrations

Network Hashtags

Veeva OpenData

Data Quality Reports

Data Managers

Data Model

21R3

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

Workflow Settings

Inbox

Administrators

Search/Profiles

Subscriptions

Security

Standard Users

Network Widgets

Source Subscriptions

Network UI

Hierarchy Explorer

21R2.1

All Users

Data Stewards

API

User Status

View Docs

Veeva OpenData data models have been added for countries in Latin America. Bahamas (BS)Barbados (BB)Bermuda (BM)Cayman Islands (KY)Curacao (CW)Jamaica (JM)Trinidad and Tobago (TT)LocalizationJamaica - English translations will be used for the UI, data model fields, and reference data.All other new countries - Spanish translations will be used for the Network UI and data model fields. Spanish-Mexico (es-MX) translations will be used for reference data.New languageKorean (KO) is now supported for data model fields and reference codes. Korean characters can also be used in Network search. Korean is not supported for the Network UI. This enhancement is enabled in your Network instance by default. GeocodesLatitude and longitude fields are now available for addresses in all countries. Geocodes are available 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. This enhancement will be enabled by default in the Network 21R2.1.1 Production release.

Country Support

Data Model - Cluster Management

Customers can enrich addresses for additional providers and countries by adding cluster codes. In this release, Network has included support for the following country/third party cluster provider combination:Ireland - IQVIA™Netherlands - IQVIARussia - IQVIASwitzerland - SM Service Marketing™A TPA must be signed with the third party cluster provider to use the cluster management feature. For more information, see the topic called Managing clusters in the Veeva Network Online Help.

The Customer Data Privacy Opt Out Date field will become read-only in Network version 21R3.0. The field was introduced in version 20R3.1 to capture the date that the data privacy opt out flag is set to True. The field has been editable so administrators could backfill the date on locally managed HCPs records that were opted out before the field existed.If you are planning to backfill the Customer Data Privacy Opt Out Date field, the updates must be completed before version 21R3.0. For detailed instructions, see the Data privacy opt out date topic in the Veeva Network Online Help. This update will be enabled by default in your Network instance in version 21R3.0.

Data Model - Data Privacy Opt Out Date

Tasks with many objects The DCR process now supports tasks for entities with a large number of sub-objects (> 100 sub-objects per sub-object type) or with a large number of pending associated tasks (> 100 tasks). This enhancement is enabled in your Network instance by default. Sub-objects When data change requests are submitted, Network reindexes the DCR task and the entity. Indexing DCRs for records containing many sub-objects (for example, 300 sub-objects or relationship objects) may cause issues in your Network instance. To better handle these tasks, Network will not index the sub-object or relationship object records if there are more than 100 records for each object type. Associated tasks After an update to a record, Network indexes the entity for each associated pending task. Network will not reindex the entity if there are more than 100 associated tasks for the record.

Custom object records can now be hard deleted. Previously, the records could be soft deleted (record state is DELETED) but the custom object definition could not be deleted because tasks and records still existed in the database. Now, the custom object records can be flagged for hard deletion. After Veeva Support deletes the records, administrators can delete the custom object definition.This feature is enabled by default if you have custom objects enabled in your Network instance. Hard deleting records is helpful when you have loaded data for testing but you no longer want the object and records in your Network instance. When custom object records are hard deleted: They are permanently removed from your Network instance.Pending and closed add and change requests are deleted.Pending and closed suspect match tasks are deleted if they contain deleted records.Source subscription jobs for the deleted records are still available for audit purposes.Reports cannot be run on the records. Reports that previously ran using the deleted records are available to view.

Custom Objects - Hard Deletion

Veeva OpenData Subscriptions

Mail only addresses on Veeva OpenData records can now be invalidated automatically. Network Expression rules can be used to invalidate these addresses after they are downloaded from Veeva OpenData but if the addresses are merged into other addresses in the OpenData instance, those updates will not occur in your Network instance. Using this feature, mail-only addresses from OpenData subscriptions, ad hoc download jobs, and change requests are automatically updated to the INVALID record state after merge updates. Additionally, the feature ensures that invalid addresses are not set as primary addresses. Custom keys are not inactivated when mail-only addresses are invalidated. This feature is not enabled by default. To enable the feature, contact Veeva Support.

Source Subscriptions - Network Expressions

A new function, SETI, can be used in source subscriptions to help load dynamic attribute data from Veeva CRM.SETI(field, value)Dynamic attributes are special Veeva CRM fields created for an immediate business need; something that would not require a custom field. For example, business admins might collect information for an account for an upcoming conference. Dynamic attributes can be extracted from CRM using the Veeva Connector. This is a one-way integration from Veeva CRM to Network.

The following fields have been added to the results:Medical DegreeSpecialty This enhancement is enabled in your Search widget by default.

Network Widgets - Search

Data components are now supported on account profiles in Network widgets.Data components were introduced in version 21R1.1 so users could view external data related to main entities (HCPs, HCOs, and custom objects) in Network without logging into another system. Previously, data components were limited to the Network UI. Now, you can view external data for HCPs and HCOs in the Network widgets. Administrators can apply the same data component to the Network UI and the Network widgets. This feature is enabled by default in your Network instance. Administrators can add existing or new data components to the following Network widgets: Affiliation widgetProfile widgetSearch widgetData components cannot be applied to the My Request widget. Network PortalIf you are using Network widgets in the Network Portal, the portal must be enabled to see the data components in the widgets. Data components do not display when the Network Portal is in preview mode.

Network Widgets - Data Components

For consistency, the Status label on Network user accounts has been changed from Disabled to Inactive. The two user status options are now Active and Inactive.

Veeva Network is deprecating the use of TLS 1.1. Network currently supports TLS 1.1 and TLS 1.2. security protocols for encrypted internet communications. After version 21R2.1 is released, only TLS 1.2 will be supported.Support will be removed for the following TLS cyphers: DHE-RSA-AES256-GCM-SHA384DHE-DSS-AES256-GCM-SHA384DHE-DSS-AES128-GCM-SHA256

Transport Layer Security (TLS)

You can now view external data for multiple HCPs and HCOs in the Affiliation widget. In version 21R2.1, support for data components in the Affiliation widget was introduced, but the data was limited to a single profile.  Now, using tabs on the Influence Map, you can view data components that display data for multiple accounts. For example, you can see emails sent to all HCPs from Veeva CRM or view recent calls for all HCPs. This feature is enabled by default in your Network instance. Administrators can create the data components to display on Affiliation widget tabs.

Network UI Improvements

Changes are being added to the Network UI to standardize icons. You might notice slight differences in icon appearance and sizes throughout the UI. These changes are enabled by default in all Network instances.

Hierarchy Explorer is a new feature that enables you to explore entire health systems from a top-down approach. All levels of the hierarchy display so you can search through it to find new targets and to visualize and understand the hierarchy. Only the data in your Network instance displays. The Hierarchy Explorer is available as a Network widget. You can add it to the Network Portal, an internal application, or Veeva CRM Online. This feature is for Early Adopters. If you are interested in using the Hierarchy Explorer, contact your Veeva Network representative.

The Date field now displays the start date of the data quality run, not the last update from the reporting data warehouse. Previously, the Date field displayed when the reporting database was last updated.  After the reporting improvements in version 21R2.1, entity-level updates are immediately exported to the reporting database, so there is no need to track that date. This enhancement is enabled by default in your Network instance.

Network hashtags are now available in the Search, Profile, DCR, and MyRequest widgets. Hashtags summarize important details on record profiles. Network provides a set of predefined hashtags and administrators can create hashtags for their specific business purposes. For example, you can use hashtags to easily identify records that were already downloaded in Salesforce® Service Cloud. This enhancement is enabled by default in your Network instance.

Hashtags now display on record profiles to summarize important details. Hashtags also display on search results and can be used in search queries to improve search accuracy. Network provides a set of predefined hashtags and administrators can create hashtags for their specific business purposes. This feature is enabled by default in your Network instance.

Search/Profiles - Network Hashtags

Advanced reporting users can now create their own data tables in the SQL Query Editor. You can create a table by uploading a file or through your report results.Use custom tables to: Compare existing data in your Network instance to a source file before an initial data load.Upload a file instead of using the Lookup Tables feature. There is no file size limit for creating a custom table; lookup tables are limited to 1GB or 5 million rows.Create a table based on your report results so you can create complex queries that don't time out.This feature is enabled by default in your Network instance.

Reports - Custom Tables

As part of our ongoing Network Reporting infrastructure improvements, entity-level updates are now immediately exported to the reporting database. This means that you can report on updated data as soon as changes are made in Network. This significantly improves on the existing process of scheduled database updates and eliminates the need for the Reporting Database Last Updated timestamp on the reporting pages. These improvements are enabled by default in your Network instance.

Reports - Real Time Exports

Data Privacy Opt Out

Data privacy opt out date The Customer Data Privacy Opt Out Date field will become read-only in this release; Network version 21R3.0. The field was introduced in version 20R3.1 to capture the date that the data privacy opt out flag is set to True. The field has been editable so administrators could backfill the date on locally managed HCPs records that were opted out before the field existed. If you are planning to backfill the Customer Data Privacy Opt Out Date field, the updates must be completed before Network instances are updated to version 21R3.0.1 (Production release). Data privacy opt out Veeva OpenData now manages HCP opt outs for South Korea. Two data model fields have been enabled for the HCP object: data_privacy_opt_out__vdata_privacy_opt_out_date__vRecords that are opted-out by Veeva OpenData do not display and cannot be accessed in downstream systems. This ensures data privacy for opted-out HCPs to satisfy regional regulatory requirements.

Formatted Name

A custom calculation has been added for the formatted_name__v field for South Korea. The formatted name uses values from several name fields to display a complete name for an HCP. This enhancement is enabled by default in your Network instance. Name calculation HCP names for South Korea are calculated using these Veeva fields in the following order: last_name__v + first_name__v The formatted name displays on the profile page.

Changes to Non-System Fields

Several updates have been made to non-system Veeva fields so Administrators and Data Managers have more control and consistency over the fields in their Network instance. These updates occurred in the 21R2.1.3 maintenance release. The changes are documented for information purposes only; no action is required. Click the View Docs link in the bottom corner for a list of unlocked fields.

The Geo Subdivision and Geo Subdivision 2 subscriptions are now available for the United Kingdom. These subscriptions contain sales data that is organized into small geographic areas. If these subscription are added to your OpenData subscription for the United Kingdom, the following fields are automatically enabled on the address object: geo_subdivision__vgeo_subdivision_label__vgeo_subdivision_2__vgeo_subdivision_2_label__vThe subscriptions will be available after the 21R3.0 Production release.

Veeva OpenData Geo Subdivision Subscriptions

Beginning January 1, 2022, US Veeva OpenData subscriptions will no longer include American Medical Association (AMA) data. Currently, this data is stored in a list of data model fields on US records. Those fields have been grouped together to form an AMA data subscription which controls the behavior of the fields depending on your agreement with the AMA. Key dates November 19, 2021 - AMA subscriptions are available in Network instances that have US OpenData subscriptions enabled. The subscription was included in the 21R2.1.3 release. It is enabled by default. If you will receive AMA data from a different data source, you can begin testing the subscription. Disable the subscription so the Veeva AMA fields become locally managed, and create a source subscription to populate those fields. December 15, 2021 - If you will continue to receive AMA data from a different data source, disable the AMA subscription by this date so the existing data is retained in the AMA fields. December 16-31, 2021 - After December 15, Veeva OpenData will begin removing the contents of the AMA fields. The data will be completely removed by December 31, 2021. If you have disabled the AMA subscription by December 15, the data will be retained. January 5, 2022 - If you canceled your agreement to receive AMA data from a Database Licensee (DBL), send confirmation letter of the data removal to the DBL. Contact your Veeva OpenData CSM for more details.

Veeva OpenData AMA Subscription

Veeva OpenData subscriptions for the United States contain the option to receive a score that indicates an HCP's affinity for consuming digital data.  This subscription is available to customers whose US OpenData contract allows them to download unlimited records. There is no extra cost for enabling this subscription and receiving this data. The Include Digital Affinity Scores subscription can be enabled in your US OpenData subscription. If the subscription is available for your OpenData contract, select the option in the Field Level Subscriptions section and then save the subscription.

Digital Affinity Score Subscription

Network Integrations - Network Bridge Warnings

Detailed warnings now display in your Network Bridge configuration if you link the Bridge to an incorrectly configured target subscription. The warnings will prevent data issues in Veeva CRM.Common issues for target subscriptions include: The Record State setting is set to Valid & Under ReviewRecords that are INVALID or MERGE_INTO state are not sent downstream so merges don't occur; duplicate records will be created in Veeva CRM. The Full Data Extract setting is set to Full instead of DeltaWhen you export the full set, entities that haven't changed are continually sent to Veeva CRM. This increases the Network Bridge job time and increases the time to sync and download to mobile devices. When these issues are identified for the target subscription that you link to your Network Bridge, the warnings display in your Network Bridge configuration so you can make changes. This enhancement is enabled in your Network instance by default.

Network Integrations - Network Bridge Errors

Administrators can now report on record level errors in Network Bridge jobs. Previously the Network Bridge job stats were not recorded in reporting. Now, you can query the data and error types for each Bridge job in the SQL Query Editor. This enhancement is available by default in your Network instance. Note: The Network Bridge job stats are available for Bridge jobs that started after the version 21R1.1 release.

Primary field updates on subscriptions Network now provides a summary of the updates that occur on primary fields during subscription jobs. Many customers use primary fields for business purposes like incentive compensation or territory alignment. When changes occur to primary fields, it can impact those processes. After subscriptions run, counts for primary field updates now display in the job details so administrators are aware of the updates and can make necessary changes. This feature is enabled in your Network instance by default.

Subscriptions - General

Administrators can now configure multiple custom keys for sub-objects and relationship objects in the source subscription wizard.  Sub-objects and relationship objects can be associated to more than one main entity. To avoid duplicate key errors when the subscription runs, the Select Keys step in the wizard is updated to provide a custom key configuration for each associated main object. This enhancement is enabled by default in your Network instance.

Source Subscriptions - Configuring Custom Keys

Match API

You can now use the new Match API to match data immediately for a single record. This is helpful when you need to verify data in real-time, for example, when you are registering HCPs in a portal. You can match the data using an API call instead of trying to verify the data using Network Search which requires multiple searches, filtering and field queries. The API uses the default match rules for your Network instance.

API - Network Hashtags

Hashtags help to summarize important details about records. Integration Users can now include hashtags in the Search, Retrieve, and Retrieve Change Request API calls. This enhancement is supported for Network API version 25.0 and later. Integration users can use a new parameter to see hashtags in search results and metadata for the requested type.

Custom Objects - Limiting the Number of Relationships

Administrators can now configure custom relationship objects to limit the maximum number of relationships to an owner object to one. Before this release, all relationship objects were many-to-many relationships by default. Now, you can create one-to-many relationships in the data model by limiting relationship objects to one relationship per owner object. This feature is enabled by default for your Network instance.

Default field values can be automatically added when new object requests are submitted without a value. Administrators can define default values for fields in the workflow settings.  When requests to add an object are submitted without values for these fields, the workflow defined default value is added when the task is created. This feature is enabled by default in your Network instance.

SSL certificate updateThe current SSL certificate for veevanetwork.com expires on January 1, 2022. The following certificates must be updated by December 31, 2021: veevanetwork.com - Covers all sandbox and production Network instances and login.veevanetwork.com.Intermediate CA certificate cert - Ensures that the SSL certificate is fully trusted by the supported browsers and client computers.Note: The certificates are not yet available. They will be available in December. Only customers who explicitly download and install certificates on any site caches or proxy servers must update their certificates.