Lookup Tables

Refreshing Subscriptions

Future Release

Network Bridge

Future Release

Match Against Veeva OpenData

Workflow Settings

Custom Objects

Reporting

Reference Data

Affiliation Widget

Veeva OpenData Subscriptions

Data Managers

Country Subscriptions

20R2

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

Primary Address

Search Widget

Network Integrations

Administrators

Widgets - Custom Keys

Source Subscriptions

Cluster Management

Widgets - Filter by Parent HCO

API

Custom Domain Templates

Standard Users

Profile Badges

Widget Profile Layouts

Single Sign-On

20R1.1

Data Stewards

Geo Subdivision Subscriptions

All Users

US Compliance Data

Network Users Administration

View Docs

Veeva CRM users use Network Account Search to search for accounts in Network. Enhancements have been to the Network Account Search, particularly for addresses, to help you get more relevant results. Recommendations: Narrow your search results by providing a name and address. General search box - Searching with a name and/or identifiers (NPI, SLN, VID) will return more relevant results. For example, search for a specific NPI, License, or Network entity ID (VID). Address search box - Use this to search for fields on addresses. For users in the United States, provide the city and the state abbreviation; for example, Boston, MA.   These enhancements are enabled by default.

Integrations - Network Account Search

Integrations - Network Bridge

Updates have been made to the Network Bridge to help you to easily troubleshoot job errors. The Job Details page is redesigned to highlight any record-level errors that occurred during the job and includes an error log that can be downloaded. Record-level errors are also restructured into more granular categories to provide more information for administrations. Previously, many of the record-level issues were considered "Salesforce Upsert Errors." These enhancements are enabled by default in your Network instance.

Credentials that are saved for external applications must follow specific URLs patterns for security reasons. Some of the credential types have been updated to comply with the security guidelines. This enhancement is enabled by default in your Network instance.

Integrations - External Credentials

In Advanced Search, several enhancements have been made to the Country field to improve your search experience. The flag has been added beside each country name to quickly help identify it.

The Country list only displays countries that you have access to through your data visibility profile.When you log into the search widget, the country that you used for your previous search is preserved.When you filter your results using other fields, the options are determined by the selected country.

The search widget and profile widget can now filter the parent HCOs that display to users. Using a preset filter in the widget code, you can define the parent HCOs that are relevant to your business. Only the filtered parent affiliations will display in search results and on record profiles. The following example shows a widget to the right, filtered by Health Systems that are active only.

When you update a subscription to add HCP or HCO filters, you can now choose to download any additional records that meet the new filter criteria the next time the job runs. By default, when you add HCP and HCO filters, new records that match the criteria are downloaded only when OpenData makes changes to the record. Now, the next job that runs can include any new records along with updates to existing records.

Country Subscriptions for All Records

If you purchase all Veeva OpenData records for a particular country and you have specifically requested to have all records downloaded to your instance, the country subscription page now indicates these details. The subscription is also updated to remove the Working Set, Health Care Professional, and Health Care Organization sections to subscribe to additional records. When you subscribe to have all records downloaded to your Network instance for a particular country, there is no need to maintain a working set or HCO/HCP filters. You can continue to manage the parent HCOs that are downloaded, additional field level subscriptions (for example, Email and Geo Subdivision), and Veeva OpenData fields.

The Geo Subdivision and Geo Subdivision 2 subscriptions are now available for Russia. These subscriptions contain sales data that is organized into small geographic areas. If these subscriptions are added to your Veeva OpenData subscription for Russia, the following fields are automatically enabled on address object: geo_subdivision__vgeo_subdivision_label__vgeo_subdivision_2__vgeo_subdivision_2_label__v

Performance improvements have been made for source subscription and ad hoc match jobs when large numbers of new records are downloaded from a Veeva OpenData master instance. Veeva OpenData records are downloaded when the Match & Download from OpenData setting is selected in the subscription configuration. Ad hoc downloads that download numerous records from Veeva OpenData will also see improved run times.

Administrators and data managers can now disable Network Bridge subscriptions. This enhancement gives administrators more control for managing their Network Bridge subscriptions; for example, subscriptions that are no longer used, or that are seldom used, can be disabled so they no longer display on the subscription list page. When a Network Bridge subscription is disabled, the following behavior occurs:Scheduled jobs do not run (in the Network UI or the API).Job triggers that are set for this subscription do not run.New job triggers cannot be added for the disabled subscription.The subscription is removed from the list on its subscription list page. Network Bridge subscriptions can be enabled again after they have been disabled. When a disabled subscription is enabled again, any schedules or job triggers on the subscription will be active again; schedules will run at the set time and jobs will be triggered when the conditions are met.

