Match Config Field Support

Future Release

Network Bridge

Future Release

Data Model Country Support

Primary Country

Updating Data

HomeDashboard

Address Lines Construction

API

Match against Veeva OpenData

Data Managers

Data Export

19R3

Geocodes

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

Custom Keys

Affiliation Widget

Administrators

Profile - Revision History

Disable Subscriptions

What’s New Button

Inbox Enhancements

Data Model Export

Standard Users

Updated Reporting UI

Reference Type Labels

License Mapping

19R2.1

Cluster Management

All Users

Data Stewards

Dynamic Access Control

Integrations

View Docs

The navigation options for Network Reporting have changed as follows:SQL Query Editor (formerly Ad Hoc Queries, Advanced tab)Basic Report Builder (formerly Ad Hoc Queries, Record Details tab)Aggregate Report Builder (formerly Ad Hoc Queries, Counts & Summaries tabSaved Reports (formerly All Reports)Data Quality Reports (formerly Quality Reports) Reporting database timestamps Updates for the reporting database display on the Basic Report Builder, Aggregate Report Builder, and SQL Query Editor pages. The Last Updated timestamp is now more readable. The Next Update timestamp has been removed to avoid confusion; the timestamp could be misleading especially when there were no updates to export.

Network Reporting UI Updates

Reporting - SQL Query Editor

The SQL Query Editor has been redesigned to make the following functionality easier to use:Query Helpers - Several options help you build your query. Click each icon to open a list of available tables, fields, reference codes, keywords, and operators.Excluding Records - Select Include only VALID and UNDER_REVIEW records in results to exclude all other record states. This option is enabled by default. Sample Queries - Enables you to open a list of query templates, which you can preview and insert into the SQL Query Editor (without overwriting the current query.My Recent Queries - Enables you to find, preview, and insert a query that you have previously run from the SQL Query Editor. It functions similarly to the sample queries list.

The Saved Reports page was previously called All Reports. The function of the page is unchanged, but improvements have been made to the UI to make it easier for you to create a new report. The key change on this page is how a new report can be created. Creating new reports On the Saved Reports page, click Create a Saved Report. When you click the button, two options display:Start from a Blank Report - Create a report. In the Build Report section, choose how you want to create the query: Basic Report Builder, Aggregate Report Builder, or SQL Query Editor.If you choose the SQL Query Editor in the custom report, you must type the SQL query in the query box; Sample Queries and My Recent Queries are not available on this page. Start from a Sample Query - Choose a sample query. In the Sample Queries dialog, you can click Preview Query to view the SQL for any of the sample queries in the list. The sample query is inserted in the query box on the SQL Query Editor tab.You still have the option to use the Basic Report Builder and Aggregate Report Builder by clicking on those tabs.

Reporting - Saved Reports

The affiliation widget enables business users to quickly visualize HCP influencers and identify key players in a health care system. Sales reps, home office users, and account managers can use affiliation data to determine who to target during the pre-commercial stage of a product. Users access real-time Network data in their own application without logging into Network. Affiliations are displayed in an influence map or a table, to visualize metrics or determine the level of influence between HCPs. They can further explore details by opening individual profiles, whose visibility are determined by each user’s data visibility profile. The affiliation widget is  available for early adopters;  it is not available by default.  To discuss becoming an  early adopter, contact your  Veeva representative.

The following fields are now available to use when you are creating or editing data groups and match rules using the basic match UI.address_status__vhco_status__vhcp_status__vlicense_status__vparent_hco_status__vPreviously, the address_status__v and parent_hco_status__v fields were available only in the advanced match UI.This enhancement is enabled by default in all Network instances.

Match Configuration - Field Support

Administrators and data managers can now choose to export Network data in individual .zip files. The setting is available in all target subscriptions, but it is disabled by default. On the Job Details page, the Overview section displays the selection for the Zip Files Individually option.

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

A data model has been added for eight new countries for Veeva OpenData:Armenia (AM)Azerbaijan (AZ)Georgia (GE)Kyrgyzstan (KG)Moldova (MD)Tajikistan (TJ)Turkmenistan (TM)Uzbekistan (UZ)

A geocode accuracy field is now available in the Network data model. The field can be used to understand the quality of the geocodes that are returned by Network's third party address cleansing service. For example, you can use the GeoAccuracy code to troubleshoot inaccurate cluster calculations.Enable the fieldThe geo_accuracy_code__v field is enabled by default in new Network instances. The field is not enabled by default in existing Network instances to prevent mapping issues in downstream systems. Administrators can enable the field. The field is available for all countries but data is populated only for countries where geocoding is supported: Australia, Canada, France, Italy, and the United States. The field is populated (along with the latitude and longitude fields) when an address is cleansed. Address cleansing occurs when addresses are added or updated in your Network instance. The geocode accuracy field can be added to profile layouts; it is not added by default. GeoAccuracy codesGeoAccuracy codes contain two values: status - P (Point), I (Interpolated), A (Average), U (Unable to geocode)level - 5 (Delivery Point), 4 (Premise), 3 (Thoroughfare), 2 (Locality), 1 (AdministrativeArea), 0 (None)

Columns that contain multiple filter selections are standardized to ensure the behavior is consistent:Filter selections are not automatically applied; each list contains Apply and Cancel buttons to complete or cancel the action.Selected values are identified by a count.All values can be selected at once.

Inbox Filters

In addition to the column filter enhancements, updates were also made to the main filters. As you make selections, a count now displays beside the main filter name. When you apply your selections, the color of the filter name, icon, and the selection count changes from black to blue. This is a quick way for you to see that you have filters applied.

Task IDs are now a link so you can quickly open the request. Right-click the link to open the data change request in another browser tab.

Task ID Column

Columns have been added to the data model export file. The columns have been added to the Network Data Model and the Custom Objects Data Model so both exports contain the same columns.The following columns have been added to the exported file. Initial Version Added - The first time the field was created for at least one country. Reference Type - If the field does not have a reference type, the column is empty. Default Value - True if the field has a default value in at least one OpenData country HCP Opt Out Behavior - Indicates what happens to the field value when the record is exported if the data_privacy_opt_out field is set to Yes/True. Default Rankings - Identifies if the field rankings have been overridden.Read Only in (region) - Determined per country; False if the field is not available in a country. Required in (region) - Determined per country; False if the field is not available in a country.

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

The Home dashboard for administrators is updated to include dashboard widgets that were previously available only to data managers. These widgets are available by default. Administrators can add them to their dashboard using the Manage Dashboard button on their home page.The following dashboard widgets are now available for administrators: Task Breakdown Today - Displays all of the tasks in your local timezone.DCRs Created and Processed by Hour - Displays the number of DCRs that were created and processed in the last 24 hours.Steward Productivity over Time - Identifies the number of tasks processed by data steward for the past week.Note: For the three dashboard widgets above, administrators must belong to inbox task groups to have access to the available data.

Home Dashboard

What’s New Button

The What's New appears when you log into Network at the beginning of each new release. Click the button to navigate to the "What's New" topic in the Veeva Network Online Help to learn about the new features and enhancements in the release. A red badge displays on the button to advise you that there are new features and enhancements to read about. The badge disappears after the button is clicked. When you end your Network session, the What's New button also disappears until the next release. After the button disappears, to revisit the "What's New" topic, click the Help icon to access the Veeva Network Online Help.

Labels for Reference Type Fields

Web developers can add properties to the widget code that will return label values for reference type fields. Developers can use these labels for mappings for their application instead of creating reference aliases. These properties are supported for the Search widget and the DCR widget.When a user downloads a record in these widgets, the labels for reference type fields will be available for developers in the select events. Developers can retrieve the data from the JSON that is returned and use them for their Network integration. New propertiesenriched-results="true" - This will display labels in the JSON that is returned for the select event.lang="en" - The language that you want the labels to display; for example, en (English)For example:

Administrators and data managers can use this new feature to quickly make simple updates to records using .csv files and Microsoft Excel (.xlsx) files. For example, you might want to update primary addresses or deactivate records. Data update jobs are ad hoc jobs; they cannot be scheduled.This feature is available by default in your Network instance. With this feature: Users can update records without needing the Network training that the robust source subscriptions feature requires.Parent objects are not required. For example, to update an address, provide the Network entity ID (VID) for the address only; you do not need to upload the HCP associated with the address.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 updated.The following considerations apply for record and field support: Record state - Only records that have a VALID record state can be updated.Fields - The following are not supported for update: system fields (such as created_date__v, record_state__v), alternate keys, read-only fields, custom key fields, and entity_vid__v.Field ownership - Custom fields can be updated on OpenData or third party master records. Updates to OpenData or third party managed fields will not be processed on OpenData records or third party records.

Data Updater

US addresses can be reconstructed to ensure that they support downstream systems by containing the street number, street name, and suite number (if applicable) in Address Line 1.The US OpenData team will begin updating US addresses in batches to leverage the address lines reconstruction feature starting after release 19R3.0. Customers with both locally managed US records and OpenData US records should consider enabling this feature so all US addresses are standardized consistently. Administrators can enable this feature for locally managed US addresses in their Network instance. In the General Settings, enable the Address Lines Construction setting. When the feature is enabled, locally managed addresses are reconstructed whenever they go through the address cleansing process.

Match Against Veeva OpenData

Users that run ad hoc match jobs and source subscription jobs that also match against Veeva OpenData will see noticeable improvements in the processing time for their jobs.

Administrators and data managers can now disable subscriptions in their Network instance, which allows for more control in managing their 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 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.Subscriptions can be enabled again after they have been disabled. Any previously set schedules or job triggers on the subscription will be active again. The following types of subscriptions can be disabled: source subscriptionstarget subscriptionsdata maintenance subscriptions

Custom Keys and Merge

Active custom keys are now retained when a record is merged with an Veeva OpenData record that has an identical custom key that is source deactivated. Previously, in this situation, the active key on the losing record was not included on the winning record. This enhancement is enabled by default. Previous behavior New behavior Now, the active custom key from the losing record is copied over to the winning record to ensure that the winning record has an active key.

The Network bridge enables you to run and monitor data subscription jobs that export data from Network to Veeva CRM within Network. Previously, these jobs were run from Veeva CRM using the Network Subscription Process.The Network bridge integrates the CRM account mappings so the target subscription files are transformed into Veeva CRM format. Veeva CRM accounts will be updated with the data from Network; for example, accounts will be merged or deactivated, and addresses can be updated with license data (DEA, SLN, CDS, ASSMCA, OhioTDDD). This feature is enabled by default for new Network instances. The Network bridge can be enabled by request for existing instances; manual migration steps are required. Note: The previous version of the CRM bridge that uses the CRM Data Subscription will be sunset in Veeva CRM version 20R3. 

The Network State License Mappings is updated to include the rxa_eligible__v field. Currently, the license mapping includes the license_eligibility__v field which reflects an HCP's prescriptive authority. The RXA eligible field identifies an HCP's sample authority eligibility by state, degree, and license. Sample eligibility and prescriptive authority can be different, depending on state laws.You can customize your CRM sample formulas to use one or both sample eligibility fields to determine which information to use to know if an HCP is eligible to receive samples. License mappings are as follows: Network (License): Sample Eligibility rxa_eligible__v (formerly Prescriptive Authority license_eligibility__v) Veeva CRM (address_vod__c): Network RXA Eligible Network_RXA_Eligible_vod__c (formerly Network Prescriptive Authority Network_Sample_Eligibility_vod__c)To backfill your license data, use the Network bridge to resend HCPs with a full extract from Network. The sample eligibility data will be loaded into CRM using the CRM Data Subscription process. Data change requests (DCRs) should not be submitted to update the field. Note: These license updates will be supported in Veeva CRM version 19R3.0. More information will be available in the Veeva CRM 19R3.0 Release Notes.

Updated State License Mappings

The Network API is updated to v19.0. API enriched results The following parameters have been added to display reference type labels in the supported API: enrichedResults (optional) - True or False (default)resultLanguage - (optional) - Use the language code; for example, EN. If this parameter is not provided, the requester's language is used (typically English). It is recommended to supply this paramter with the enrichedResults parameter.Example: "medical_degree_1__v": "MD", "medical_degree_1__v_value__u": "Doctor of Medicine",Then new parameter is supported for the following API SearchRetrieve/batch retrieve entityRetrieve child entity

The primary_country__v field for HCP and HCO objects will be read-only starting in version 19R3.1. The primary country is defined when a record is created. Previously, the field was editable. 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. Because reference data is managed by country, if you change a record's primary country the existing reference values might be incorrect. Changing the primary country can also cause users unexpectedly losing access to records because of their data visibility profile permissions. This update will impact the following 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.Network API - Changes for the primary_country__v field will be denied. The response will display a Failure message for the field.This enhancement is planned for version 19R3.1.

The Revision History preview box on the profile page now displays the name of any source systems created by administrators; for example, concur_system. Previously, the system description displayed; for example, the preview box displayed Update from Concur. This enhancement ensures that the information in the Data Sources preview box and the Revision History preview box are aligned.

This new permission feature allows administrators to provide more granular access to custom objects by using rules that are assigned to specific users. Dynamic access control can be enabled on each custom object in your Network instance. When it is enabled, access to the object is permitted only through the rules to the defined users. Users must also have access to the object through their data visibility profiles.

This feature is available for custom objects that are enabled in your Network instance. Dynamic access control can be enabled on each custom object. It can be disabled on the custom object after it has been enabled. Dynamic access control works with data visibility profiles (DVPs) to provide access to individual custom objects. When dynamic access control is enabled for a custom object, no user can access the object until rules are created and assigned to user groups or individual users. If the rule conditions are met and users have access to the custom object through their data visibility profile, they will have access to the custom object records that meet the rule criteria. For custom objects, DVP access is either all access or no access. If dynamic access control is disabled, permissions to access custom objects are defined only through a user's data visibility profile. This is the existing behavior that has always determined access to custom objects.

A summary of all dynamic access control rules in your Network instance is available in the Admin console (Users > Dynamic Access Control). This tab displays if custom objects are enabled in your Network instance.The summary page lists any rules that have been defined for custom objects. You can do the following actions on this page: Create a new rule - Only custom objects that have dynamic access control enabled will be available for the new rule.Edit an existing rule

Dynamic Access Control Summary