Click a point on the timeline to view features released in that version.
Custom Merge Rules
Profile Layout Support
Veeva OpenData Subscriptions
Reporting Error Messages
Viewing Custom Relationships
The redesigned profile will become the default view in Network version 19R1.0. This update will be applied to all Network instances.
The header of the new profile contains convenient and key information at a glance, with contact details and related tasks, as well as options to toggle field ownership, empty fields, and expand or collapse page sections. Detailed online help and videos are available for more information.
New Profile - Preview Boxes
Preview boxes for Compliance Data, Network Explorer, Revision History, Data Lineage, and Find Suspect Match replace the links that were in the left navigation in the classic view.
These boxes display a summary so you can quickly view details without leaving the profile.
A Sample Eligibility box also displays on HCP and HCO records so sales reps can quickly determine if they can drop samples.
Each child object has a summary card so you can quickly and easily retrieve the most relevant details about that object. The card can be expanded for more detailed information.
Badges might display on the summary card to alert you about pending tasks, primary designations, inactive status, and so on.
New Profile - Summary Cards
Users can now submit change requests using the profile widget. They can update existing records by changing primary fields (such as name or type) or by adding or updating sub-objects.
When changes are submitted, requests are forwarded to the appropriate data stewards for processing, but new sub-objects are immediately available as under review so users can take action on the record.
New HCOs and HCPs cannot be added through the profile widget.
The profile layout for HCPs in New Zealand, NZStandard, has been updated to remove fields that Veeva OpenData does not use. The following medical degree fields have been removed:medical_degree_1__vmedical_degree_2__v
You can now move the pop-ups that display when you view profiles or search for and view affiliations in Network Explorer. Data stewards and data managers can move around the pop-ups that display when they are editing affiliations or adding objects.
This enhancement enables you to more easily view the canvas underneath the pop-up when you are reviewing affiliations. Previously, these pop-ups could only be docked to the right-side of the canvas.
Network Explorer- Dragging Pop-Ups
You can now use the Advanced Search form to search on a name from the related object in a relationship. When you search by entity type, the More fields list now contains the custom relationship objects and related object.
For example, you might need to find HCPs that participated in a study related to rheumatoid arthritis. Because HCPs and the custom object called STUDY are linked in a custom relationship object, if you search by the HCP entity type, the custom relationship object will display in the More fields list and you can select the related object.
This enhancement is enabled by default if custom objects are enabled in your Network instance.
Error messages for advanced ad hoc queries now display more detail to help users troubleshoot issues. Previously, a query could validate and run, but if an error occurred, the message Unknown Error would display. Now, the error message from the data warehouse also displays to provide more detail.
The following query validates and runs, but an error occurs because the query is trying to divide by zero. The Unknown Error message includes the error details from the data warehouse: Divide by zero.
The SSL certificate for veevanetwork.com is being updated in Network 18R3.1. The new certificate expires in 2021.
Only customers who explicitly download and install certificates on any site caches or proxy servers must update their certificates.
The following certificates must be updated:veevanetwork.com certificateIntermediate CA certificate cert
Administrators and data managers can now choose to have Network recalculate primary addresses that use the Unique Checkbox configuration.
This enhancement enables you to control the behavior of the primary flag using the options on the primary address custom field. Primary address calculations can be used for any address on any HCP or HCO. The HCP, HCO, and address objects can be locally managed or managed by Veeva OpenData.
The options for allowing Network to calculate the primary address support the following situations:The record DOES NOT HAVE a primary address - For records that do not have a primary address defined (the primary value is No Value, Unknown or No) Network will set a primary. Only valid, under review, and active addresses are considered.The status of the primary address is INACTIVE - For primary addresses where the address status is Inactive, Network will recalculate a primary address.The record state of the primary address is INVALID or DELETED - For primary address records that have been reviewed and are considered invalid, Network will recalculate a primary address.By default, none of these options are selected.
Primary Address Calculations
When primary options are selected, Network calculates the primary whenever new addresses are added to your Network instance or specific changes are made to an address.
The following events will trigger Network to calculate the primary:New address is added or specific fields on an existing address are changed using source subscriptions, DCRs, or the Network APIMerging records manually using Find Suspect MatchMerging records in bulk through source subscriptionsUnmerging recordsDownloading records from Veeva OpenData (using OpenData subscriptions or the Ad Hoc Download or Download from OpenData buttons on a record).Syncing a record with Veeva OpenData (using the Sync with OpenData button).
Primary Address Triggers
A data model has been added for seven new countries:
Bahrain (BH)Kuwait (KW)Lebanon (LB)Oman (OM)Qatar (QA)Saudi Arabia (SA)United Arab Emirates (AE)The reference data is based on the Other Countries (ZZ) data model.
To view the data model for these new countries, in the Admin console, click Data Model > Network Data Model. On the Network Data Model page, expand the Country list and select the country.
English translations will be used for the reference data in the Network UI.
A data model has been added for seven new countries:
Bahrain (BH)Kuwait (KW)Lebanon (LB)Oman (OM)Qatar (QA)Saudi Arabia (SA)United Arab Emirates (AE)United States (US)Records 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.
To review the list of opted-out countries in the data_privacy_opt_out__v field, in the Admin console, click Data Model > Network Data Model and select the field.
The default value for the Address Type (address_type__v) for New Zealand records has been changed to M (Mail Only). Previously, the default value was P (Professional).
When users add an address to a record, the Address Type field will default to Mail Only. Other values can be selected from the list.
Default Address Type - New Zealand
The search widget now only displays active addresses in the search results.
If there are no active addresses on a record, an address does not display in the search results. This enhancement ensures that users do not see inactive addresses.
You can now submit add requests from the search widget when you cannot find the record you are looking for. When you create a record, a data change request (DCR) is submitted to data stewards to validate and create the record in Network; however, the record is also available immediately in your internal application so you can action it.
This enhancement is enabled by default when administrators are configuring new search widgets. It can be enabled for existing search widgets.
Default Profile View
The redesigned profile is now the default profile view for all users in all countries. When you log into Network and view a profile, the new view will display.
Several enhancements have been made to the ad hoc match feature to improve the usability of the match configuration and to allow administrators to view ad hoc match jobs created by other users in the Network instance.
The enhancements have been added so you can do the following actions:
Match against the Veeva OpenData master instanceChoose the fields and the order they display in your exported ad hoc match fileSave the field export selections for future ad hoc match jobsDownload the input file that you used for each match jobView all jobs for the users in your Network instance that are available through your data visibility profile (administrators only)Most of these enhancements are enabled by default in your Network instance. The option to match against Veeva OpenData is available to customers that subscribe to all records for a country and must be enabled by Veeva Support.
Ad hoc match enables you to match an external file with data in Network. Depending on your match rules, the job can identify exact or high confidence matches that you can export and use for your business processes.
Enhancements have been made to the ad hoc match configuration so you can choose and arrange the fields to export. An option to match against the Veeva OpenData master instance is also available if specific requirements are met.
Performing an Ad Hoc Match
The Matched Files page has been updated to include more information and to enable you to download the input file that you used for each match job.
Administrators can now view the jobs for any users in their Network instance that share the same data visibility profile. This allows them to support users with their ad hoc match jobs.
Viewing Matched Files
Associated tasks display on data change requests to alert data stewards and data managers that there are additional tasks for that object.
DCRs have been updated to make it easier to see when there are multiple tasks for the same record and if they are assigned to another data steward. A highlighted box now displays below the link to provide task assignment information. This enables you to proactively assign those tasks to yourself or coordinate with the data stewards assigned to the other tasks to avoid making multiple calls to verify the data.
Several features in the Network UI have been updated to display timezones so users know exactly when events have occurred or will occur. This is particularly helpful for subscription jobs because multiple schedules can be set by users in different timezones.
The timezone that displays is based on the profile settings of the user viewing the time in the Network UI. To view your timezone setting, on the Network menu bar, click your user name and select My Profile. The timezone is defined in the Settings section.
This enhancement is enabled by default in all Network instances.
Veeva Network is now supported for the Microsoft Edge web browser.
Merge Instructions for Child Objects
Administrators can now define the behavior for each locally-managed child object when records are merged. Previously, the merge property for child objects was either on or off for all child objects, so if you wanted to retain parent HCOs but remove addresses licenses, it wasn't possible. You can now add a new property to define merge instructions for a specific child object.
This enhancement applies to bulk merge jobs and suspect matches when the winning record is a Veeva OpenData record.
Administrators can now define business logic for merge rules to ensure that field values are not lost or overwritten when two records are merged together. Previously, field values were not considered during record merges; the fields that were retained were determined either by source survivorship or the winning record. This caused some field values to be lost; particularly custom field values.
Now, custom merge rules can be defined for the field for each object for a country. If rules are applied to fields, they override regular Network survivorship rules. Custom merge rules can be applied to Veeva fields (__v) and custom fields (__c). Custom keys are not supported for merge rules.
This feature is enabled by default in all Network instances. Custom merge rules must be explicitly created for each object and country.
Managing Configurations with Custom Objects
Administrators and data managers can now include custom objects in configuration packages. This enables administrators to test a custom data model in their sandbox environment and then create an export package that includes the custom objects so they can be imported to a production environment.
This enhancement is available by default for custom objects that are enabled in your Network instance.
Custom relationship objects link related objects; for example, STUDIES and HCPs. Within the relationship, one of the objects is defined as the controlling object and the other is the non-controlling object.
You can now view relationships on the non-controlling object's profile page. Administrators and data managers can include the relationship on the non-controlling object's profile using the profile layout editor.
Administrators can now unsubscribe from records from third party master feeds and then anonymize the records in Network. This enhancement supports the GDPR requirements for allowing HCPs to request that their data is removed and also to remove data that is no longer needed; for example, to delete HCP records that sales reps no longer visit.
This involves the following steps:
Contact the third party providerCreate NEX rulesExport deleted recordsAnonymize personal data in those records
You can resubscribe to a third party record after it's been deleted and the personal data is anonymized in Network. For example, HCPs might give consent to process their data again, or you might find that a record has been unsubscribed to by mistake and your sales reps need to visit that HCP again.
Unsubscribing from Third Party Records
Veeva OpenData has additional capability to manage email subscriptions for customers who purchase emails for only a subset of records in the United States. This enhancement ensures that you receive regular updates for email data for the records that are outlined in your contract.
The Additional Permissions section on user profiles has been updated to more accurately reflect the setting options. Previously, the value for each permission was Allow All or Don't Allow.
Now the permission values describe the options more clearly. Additionally, the permissions have been reorganized on the User page because some permissions are dependent on the value of others and might not need to display.
These usability enhancements are enabled by default in your Network instance. The label changes and reordering do not impact any of the permissions set for existing users.
Permission updatesThe permissions that display on the User page depends on the user type (data steward, integration user, and so on).
Additionally, some permissions are dependent on other permissions, so they might not display if the parent permission is not available to the user; for example, the Reporting Ad Hoc Queries permission does not display if the Reports permission is set to Hide Tab.
The Network API is updated to v17.0. Currently, there are no changes from v16.0. As with all version updates, integration users should continue to use v16.0 until there is a change for v17.0 that they want to apply.
Create unverified recordsThe create_unverified parameter is now supported for the Change Request API. Integration users can specify which DCR API calls create unverified records.
This API call overrides the Network workflow settings defined for HCPs, HCOs, addresses, and parent HCOs. The parameter can either allow or prevent an unverified record from being created.