Veeva OpenData Subscriptions

Future Release

Integrations

Future Release

Sub-Object Workflow Settings

Source System Types

Data Visibility Profiles

Data Validation Rules

Network Integrations

Reporting Tree View

Lookup Tables

Data Managers

Record State Property

20R3

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

Browser Support

Administrators

Address Cleansing

Network Expressions

Network API

General Updates

ERD View

API

New User Type

Standard Users

Inbox

Profiles

20R2.1

Exported Files

All Users

Data Stewards

Job Error Log

Welcome Email

View Docs

Network instances that use the CRM Data Subscription to export data from Network to CRM will automatically be migrated to the Network Bridge. The Network Bridge enables you to run and monitor these data subscription jobs within Network. The Network Bridge has been in production for early adopters since version 18R1.0. Note: The previous version of the CRM Bridge that uses the CRM Data Subscription will be sunset in Veeva CRM version 20R3.0.

Network Bridge Migration

Delta ID Incrementation for Veeva CRM

Network now increments the delta ID for entities related to rejected data change requests so records remain synced between CRM and Network. Veeva CRM users can immediately save updates to DCR_Editable fields in CRM before the changes are processed by data stewards. However, if the data change request is rejected, the record is not considered changed in Network and is not included in the subsequent target subscription. This means the field value in CRM is now out-of-sync with Network. To prevent this, Network will increment the delta ID for any rejected DCRs so the target subscription includes the record to update CRM. For example, if you configure email fields as DCR_Editable in CRM, when a user updates an email in CRM but it is rejected in Network, the target subscription updates the record in CRM so the email value becomes synced with Network again. This enhancement is enabled by default in your Network instance.

The Veeva Connector for Nitro is updated to use Intelligent Load. The runTaskJob in the CTL file will be set to jb_ftp_intelligentload__v. To support Intelligent Mode, the Nitro Connector jobs will export individual .gz files to your FTP server. Previously, .zip files were exported. Using .gz files avoids issues that occurred when Network uploaded the files because of special character handling for .csv files. These changes are enabled by default.

Veeva Connector for Nitro

Support for Internet Explorer™ 11 will end in Network version 20R3.0.

An entity relationship diagram (ERD) view is now available for each data domain in your Network instance. Use this view to get a better and faster understanding of your data model. This is also helpful to use for reporting to understand what tables you can join in your SQL query. The view is read-only, but if you update your data domain the view immediately refreshes so you can see the changes. This feature is available by default in your Network instance.

Administrators and data managers can add a new advanced property to source subscriptions to determine which records should be updated based on record state.  Updates to non-valid records (merge losers, invalid or deleted) typically have no benefit because they are not visible in the Network UI. Updates to merge losers are not shared with the winning record. So, although these updates are lost, they are still processed in other subscription jobs (for example, target subscriptions). The record state property specifies that only valid records are updated to reduce processing times. This property is available in your Network instance by default. If the property is not defined, the default behavior (ANY) is applied to new and existing subscriptions to ensure that existing behavior in your source subscription does not change. job.merge.allowUpdatesForRecordsWithState Supported values include:ANY (default)VALIDINVALIDUNDER_REVIEWMERGED_INTO

Target Subscriptions - Exported Files

Target subscriptions now contain options for defining the exported file format and file name. This enhancement enables you to have more control over the exported files. This enhancement is enabled by default in your Network instance.

Sub-Object Workflow Settings

Administrators can now define routing rules in the workflow settings so sub-object (address, license, parent HCO) add requests are routed directly to local data stewards, even if the object is owned by a master data source. If the add request was  accepted, the sub-object was created and a local DCR was routed to local data stewards to process custom fields. If the add request was rejected, the DCR was routed to local stewards if the review rejection setting was enabled. Now, you can define rules to route sub-objects directly to local stewards. For example, if you define a custom address type, you specify that any add requests with that address type are routed.

A new user type called System and Data Admin is now available. This user type combines the System Admin and Data Steward capabilities so you no longer need alternate user IDs to completely manage your Network instance. As a System and Data Admin user, you have complete access to Network; all the capabilities of the system administrator user plus the data steward user. This new user type is available by default in your Network instance.

Administrators now have the option to configure a Veeva OpenData subscription so opted-out records for Veeva OpenData HCPs are automatically converted into customer-managed records. Today, when HCPs opt out of OpenData, the record is no longer actionable; it disappears from your Network instance and is masked in Veeva CRM. However, some HCPs that opt-out of OpenData still consent to customers continuing to store and process their data. In this case, Network can convert the OpenData record into a customer-managed (local) record that keeps the same Network entity ID. This enables you to retain the history of transactions and to continue engaging with the HCP.  This setting is disabled by default. When enabled, it only applies to future records that are opted-out of Veeva OpenData; it does not apply to previously opted-out records. This enhancement is available in all Veeva OpenData country subscriptions in your instance; for countries that do not use the opt-out feature, this setting has no impact on their data.

