Future Release

Network File System

Future Release

Transfiormation Queries

DCR Cleanup

System Audit Log

Data Model

Data Managers

Default Match Rules

22R1

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

Hierarchy Explorer Widget

Administrators

Network Hashtags

Permission Sets

Standard Users

Hierarchy Explorer

Profile Notes

Field Mapping

Specialty Information

21R3.1

Data Stewards

Source Subscriptions

API

Field Updates

All Users

View Docs

The Hierarchy Explorer widget is available in Beta version.  If you are interested in being an early adopter, contact your Network representative.

The Hierarchy Explorer widget was introduced in 21R3.0 to help you 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. Custom hierarchiesYou can now create hierarchies so you can visualize primary relationships for specific business purposes. For example, you might create a hierarchy for sales roll-ups or for specific therapeutic areas (such as Neurology).

Hierarchy Explorer widget

Hierarchy Explorer Widget - Parent Organizations

Parent organizations The Explore HCPs tab contains a powerful new column to display all affiliated HCOs for HCP in the health system. You can use this information to see other HCPs that work for the affiliated organization and the health system the HCO is affiliated with. If an HCP has more than one affiliated HCO, click the + more link to expand the column for more details.

Search audit Administrators can track the searches in the Hierarchy Explorer through the Search Audit Log. You can find search events using the Hierarchy Explorer Widget term in the Search Origin filter.

Hierarchy Explorer - Search Audit

Hashtags display on record profiles and in search results to summarize important details. They can also be used in search queries to improve search accuracy. Network provides a set of predefined hashtags, but you can also create your own hashtags. New hashtags The following predefined hashtags are now available: #pharmacist (HCP - United States, Canada) - HCP is a pharmacist in the US and Canada.#phs (HCO - United States) - HCO is a PHS Outpatient Organization.These hashtags are enabled by default in your Network instance.

The dataflow functionality for record updates and merges now considers how standard (__v) and custom (__c) fields are managed. Fields can be managed locally, managed by Veeva OpenData, or managed by a third party data provider. Previously, data could be lost when updates or merges occurred because the process was unaware of the field management. For example, if you do not subscribe to field-level OpenData subscriptions (Email, HIN, NCPDP, GeoSubdivision, or CIP), those standard (__v) fields can be used for local data. When a record was merged in Veeva OpenData, any local data in those fields could be lost when the updates came down to your Network instance.  These enhancements ensure that the update and merge logic respects the management of the field data. Additionally, the merge logic will now treat NULL and EMPTY fields as the same in customer instances. These enhancements are enabled in your Network instance by default.

Field Updates and Merges

EuropeNew default match rules for HCPs and HCOs have been added for the change_request subscription. This is an internal subscription that is used to process all add and change requests through the Network UI or API. These changes will be applied to all Network instances by default. SingaporeNew default match rules for HCPs and HCOs in Singapore have been added for all subscriptions.

Source Subscriptions - Field Mapping Suggestions

The source subscription wizard now provides Network field suggestions to map to the column headers in your sample file. Suggestions are available for fields for all object types. This enhancement is enabled  by default in your Network  instance.

You can now export hierarchies to a Microsoft® Excel® file so you can share it with other users or further investigate the details. Select the HCPs or HCOs that you want to export or export the entire hierarchy. You can use the data to analyze the hierarchy; for example, use the data to understand the biggest HCOs (sort by total number of HCPs), calculate the levels inside the hierarchy, and analyze the geographies where HCOs are located. This enhancement is enabled by default in the widget.

Specialty information now displays in the partial results when you search for a record. Use this information to quickly identify the correct record. This enhancement  is enabled by  default in your  Network instance.

Specialty Display

In 21R3.1, the source subscription wizard was updated to provide suggestions for mapping your sample file column headers to Network data model fields. The suggestions were based on the column headers in the sample file. Now, the contents of the sample file are also reviewed to provide more helpful suggestions. This enhancement is enabled by default in your Network instance.

Field Mapping Improvements

Administrators can now provide application-level access to features using permission sets. Previously, application feature access was controlled only through a user's profile or at the instance-level (General Settings). Permission sets give Administrators more granular application-level control. Permissions can be granted to user groups or individual users. In this release, permission sets are supported for the new DCR Cleanup feature. The Permission Sets feature is enabled by default in your Network instance.