Network Bridge Subscriptions

The Network Bridge page is updated to include the country and status for each subscription in the list.

Network Bridge Page

Network now provides custom domain templates for Product Master and Payer Master. The templates are populated with the typical objects required for these business areas. Designing and implementing a data model takes time, so using the templates ensures that the data model is well-designed and enables you to quickly start using the custom objects. The template is provided by Network, but after it is applied, the data model is customer-owned.

Spanish (Mexico) has been added as a new reference data language. This new language will inherit the translations from Spanish with a few exceptions. To review the specific translations, see "Spanish-Mexico" in the Translation section of the Veeva Network Data Governance document.

Integrations

The Network API includes the following updates to support Network integration with Veeva Nitro. Create target subscription job and Create subscription jobThe following optional parameter and values are supported:export_archiveall - Compress all .csv files into a single .zip file. The .zip file will be exported to the specified path in the target subscription (if not specified, the default path is used).individual - Compress each .csv file into an individual .zip file. The .zip files will be exported to a separate subfolder in the specified path in the target subscription (if not specified, the default path is used).none - Does not compress .csv files. Files will be exported to a separate subfolder in the specified path in the target subscription (if not specified, the default path is used).Retrieve target subscription job and Retrieve subscription job The following response fields are supported: exportFormatDelimiter - The .csv delimiter.exportFormatTextQualifier - The .csv text qualifier.export_archive - The archive mode of the target subscription.

API Updates - Nitro Integration Support

Administrators and data managers can now import lookup tables into their Network instance to perform operations and to calculate or validate data. These multi-value reference lookups are stored in Network so you can cross-reference your object data. Lookup tables can be used in Network expressions for source subscriptions and data model fields.

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

US compliance data is now updated weekly by Veeva OpenData. Previously, the data was updated monthly. Compliance data can be viewed on US record profiles in the Transparency Reporting preview box. This enhancement is enabled by default if you subscribe to US compliance data.

SAML for Single Sign-on now includes a relay state URL. The RelayState parameter defines where identity providers (idPs) send users after they authenticate. By default, a relay state URL is automatically generated for existing customers, but a custom URL can be defined. In some cases, there are idPs that use a different relay state parameter or URL. This setting gives administrators more flexibility to use different identity providers. This enhancement will be enabled by default in all Network instances in the Production release, version 20R1.1.1. It supports the Network widgets and the SSO button on the Network login page.

In version 20R1.0, workflow settings were updated to include any reference type fields. Now, Boolean reference fields are now supported for the workflow settings. You can use these BooleanReference and Checkbox type fields to be more specific about the records that are auto-approved or records that are returned to local data stewards if rejected by Veeva OpenData. In the following example, add requests for locally managed records will be automatically approved if the HCPs are pharmacists OR they are Fellows.

The affiliation widget homepage title has been changed to Influence Maps to more clearly identify it as a tool for visualizing affiliations. Previously, the homepage title was Health Care Systems. Additionally, the search field now displays the number of available health care systems available. This enhancement is enabled by default. The affiliation widget is available for early adopters. For more information, contact your Veeva representative.

By default, the Network widgets display record profiles using the profile layout assigned to a user's data visibility profile (DVP). Typically, the layouts assigned to the DVP contain all of the fields in the Network data model. Administrators can now choose to override this default behavior and assign specific profile layouts for each country to the widget. For example, you can use custom profile layouts to standardize the widget so all widgets users see the same fields or to limit the number of fields so widget users only see the essential fields.

You can now more easily identify information about the object from the badge on the object icon. Object icons contain information about the record; for example, the record state, the record status, if the HCP has opted-out, or if the record is a candidate record. When you hover your cursor over the badge, the tooltip clearly summarizes the badge information. This enhancement is enabled by default in your Network instance wherever icon badges are used.

Source Subscription Wizard

Network now provides a wizard to simplify the process of creating a source subscription. Using a sample file of data, the wizard guides you through the steps to define the advanced properties, field normalization, and model map. At the end of the wizard, the classic subscription configuration page opens so you can continue the setup by defining match rules, Network expression rules, and so on. This feature is enabled by default in your Network instance.

The Network API is updated to v21.0. Bulk export APIIntegration users can now use the Network API to retrieve data in bulk using API calls. Full exports can be large, so to prevent timeouts, the .csv file can be divided using the new split option for the existing export_archive parameter. The files will be split so no file is larger than 1GB. All .csv files generated by the target subscription will be split, including Source Data files if you selected that option in the subscription settings. The files are appended with a number (_0000, _0001, and so on) and are added to your outbound FTP folder. This is not configurable through the Network user interface. In this example, the address.csv file is greater than 1GB, so the files will be exported uncompressed and split into two files. This feature is enabled by default.