Veeva OpenData Subscription Opt Outs

The filter labels that are used to subscribe to additional HCPs and HCOs in country subscriptions are updated to more accurately reflect how the filters actually work.

Veeva OpenData Subscription Filter Labels

The new user welcome email now includes the user type and Network instance URL details.When administrators create new users, a welcome email is sent to the user if the Generate temporary password and notify user option is selected. Users can click Log In to Network to navigate to the instance's login page to change their temporary password. This enhancement is enabled by default.

The SQL Query Editor now contains a tree view of the data domains and additional reporting tables available to you to query against in your Network instance. The tree view gives you the visibility to see your data model and reporting structure to help you create queries. Each data domain and reporting table category can be expanded so you can view its tables, fields, field metadata, and reference codes. Use the tree view to become familiar with the data model structure and to help you build your query by understanding the fields that can be joined. This enhancement is available by default in your Network instance.

Source systems now include a type and icon so it can be immediately identified as a Veeva system, SAP Concur® system, or custom system. This enhancement is available by default in your Network instance. The following options are available:ConcurCustom (default)Veeva CRMVeeva NitroVeeva Vault

Integration users can now exclude records from search results using custom fields without excluding Veeva OpenData results. Previously, any filters used on custom fields automatically excluded Veeva OpenData-only records because those records do not have the custom field. You can use custom fields to identify records the records that you want to exclude while still being able to search OpenData. The exclusion filter supports the following: Multiple valuesScoped entitiesField setsParent HCOs

Network API Search Filter Exclusions

Data Validation - Custom Keys

Data validation rules can now be created for custom keys on HCP and HCO objects. This is helpful if you manually maintain custom keys and need to validate the Source and Value fields; for example, to check for specific sources and the length of values.Data validation rules should run only on custom keys that have just been manually created on a record profile. When custom keys are saved, they cannot be edited. If validation rules fire for existing custom keys, data stewards cannot resolve the issue on the profile page; it must be resolved through data loading. These data validation rules must be thoroughly tested before they are used in production. This enhancement is enabled in your Network instance by default.

The following new functions are available for Network Expressions:LOOKUPN() - Look up values matching a key in a defined lookup table.JOIN() - Format an array of values using a delimiter.GETTARGETTYPE() - Check the entity type of a record.DELETE() - Delete objects and sub-objects during a data load.

NCPDP IDs Veeva OpenData subscriptions for the United States now contain the option to receive National Council for Prescription Drug Programs (NCPDP) IDs for HCOs.For compliance, Veeva OpenData can provide NCPDP data only to customers that have a NCPDP license. Previously, NCPDP ID data was available to all customers. There is no extra cost for enabling this subscription and receiving this data. Additional OpenData Parent HCO RecordsThe tooltips that displayed beside the Additional OpenData Parent HCO records options have been removed to avoid misrepresenting the count of records that could be downloaded The tooltips contained a count of the records that could be downloaded into your Network instance the next time the subscription job ran. This count could be vastly overstated because it could not reflect the filtering criteria that is applied before records are downloaded.

You can now include lookup tables in SQL queries. Previously, reporting was not supported for lookup tables. Now you can run a query so you can analyze the table data and generate reports. When lookup tables are loaded or reloaded into your Network instance, they are immediately available in reporting. Existing lookup tables will be automatically available to report on.All users with access to create SQL queries using the SQL Query Editor or on the Saved Reports page can run reports against lookup tables that have been loaded to their Network instance. The Basic Report Builder and Aggregate Report Builder do not support lookup tables. This enhancement is available by default.

The Read-only access permission on data visibility profiles is renamed to Data Read-only access because it restricts edit access to data only. If users have read-only access to data, they can view records, but they cannot add or edit records. Previously, the Read-only access permission prevented users from adding and editing reports as well as data if they only had one data visibility profile. The restrictions for reports have been removed so users with Data Read-only access can edit and create reports based on their user type. This enhancement is enabled by default in your Network instance.

The Job Error Log for now includes a Native Key column. If you set a native key in your source subscription, it will display in the error log so you can identify which incoming record experienced the error. This is helpful if the record does not have the Network entity ID (VID) as the key.The option to export the job error log to your FTP server is available in the General Settings section of your source subscription configuration. This enhancement is enabled by default in your Network instance.

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.

Profile Badges

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 v22.0. As with all version updates, integration users should continue to use v21.0 until there is a change for v22.0 that they want to apply.

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.

Administrators and data managers can now choose to enable address cleansing when they run a data updater job to update addresses. Address cleansing verifies addresses and parses the data into Network fields. Because cleansing can change the address data in your uploaded file, you might not want cleansing to occur; for example, if you are correcting postal codes on existing addresses. However, it is helpful to use Network's address cleansing to correct entire addresses. Now, you have the option to enable address cleansing depending on the address data in your .csv file. This enhancement is available by default in your Network instance.