The System Audit Log now tracks all exports from your Network instance.The following exports are now tracked: Data model - Export the data model by clicking Export Data Model on the data domain page (Data Model > Data Domains).Reference data - Export all reference lists or a specific reference list (Data Model > Reference Data).Reference aliases - Export a reference alias list (System Interfaces > Reference Aliases).User list - Export the list of users for the Network instance (Users & Permissions > Users).This enhancement is enabled by default in your Network instance.

Network can now transform data so you can export it in the format that downstream systems can easily receive. Previously, you might have used a third-party ETL tool to post-process Network data. Now, you can create SQL queries to transform the data within Network before exporting it using a target subscription.Use transformation queries to post-process data. For example: Replace values - For example, if a limited relationship in Network is invalidated, the foreign key fields are set to -1, but that value is not supported in Veeva CRM. Replace -1 with #N/A for the CRM Upsert Connector.Denormalize a complex data model - For example, flatten a multi-level product hierarchy. The data is transformed to a single .csv file that your downstream system can easily digest.Join additional fields - For example: Join additional fields from any table in Network reporting, including lookup tables or custom tables.Define field values based on certain conditionsRename fieldsConcatenate or split fieldsThis feature is enabled by default in your Network instance.

Transformation Queries

You can now add notes to record profiles so other users can see the information. For example, data stewards can add a note to alert users when an HCP has taken a leave of absence, or to indicate an HCP's call time preference for data verification. All users, except Standard users, can view, edit, and delete profile notes if they have access to the main object through their data visibility profile. This feature is enabled by default in your Network instance.

Data Model - Country Support

Veeva OpenData data models have been added for the following countries/regions:Hong Kong (HK)Macao (MO)Taiwan (TW)The data models are based on the Other Countries (ZZ) data model. The data model also includes additional fields so they are consistent with the China OpenData data model. The activated reference codes are based on the reference codes that are activated for Other Countries (ZZ), along with additional reference codes supported by the China OpenData team. Chinese (zh) and Traditional Chinese (zh-TW) will be used for the Network UI, data model fields, and reference data.

Data Model - New Language

Albanian (SQ) is now supported as a reference language. It is not supported for Network data model fields or for the Network UI.This enhancement is enabled in your Network instance by default. To view reference codes in this language: On the Network menu bar, click My Profile.In the Settings section, expand the Language list and select Albanian.Apply your changes.

Data Model - Formatted Name

HCO and HCP name formatting rules have been added for the following regions:Hong Kong (HK)Macao (MO)Taiwan (TW)This enhancement is enabled by default in your Network instance. HCO Name calculationThe formatted name for HCOs uses the corporate_name__v field. HCP Name calculationHCP names will use the full_name__v field. If the full_name__v field is blank, the formatted name will be calculated using these Veeva fields in the following order: last_name__v + first_name__v The formatted name displays on the profile page.

The Network API is updated to v26.0.The Network API version is updated for every major release. Any additional changes are documented in this section of the Release Notes. As with all version updates, Integration Users should continue to use v25.0 until there is a change for v26.0 that they want to apply. Supported languagesYou can now use the Metadata API to retrieve the list of reference data languages supported by Network. Sample request: GET https://myveevanetwork.com/api/v26.0/metadata/languages

Network API

Users can now cancel or reject tasks in bulk in the Inbox. Tasks can be generated from internal processes or through integrations and need to be removed in bulk without reviewing each individual task. Previously, these tasks had to be rejected individually in the inbox or be rejected in bulk using the Network API. Users with the appropriate permission sets can now clean up these tasks directly from the Inbox. This feature is available by default in your Network instance, but it does not display until Administrators create permission sets to provide access to users. Only users with access will see the feature in the Inbox.

Use the File Explorer to see and manage your file system directly within Network. Previously, access to the file system was available using a third party tool only. Users that have FTP access can upload and download files in the File Explorer so they can be used by subscription jobs. This feature is enabled by default in your Network instance. Administrators can disable the feature for their Network instance using the File Explorer setting in the General Settings. Disabling the File Explorer does not impact your Network file system in third party FTP applications.