Custom Object Support

Future Release

Integrations

Future Release

Data Model Support

Data Domains

Profile Layouts

Network Bridge Updates

Single Sign-On

Veeva OpenData Subscriptions

Data Managers

Match Against OpenData

20R1

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

Data Model

Search Widget

Administrators

SQL Query Editor

Data Updater

Standard Users

Terminology

HIN Data

API

Primary Country Field

Network Reporting

Affiliation Widget

Workflow Settings

19R3.1

Export By Custom Key

All Users

Data Stewards

Custom Objects

Custom Objects in Profile Layouts

View Docs

The RXA eligible information is now available when you download an account using Network Account Search and when you import an account from a New Account DCR. In version 19R3.0, the Network State License Mappings was updated to include the rxa_eligible__v because sample eligibility and prescriptive authority can be different, depending on state laws.  Note:  More information will be available in the Veeva CRM 20R1.0 Release Notes. 

Integrations - State License Mappings

Veeva CRM Upsert

Customers that use Network and Veeva CRM can now push object data from Network's FTP server to CRM. Previously, users had to manually transfer the files to CRM. To upsert data to CRM, the following tasks must be completed: Add Salesforce credentials to Network - The credentials are used to connect to Veeva CRM.Create a connector - Create a connection to push object data from Network's FTP server to Veeva CRM.This feature is enabled by default in your Network instance.

Customers that use Network and Veeva Vault can now push object data from Network's FTP server to their Vault application. Previously, users had to manually transfer the files to Veeva Vault. To upsert data to Vault, the following tasks must be completed: Add Vault credentials to Network - The credentials are used to connect to Veeva Vault.Create a connector - Create a connection to push object data from Network's FTP server to Veeva Vault.This feature is enabled by default in your Network instance.

Veeva Vault Upsert

Business users can search for records by ID in the Advanced Search form, which can help you immediately find a specific record. Administrators must configure the search widget to use the ID field. The IDs that are available for search depend on the object and the country defined in your search form. For example, for HCOs in the United States, various license IDs and government IDs can be searched.

The IDs that are available for search in some countries might only include the Network entity ID (VID) and a license. If a country is not defined, the widget searches all available IDs. Click the IDs Available to Search link to see the IDs supported for your defined country and object. In the search results, the matching ID displays below each result. 

In the United States, a license is required if you want to receive Health Industry Number (HIN) IDs. For compliance, Veeva OpenData can provide HIN data only to customers that have a HIN license.  Previously, HIN ID data was available to all customers. HIN subscriptionUS Veeva OpenData subscriptions now contain the Include HIN data option that can be enabled if you have a HIN license. Enabling the HIN data subscription ensures that you continue to receive HIN IDs from Veeva OpenData when records are updated in your Network instance. There is no extra cost for enabling this subscription and receiving this data. Enable the HIN subscriptionIf you subscribe to OpenData for the United States and have a HIN license, the subscription will be enabled and you will continue to receive HIN data. If you do not have a HIN license, the subscription cannot be enabled; the option will be dimmed on the US OpenData subscription. For new customers, the HIN subscription is disabled by default until a license is verified. If you do not have a HIN license, the hin__v field can be managed locally; data change requests on the HIN ID will be sent to local data stewards.

HIN IDs for HCOs

The Data Updater feature now supports custom objects.This enhancement is available by default if custom objects are enabled in your Network instance.  To update custom objects, you must have access to the object through your data visibility profile.

You can update custom objects by uploading a file and choosing the custom object in the Data Updater job. Custom sub-object and custom relationship objects also display in the list if you have access to the root object.

Data Updater - Custom Object Support

Match Against Veeva OpenData

The Match Against Veeva OpenData process can now find all possible matches in both your Network instance and the OpenData master instance and choose the highest ranked match. When you use the Match against OpenData option in a source subscription or ad hoc match job, the match process first looks for matches to OpenData records that exist in your Network instance. If a match is found using any of the match rules, your locally managed record is merged into that Veeva OpenData record. Now, administrators can enable a setting so the match process will continue looking for a superior match (meaning that a record matches uses a higher ranked match rule) in the Veeva OpenData master instance, even if a match has already been found in your Network instance. This ensures that you have the best possible match. Enable Match against OpenData optionsTo direct the match process to continue looking for superior matches in the Veeva OpenData master instance, administrators can enable the Consider records in OpenData Master setting on the General Settings page. The Consider records in OpenData Master setting is enabled by default in new Network instances. It can be enabled in existing Network instances.

