Future Release

API

Subscriptions

Data Quality

Future Release

Reporting

Inbox View

Data Model

Data Managers

Data Cleansing

22R2

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

Hierarchy Explorer

Administrators

Data Lineage

Standard Users

Primary Address

Flattened Hierarchies

Data Sources

Transformation Queries

Integrations

Hashtags in CRM

22R1.1

Data Stewards

Smart Tables

All Users

Network File System

View Docs

Health system searchOn the Hierarchy Explorer landing page, you can search for the health system that you want to explore. You can now click the Search icon to open the list of health systems that are available in your Network instance. The health systems are listed in alphabetical order. Note: The Hierarchy Explorer widget is available in Beta version. If you are interested in being an early adopter, contact Veeva Support.

Clear filters The Active Filters dialog is updated to include the option to clear all of the selected filters. Click Clear All HCO Filters or Clear All HCP Filters to reset your selections.

Hierarchy Levels When you download a hierarchy or selected records, the Hierarchy Level column now displays in the exported file. Levels are the distance between the HCO at focus and the HCO in the hierarchy. For example, if the HCO is directly connected to the health system, the Hierarchy Level value is 1. Tooltips Tooltips display when you hover over links to provide information about what happens when you click.

A new table called flat_hierarchy is added to Network reports to help you report on relationship hierarchies. The table updates hierarchies once a day and displays all of the relationships and levels so you can see how HCPs and HCOs rollup to HCOs. Existing hierarchy reporting Using the existing parenthco table, you can view each entity and its direct parent HCO. You can create a SQL query and join the table with other tables, but this can be complex. Flattened hierarchy reporting Using the new flat_hierarchy table, you can view all the relationships and understand how HCPs and HCOs roll up to direct and indirect HCOs.

Administrators and data managers can now define rules to cleanse and standardize data in fields. Addresses are cleansed using Network's third party cleansing tool, but previously, there was no efficient way to cleanse and standardize other fields. Now you can create a data cleansing dictionary to do things like remove noise characters and words and replace strings with better strings. Use the data cleansing dictionary with a new Network expression function in a source subscription or a data model field to update specific field values. This feature is available by default in your Network instance.

Administrators and data managers can now include their own conditions for recalculating primary addresses for Unique Checkbox primary fields.  This is helpful to ensure that the address that is the most relevant for your business purposes is selected as primary. For example, an address that is outside of the sales territory could be calculated as the new primary because the existing primary recalculation logic does not consider postal codes. You can now specify the fields that you want Network to consider during the primary address recalculation. This enhancement is enabled by default in your Network instance. It is supported only for Unique Checkbox primary address configurations.

Veeva OpenData - Export job error logs Administrators can now export the job error log after an OpenData subscription runs to further investigate the issues. This enhancement is enabled by default in your Network instance. Source Subscriptions - Source file column headers Administrators and data managers can use a new property rule to format column headers to use either lowercase (default) or uppercase letters. Currently, the column headers for source subscriptions are case-sensitive which can cause data loading issues. This feature is not enabled by default.

Integrations - SAP Concur Authentication

The SAP Concur Connector will be updated to use OAuth2 authentication in this release. The Network Concur Connector is currently using an API for Veeva OpenData downloads that SAP Concur is decommissioning on June 30, 2022. Using OAuth2, Network can access SAP Concur and continue using that function. Existing customers will be automatically  migrated to use OAuth2 authentication.  New customers can create credentials that  use OAuth2 to connect their Network  instance to SAP Concur. This enhancement is available by default  in your Network instance.

API - Match Rule Connections

The Network Match API was introduced in version 21R3.0 to enable you 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.By default, the Match API uses the country default match rules for your Network instance. Now you can create and use match rule collections that contain country groups that share custom match rules and data groups. Match rule collections are independent of subscriptions and other Network processes, so you can customize them for specific purposes. This feature is enabled by default for your Network instance. The following new parameter enables Integration users to use custom match rules in the Match API to match data immediately for a single record: matchRuleCollection - The name of the match rule collection to be used for matching.This is an optional parameter. If it is not specified, the country default match rules are used. The response includes the following: matchSetup - Information about the match configuration used.

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

Permission Sets

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.

System Audit Log

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.

Use smart tables to open, view, and augment .csv files directly from File Explorer. This enables you to share and view files within Network. Smart tables are helpful for users who do not have robust reporting and Network data model knowledge. You can easily add Network data in bulk to the file and download the changes. For example, if a file contains a list of Veeva IDs (VIDs) but you need more data to analyze the content, you can add Network fields to the file to view that data. This feature is enabled by default in your Network instance if the File Explorer feature is enabled. Note: Users must have FTP access to use the File Explorer.

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.

DCR Cleanup

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.