Reporting - Job Details

The Folder/ZIP File information that is defined in subscriptions is now included in the Job Details table for reporting. Data managers and administrators can now report on the information to know that the correct files were processed for the job. This enhancement is enabled by default in your Network instance for all source subscription, target subscription, and Veeva OpenData subscription jobs. Data will start being tracked in the field for this release; historical data will not be loaded.

Network widgets now support creating custom keys that are cross references to the source ID. Previously, custom keys could be created to track the systems that have downloaded records. Now, a separate custom key can be created that includes the cross reference ID (for example, the Salesforce Account ID.

In the search widget, you can now search by alternate key using the ID field in the advanced search form. This enhancement supports existing and new alternate keys. When you click the IDs available to Search link, the alternate keys are listed. In this example, My Alternate Key and Verteo ID are alternate keys that can searched for using the ID field. This enhancement is available by default. No changes are required to the configuration; the alternate keys will automatically be available as ID fields.

Search Widget - Alternate Key

In the search widget, after you submit an add request, clicking the Back to Search link now returns you to the search results. Previously, clicking Back to Search navigated you to the start page (either basic search or the advanced search form). This enhancement enables you to easily submit another add request. For example, if you are adding several new records, you can immediately click the Create New button on the search results page instead of searching again.

Search Widget Navigation

Veeva OpenData Subscriptions - Fields

All Veeva OpenData fields are now mastered by default in new Network instances. Previously, all OpenData fields were enabled in new instances; now, they will also be mastered by the respective OpenData country. This update simplifies the data model configuration in new instances. In your Veeva OpenData country subscription, all fields will be included in the Selected Fields section. This enhancement is enabled by default for all new Network instances.

Veeva OpenData - Download Related HCOs

Administrators and data managers now have the option of downloading Parent HCOs that are related to the OpenData HCOs and HCPs that are already downloaded to their Network instance. When Veeva OpenData country subscriptions run, parent HCOs are not downloaded; parent HCOs are only downloaded during ad hoc download jobs. This enhancement gives you the option to download those missing Parent HCOs so you have complete relationships in your instance. The count of related HCOs is provided so you will know how many records you can expect to be downloaded. This enhancement is available in your Network instance by default. You can use these settings in new and existing country subscriptions.

Veeva OpenData - Merging Addresses

Starting September 10, 2020, Veeva OpenData (US) will begin to periodically run bulk merge jobs if duplicate addresses are discovered in the master instance. Updates to addresses will flow down to your Network instance whenever your OpenData subscription runs or you sync or download records from OpenData. This applies only to your Veeva OpenData US subscriptions. Merging duplicate addresses keeps your data quality high, but it can impact your data depending on the Network features that you use for your business processes. Review the potential impacts and methods of preserving your data.

Two of the Unique Checkbox primary address settings are updated to help ensure that records will have a primary address:The record DOES NOT HAVE a primary addressThe status of the primary address is INACTIVE             These enhancements are enabled by default in your Network instance.

Removing Custom Objects and Data Domains

Data domains and custom objects can now be removed from your Network instance.For example, if a domain or an object was mistakenly created, or the wrong object was selected as the owner or related object in a relationship object, it can be removed. All custom data model entities can be deleted: data domains, main objects, sub-objects, and relationship objects. Data domains can be removed if they do not contain objects. Objects can be removed in the following conditions: No record exists in Network for the object. The object was created and enabled, but data has not been loaded.There are no tasks created for the object.The remove option is dimmed if any of these requirements are not met. After a domain or an object is deleted, the action cannot be reversed.

The Network Bridge can now run using Salesforce™ credentials that are stored in Veeva CRM. Previously, Salesforce credentials had to be maintained in both Network and CRM.  Now, using the CRM organization ID, Network can access the Salesforce session ID so administrators only have to update the credentials in CRM. This enhancement is available in your Network instance by default.

In the Admin console, the Users menu has been renamed to Users & Permissions. This change more accurately reflects the options that are available in this menu.

Users - Menu Name Change

Administrators can now apply field-level access for specific users or user groups. Previously, field access could only be managed using profile layouts. Now, you can set read-only or edit permissions on specific restricted fields. This feature is available by default.

Users - Field Restrictions

Administrations can now define the specific systems that users with API permissions can access. Previously, users were either allowed all access or no access to the Network API. Linking the user to the system prevents users from performing API calls under an incorrect Network system. For example, if you have an Integration user for a portal, you can give the user access to only the portal system to ensure they don't accidentally make API calls for another system. This enhancement is available by default in your Network instance.

Users - API Access