Administrators and data managers can filter target subscriptions to export records using the custom key source.This filter is similar to the existing Source System filter, but instead of exporting records based on the system that was used to load the data into Network, it exports the records based on the external source of the custom key, which can be different. This is helpful if you use a single source subscription to load multiple custom key sources. To export specific records to downstream systems, you can filter on the external custom key source, not the source system that was used to load the source subscription. This enhancement is enabled by default in your Network instance. ExampleUsing a single source subscription, you load a file that includes records from two sources: DMD and RM. You load them into Network using the ServiceCloud system; all source subscriptions are assigned to one system. To update your downstream system with records from the DMD source only, filter your export options using the Custom Key Source field (custom_key_source_type__v).

Data Model Support

Reference Data Hebrew (HE) has been added as a new reference data language to support Israel (IL). The Network UI and data model for Israel is in English.

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

The primary_country__v field for HCP and HCO objects is now read-only throughout Network. The primary country is defined when a record is created. Previously, the field was editable by a source subscription, the Network API, and on the profile page. If the primary country of a record is changed, problems can occur when the record is later updated or exported to downstream systems because the reference values will be out of sync. Reference data is managed by country so changing a record's primary country can make the existing reference values incorrect. Changing the primary country can also cause users to unexpectedly lose access to records because of their data visibility profile permissions. This update impacts the following Network features: Profile page - The field will be read-only. A lock icon will display. Data load - Changes to the primary country will be skipped but other updates will be processed as usual. A job warning displays in the Job Error Log on the Job Details page. The message will include the record's Network entity ID (VID) or the custom key so administrators or data managers can identify the problematic record. Note: This behavior applies to all types of jobs, including merge requests. Network API - Changes for the primary_country__v field will be denied. The response will display a failure message for the field. Suspect matches - Matches cannot be created if the records have different countries. This is existing behavior.

Customers can now communicate with Veeva CRM, Vault, or Nitro using the Veeva Connector feature. Using the Veeva Connector, you can extract object data from CRM or Vault or upload Network data to Nitro. Each integration must be configured in your Network instance. The Veeva Connector is enabled by default for all Network instances. Veeva CRM Customers extract object data to Network FTP using SOQL and publish the .csv files to Network's FTP server. Previously, .csv file creation was a manual process. Veeva VaultCustomers extract object data to Network FTP using VQL and publish the .csv files to Network's FTP server. For example, you might want to extract product data from Vault and load it into a custom object that you have enabled in your Network instance. Veeva NitroCustomers upload Network data to Nitro FTP using target subscriptions. The following steps have been automated to support the upload process: Exporting CSV files in individual ZIP filesGenerating Nitro control files (CTL) in NetworkUploading .zip files and CTL files from Network to Nitro SFTP for processing

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 can now configure a profile layout to have two sections for the same relationship. Custom relationship objects typically have one controlling object and one non-controlling object. In some cases, a relationship can have more than one controlling object or non-controlling object (arc relationships), or the same object can be both (recursive relationships). To support these complex custom relationships, the profile layout editor now supports having two sections for the same relationship so record profiles can display each related object. This enhancement is enabled by default if custom objects are enabled in your Network instance.

To more accurately the reflect the role of the main objects within the custom relationship object, the following terms are being changed in the Network user interface and documentation: controlling object is now ownernon-controlling object is now related object

Network widgets now support Oracle Identity Management (IDM)™ as an SSO provider. For information about using SSO with widgets, see Enable single sign-on for widgets.

Data Updater - Merging Records

Administrators and data managers can now use the Data Updater feature to bulk merge records using .csv files and Microsoft Excel (.xlsx) files. The file only requires you to include the Network entity ID (VID) of the losing and winning record of the merge. The data is validated and a summary of the merges is provided before the merge job runs. Data updater jobs are ad hoc jobs; they cannot be scheduled. This feature is available by default in your Network instance. With this feature: Users can merge records without using the bulk merge option in Network's robust source subscriptions feature.Microsoft Excel® and .csv file are supported. Microsoft Excel files must be .xlsx files only.Files that you upload can be stored locally. Users do not need access to your FTP server.Data is scanned to ensure it is valid before records are merged.

The address verification status on summary cards can be disabled on custom profile layouts. The default behavior is for the address verification status to display if addresses have been verified by Network's third party cleansing service.  The verification status can be one of the following: VerifiedPartially verifiedIncompleteOverridden

Address Verification in Profile Layouts

Cluster ManagementCustomers 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: Austria - IQVIA™A TPA must be signed with the third-party cluster provider to use the cluster management feature. For more information about this feature, see Managing clusters. Geocode SupportLatitude and longitude fields are now populated and persisted for addresses in Austria. This enhancement is enabled default for addresses in Austria 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.