Standard users can now see all tasks that are pending for a record. By default, standard users can view only the data change requests (DCRs) that they've submitted (on the My Requests page). Previously, on the profile page, these users could see that there are associated tasks for a record, but could view any details. Now, standard users can access the Associated Tasks link on record profiles to view the task information and drill into the task the way all other users can. This enables standard users to see what changes have already been submitted so they don't resubmit the same information.

Task Visibility

Sub-objects will now be deleted when candidate records are deleted. This ensures that administrators can load a new candidate record with the same key. Previously, when candidate records were deleted, only the record was deleted. The custom keys remained active and the sub-objects remained active and valid. When administrators loaded records with the same key using source subscriptions, it updated the deleted candidate record instead of creating a new candidate record.Now, when a candidate record is deleted, the following behavior occurs: Sub-objects are deleted (record state) and become inactive (record status).Sub-objects are removed from the candidate record's profile.Custom keys on the sub-objects become inactive.Custom keys on the object become inactive.

Candidate Records

Veeva Network no longer supports Internet Explorer™ 11.For optimal user experience, use one of the supported browsers: Google Chrome™ (most stable version at Network release)Safari® 10+Microsoft Edge™

Instances

Instance Environment TagsTags have been added to Production instances to help you quickly identify the environment you are using. Sandbox environments already contained a tag, but are updated to include the instance name in case you have multiple Sandbox instances. These tags are displayed for awareness, but also help prevent administrators and data managers from accidentally changing data in the wrong environment, which can be time-consuming and costly to fix. The Production tag is visible on all of the Admin areas in a Production instance. The Sandbox tag displays throughout the Sandbox instance; on the Network menu and in the Admin console. It now displays the instance name. If you have multiple instances, you can identify which instance you are in.Sandbox Instance URLsSandbox instances now have their own URL. Previously, Sandbox instances had a generic URL; for example, sandbox.veevanetwork.com. Providing a unique URL allows you to display the single sign-on button on your Sandbox instance's login page. There is no impact on existing API or FTP integrations. The previous URL for your Sandbox instance will still be valid.

Home Dashboard Widget

A new home dashboard widget, Data in my Instance, provides an overview of the data domains and records that are loaded in your Network instance. The widget is available on the Network homepage for administrators and data managers.Use this home dashboard widget to immediately find the following information: All the data domains that exist in the Network instance.All objects (standard or custom) that exist in these domains.The number of records loaded into the Network instance.

Primary Address

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.

Network Bridge

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.

The Integration Dashboard provides an organized view of all the integrations coming in and out of Network. Administrators can use the dashboard to track integration activities by system from a single location. The Integration Dashboard is enabled by default.

Integrations - Dashboard

Migration to Network Bridge Network instances that use the CRM Data Subscription to export data from Network to CRM will be migrated to the Network Bridge by spring 2021. The Network Bridge enables you to run and monitor these data subscription jobs within Network. It has been in production for early adopters since version 18R1.0. Network Bridge Error Logs The error logs can now be exported in Microsoft Excel (.xlsx) format. Previously, the logs could only be exported as .csv files. When .csv files are opened in Microsoft Excel, the Network entity IDs (VIDs) are automatically rounded, so exporting directly to Microsoft Excel ensures that the VIDs do not change. This enables you to easily view and copy the VIDs from the file. This enhancement is enabled in your Network instance by default.

Integrations - Network Bridge

Data in Veeva CRM and Veeva Vault can now be updated on a scheduled basis from Network reports using the Veeva Connector upsert jobs. The Veeva Connector can read the files generated on the FTP server from Network reports. The results are exported into unique subfolders which the Veeva Connector can now find the latest file during upsert jobs. This enhancement is enabled in your Network instance by default.

Integrations - Veeva Connector

Assigning Tasks

The Assignee column list now only displays active users from your inbox task group. Previously, the list also contained inactive users. Removing these inactive users helps the list to load more quickly.If you have an inbox view saved with an inactive user in the Assignee column, the tasks will no longer display in the inbox and the inactive user is removed from the Assignee list. If you click on the Assignee list, an informational message displays "This view has been updated. Save changes”. These enhancements are enabled by default in your Network instance.

Suspect Match

The Suspect Match page is updated to help data stewards more easily process matches. The following record information displays beside the record name so data stewards can quickly identify different types of records: Dead (HCP only), Inactive, Retired (HCP only), or Undetermined. The following record information will display: Candidate or Opted Out (HCPs only). If an opted out record is also a candidate record or has one of these statuses, Opted Out displays; the opted out information takes precedence over the other statuses or candidate information. Matched records are highlighted and Surviving Record displays above the column. When a record is selected, a Select All link displays below the heading. If data stewards click Select All, the link is dimmed to indicate that no further actions are required for the individual field values. These enhancements are enabled by default in your Network instance.