The Current Source column is added to display the name of the source that provided the winning value for each field. Some fields display values other than a source name if the field value was updated by Network. Updated by System - System fields that are updated by Network. This value also displays for data that was calculated by Network using rules before these enhancements were released.Calculated Value - Field values are calculated by Network rules (for example, fields updated by NEX rules, default values, or primary values when a source file does not contain a value).

Data Lineage - Current Source Column

Addresses, licenses, and parent HCOs now contain a summary so you can easily view relevant information about the sub-object. Additionally, these sub-objects are now sorted so the active objects display before the inactive objects. Inactive objects display so you have a history of specific addresses. You can remove inactive sub-objects using the Show/Hide button. These enhancements are enabled by default in your Network instance.

Data Lineage - Sub-Object Details

Veeva OpenData data models have been added for countries in Latin America and Asia Pacific. Latin AmericaBolivia (BO)Paraguay (PY)Uruguay (UY)These data models are duplicates of the Mexico data model. They are based on the Other Countries (ZZ) data model and include additional fields so they are consistent with other Latin American OpenData data models. 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 Latin America OpenData team. Spanish (es) translations will be used for the Network UI and data model fields. Spanish-Mexico (es-MX) translations will be used for reference data. Asia PacificIndia (IN)Indonesia (ID)Malaysia (MY)Philippines (PH)Thailand (TH)Vietnam (VN)The data models are based on the Other Countries (ZZ) data model. The data model also includes additional fields so they are consistent with other Asia Pacific OpenData data models. 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 Asia Pacific OpenData team. English (en) translations will be used for the Network UI and data model fields. Australian English (en-AU) translations will be used for reference data.

Data privacy opt outVeeva OpenData now manages HCP opt outs in the following countries: India (IN)Indonesia (ID)Malaysia (MY)Philippines (PH)Thailand (TH)Vietnam (VN)Two data model fields have been enabled for these countries 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. The opt_out__v field is also enabled for these countries. The field is used to guide marketing usage of records in these countries. Cluster managementCustomers can enrich addresses by adding cluster codes from third party cluster providers. In this release, Network has included support for the following countries for the cluster provider, IQVIA™. AustraliaCzech RepublicPortugalSlovakiaA TPA must be signed with the third party cluster provider to use the cluster management feature.

Enhancements have been made to data model field configurations so it is easier to manage default values and NEX rules for your Network instance. In the Country Visibility and Field Rules section, the input boxes are bigger for the Default Value and Nex Rule rule types. The NEX Rule box can be resized so you can view the entire rule. These enhancements are  enabled by default in your  Network instance. They apply  to the Managed by Customer  section for standard fields and  custom fields.

Data Model - Field Configurations

Administrators and data managers can configure third party source systems to support data change requests (DCRs) for customer managed fields on unverified records. This will route change requests for customer managed fields to local data stewards. This is helpful when you want to add information to a new third party record but the record is still pending approval from the third party data provider. For example, if you want to add an HCP's email address on an unverified third party record, the DCR is rejected because the third party data provider is still processing the add request.  Now, you can submit the DCR and local data stewards can process the request. When the third party record is approved, the local updates are merged. This enhancement is available by default in your Network instance. Administrators must enable support for these DCRs in the third party system configuration.

DCR Routing for Third Party Systems

Parent HCO Field

When the Parent HCO object is selected as a DCR Enabled Field on a third party system, the parent_hco_vid__v field is now automatically moved to the Selected Fields pane. This field is mandatory for the Parent HCO object integration.After the parent_hco_vid__v field is moved to the Selected Fields pane, it cannot be removed unless the other Parent HCO fields are moved back to the Available Fields pane. This behavior currently exists for HCP and HCO objects; when those objects are defined in the DCR Routing Criteria for a third party system, the HCO/HCP Type fields and the Primary Country field are automatically selected. This enhancement is enabled by default in your Network instance.

Hierarchy Explorer Widget - Rollup Counts

The Hierarchy Explorer widget now displays rollup counts for HCOs to help you understand the size of the health system. The Direct and Total counts display for each HCO in the list. Using the Total count, you can immediately see how many HCOs are indirectly related to the health system. Click a count to focus on that HCO's hierarchy.

You can now apply filters on the first level of a hierarchy so you can view the hospital hierarchies in the health system. Currently, when you filter a hierarchy on hospitals, it filters every level and displays hospitals only; the hospital's children are not shown in the hierarchy. Using the new Smart Hierarchy Filter, you can see the hospital and all the HCOs in the hospital's hierarchy; for example, clinics and departments.

Hierarchy Explorer Widget - Smart Filtering

Level columnThe Explore HCOs tab contains a Level column so you can easily see what level the HCO is at within the health system. FullscreenTo give Hierarchy Explorer more screen space so you can better view the data, two enhancements are introduced: Fullscreen mode - Click Fullscreen in the header to expand the widget to your full browser screen and hide the Network Portal details at the top.Hidden navigation pane - If the application in the Network Portal has one widget only, the left navigation pane is removed by default.