Veeva OpenData - Email Subscriptions

A separate email subscription has been added to Veeva OpenData subscriptions for China (CN). This change aligns Veeva OpenData CN with other Veeva OpenData regions and allows you the option to manage the email data in your Network instance or have Veeva OpenData manage it. There is no additional cost for email data in China. If you already subscribe to Veeva OpenData for China, you will be automatically subscribed to the separate email subscription on your China OpenData subscription page. New customers for China OpenData can enable the email subscription if they want the China OpenData team to manage their email data. 

The Network data model is redesigned to support data domains. A data domain is used to logically group objects for a specific area of activity or knowledge. Data domains can be created for each business purpose; for example, you might create a domain for product data and one for clinical study data. The domain contains all of the related objects (and fields) for your data model, so Veeva standard objects and custom objects can belong to more than one domain. All objects will be part of a data domain; objects cannot exist outside a domain. Data domains also include the ability to create custom objects in your Network instance. Data domains are created in Sandbox instances so they can be thoroughly tested before being exported and used in Production instances. This feature is enabled by default in your Network instance.

Administrators now have more flexible workflow setting options for Veeva standard objects. Previously, the settings could be configured by HCO type and HCP type only. The options are now expanded to include any reference type field and can be configured to include multiple fields and criteria for each object. These options enable you 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. The following workflow settings have been updated to include the expanded criteria options: Auto-Approve Add Requests for New Customer Owned RecordsAuto-Approve Change Requests for Customer Owned RecordsReview OpenData Rejection of Add RequestsThe options in each workflow setting section have also been reworded for clarity. Any settings that you had previously defined are retained with these updates.

The Network API is updated to v20.0. Currently, there are no changes from v19.0. As with all version updates, integration users should continue to use v19.0 until there is a change for v20.0 that they want to apply.

Creating Custom Objects

Administrators can now create and edit custom objects. Previously, custom objects were created by Veeva and then you could enable the custom object in your Network instance. Now, custom objects can be created and edited in your Network Sandbox instance. After the objects are enabled and tested, you can export them to your Production instance. This feature is enabled by default in Sandbox instances. 

The LISTAGG() aggregate function now supports the WITHIN GROUP (ORDER BY ) clause so you can specify the sort order of the aggregated values. The following example returns results sorted alphabetically by HCP type: SELECT LISTAGG ( DISTINCT hcp_type__v, ', ' ) WITHIN GROUP ( ORDER BY hcp_type__v ) FROM hcp Result: A, D, DT, N, NU, O, P, PH, R, S, T

You can now download report results in Microsoft Excel™ (.xlsx) format. When report data is exported to Excel, all fields are converted to text format so the values are not automatically formatted; for example, long integer fields like Network entity IDs display properly, rather than in exponential format. After you run a report, in the Report Results section, click Download Report. In the dialog, Microsoft Excel (.xlsx) is now selected by default.  You can download reports in .xlsx format on the following pages: SQL Query EditorBasic Report BuilderAggregate Report Builder

Downloading Reports

Queries used by some data quality reports are updated to ensure that the correct records are being identified and that issues on locally managed records are clearly indicated. The query updates will occur by default in any instance where these data quality reports have been enabled. If a data quality report has been edited in an instance, the query will not be updated. Update 1- Exclude opted-out recordsOpted-out HCP records are excluded from some data quality reports. Opted-out records are currently being included which can result in records being flagged by a data quality report unnecessarily. The query is updated to check the value of the data_privacy_opt_out__v field for the HCP record. Update 2 - Check sub-object ownershipData quality report queries for sub-objects are updated to check the ownership of the sub-object records in addition to the owning entity. This refines the results to clearly indicate record ownership for data quality issues on sub-objects (addresses, license or parent HCOs). The query is updated to set the is_veeva_master__v field to the address, license, or parent HCO object. Update 3 - Exclude candidate records Candidate records are excluded from some data quality reports. They are currently being included which can result in records being flagged by a data quality report unnecessarily. The query is updated to check the value of the candidate_record__v field for records.

Data Quality Reports

The affiliation widget was introduced in version 19R2.1 to help users quickly understand influencers between HCPs and identify key players in a health care system. Edit mode is now available in the widget so you can develop the Influence Map by adding and removing accounts and relationships. 

The following changes can be made on the canvas: Draw or hide relationships: HCP to HCP, HCP to HCO, and HCO to HCOAdd HCPs from Network and Veeva OpenData to the Influence MapRemove HCPs and HCOs from the Influence Map The affiliation widget is available for early adopters; it is not available by default. To discuss becoming an early adopter, contact your Veeva representative.

Affiliation Widget - Edit Mode