Hierarchy Explorer Widget

Administrators can configure Network hashtags to display in Veeva CRM. Hashtags can help CRM users find correct records faster in Network Account Search and throughout the CRM application (both Online and iPad). For example, hashtags help with the following:Summarize a profile so you can identify HCPs and HCOs that have similar namesView more accurate search results when hashtags are appliedIdentify HCPs and HCOs that are marked as key targets from market flagsHelp find the HCOs that have sales data associated to itPrevent add requests from being created for duplicate records because it's difficult to find existing accountsNetwork hashtags are available by default. CRM administrators must configure some settings to support Network hashtags in Veeva CRM.

When Data Stewards make changes to their inbox view, they can now save the changes as a new view. Previously, when Data Stewards clicked Save changes, the current inbox view was updated with the change. Now, a pop-up displays so the updates can be quickly saved as a new view.On the Save Inbox View pop-up, Data Stewards can choose one of the options: Save as a new view - Create a new view. The column layout, filters, and table settings from the current view will be saved to the new view. This is the default option.Replace an existing view - Update the current view with these changes.This enhancement is enabled by default in your Network instance.

Inbox Views

Data Validation Rules

Data Validation Rules have been renamed to Profile Validation Rules. Validation rules for data loading jobs are introduced in version 22R2.0. This name change helps to differentiate the two types of validation rules that Network now provides.Profile Validation Rules - Apply to individual records and are used as data quality checks; for example, to ensure that mandatory fields are populated or that HCPs have an address.Job Validation Rules - Apply to data loading jobs to prevent unintended changes to large numbers of records.

Validating Suspect Match Data

Administrators can configure profile validation rules (previously called data validation rules) to run immediately after suspect match tasks are processed. Data Stewards no longer need to click Validate on the profile to run the validation rules. After Data Stewards apply a suspect match task, the profile page opens to display the surviving record and profile validation rules will run. If any of the validation rules fail, the Validation box displays the issues. If no validation rules fail, a success message displays. This feature is not enabled by default.

Administrators can create and manage data validation rules for source subscription and data updater jobs. Job validation rules will fail the data loading job if critical value changes try to occur on a large number of records.Examples of critical value changes include: updating mandatory name fields to NULLdeleting, invalidating, and inactivating recordsopting out recordsIf a validation rule is set and a defined number of records violate the rule, the job will fail before the data is loaded and these changes take effect.Job Validation Rules apply to source subscriptions and Data Updater jobs.

Job Validation Rules

Veeva OpenData data models have been added for the following countries:Egypt (EG)Jordan (JO)The data models are based on the Other Countries (ZZ) data model. The data models also include additional fields so they are consistent with other European OpenData data models.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 European OpenData team. English (en) translations will be used for the Network UI, data model fields, and reference data for both countries.

Veeva OpenData now manages HCP opt outs in the following countries:Egypt (EG)Jordan (JO)Two data model fields have been enabled for these countries 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.

Data Model - Data Privacy Opt-Out

Data Model - Network Address Inheritance

China can now be added to Network address inheritance configurations with other countries. Previously, China required a separate country group configuration because the address_type__v field was not included in the China data model. This meant that the Parent Address Type setting was not supported for China . This setting is used to copy the address from a parent HCO relationship.Now, if the address_type__v field is enabled for the address object, the Parent Address Type setting is supported and China can be added to a Country Group with other countries.

Network can now transform data before loading it into Network. Previously, transformation queries were available to use for data that you were exporting to downstream systems. Now you can use the transformation queries to pre-process data before it is processed and loaded during source subscription jobs.This feature is enabled by default in your Network instance. Use transformation queries to pre-process inbound data. For example: Process the output of a report - For example: Run a report to find HCPs that are flagged for opt out, but that are not opted out yet. The output of that query would then be the input file for the source subscription to opt out these HCPs.Process dynamic attributes from Veeva CRM - For example: This requires pivoting the data that is coming from CRM (converting rows into columns).Simplify data feeds and model maps - For example: If a source system provides a single file containing many entities, split the data into individual files so the model map can be simplified.Define field values based on certain conditionsSplit or concatenate fields

The Network API is updated to v27.0.The following value is now available for the returnHashtagsForType parameter for the Search and Retrieve Hashtag API: CRM - Display hashtags that are specific to Veeva CRM.Supplemental resultsThe returnHashtagsForType parameter supports hashtags for the supplemental parameter. The supplemental parameter returns related parent HCOs of the entities found in the supplemental results. If you use the supplemental parameter with the ALL or ONE value, the hashtags automatically display in the entity block.

The following Saved Reports will be discontinued in a future release:Merged HCO ReportMerged HCP ReportThese are legacy reports that do not use the current Network reporting warehouse.For best results, begin using the provided SQL queries for merged HCOs and HCPs. You can save the queries as saved reports.

Merged HCO and HCP Reports