Affiliation Widget
API
Future Release
Future Release
Reporting
Network Integrations
Source Subscriptions
Match
Inbox
Data Model
Data Managers
Search Widget
21R2
Click a point on the timeline to view features released in that version.
Data Privacy Opt Out
General Updates
Administrators
Network Portal
Target Subscriptions
Data Validation
Widget Profile Layouts
Network Widgets
Profile Layouts
Standard Users
Reports
Configuration Management
21R1.1
Veeva CRM Data
All Users
Data Stewards
View
Docs
The following enhancements have been made to the Influence Map to help you view and manage the accounts and views.
Bulk editingYou can now select multiple HCP and HCO accounts to manage at the same time. Influence maps can contain hundreds of accounts.
This enhancement is enabled by default in the Affiliation widget.
Display relationship infoYou can now choose how to display relationship information on the Influence Map.
Relationships labels can be useful for understanding how objects are related, but for some users, the connecting lines are sufficient. Using the Tools menu, you can decide how the information is presented.
This enhancement is enabled by default for your Affiliation widget.
Reposition relationship labelsUsers can now move the relationship labels on the connecting lines between two entities. This is helpful to avoid overlapping when Influence Maps are large.
This enhancement is available by default.
Affiliation Widget - Relationship Details
Filter by HCP/HCO
You can now use filters to highlight specific HCPs and HCOs on the Influence Map. When the filters are selected, records and relationships that are filtered out are dimmed so you can easily see which accounts apply to your selections.
You can also use the Filter section in the Tools menu as a quick overview of your health system. For example, you can easily see the number of Clinics or Infusion Centers in the health system.
The ability to filter is enabled by default in your Affiliation widget Influence Map.
Editing profiles
An Edit button is now available on profile previews so you can immediately update a record. This is particularly useful for updating the entity labels that display on Influence Map to support HCP and HCO filtering.
For example, if you download a record from Veeva OpenData and the field that you use for the entity label (for example, HCP Role or HCO Type) does not have a value, you can immediately add a value so that record can be included in filtering.
This enhancement is enabled by default.
Account list updates
The entity layout field now displays on records in the Account List to help you identify HCPs. Previously, the field displayed on the accounts in the Influence Map only.
Removing standard views
Standard views can no longer be deleted from the Influence Map. Previously, they could be removed by any widget user.
Standard views are created by Veeva Support upon request, so the Delete View option has been removed to prevent the views from being inadvertently deleted.
This change is enabled by default in the Affiliation widget.
Full screen support
The Affiliation widget can be viewed in full screen when it is embedded in Salesforce Classic™. Use the Full screen icon in the top right corner to expand the Affiliation widget.
This enhancement is not enabled by default.
Affiliation Widget - HCO Metrics
HCO Icons
The HCO type icons have been extended to include HCO types that are commonly used in Europe. In addition, the following icons have been added to improve branding for dentistry and infusion centers.
The HCO icons help you easily differentiate HCO types when HCOs have the same name. They are used for all record owner types (local, Veeva OpenData, third party data providers) and all record states.
These new specific HCO icons will be used throughout the Network UI, the Network Portal, and Network widgets. They are enabled by default.
Chinese Names
Chinese full names that contain the special interpunct (.) character will now be split into the first name and last name fields. Previously, the full name was copied into the first name field only. Now, names that contain this special character will be used to split the full name into first name and last name fields.
This enhancement is enabled by default in your Network instance.
The primary country field is added to the predefined NetworkWidgetsLayoutHCO and NetworkWidgetsLayoutHCP profile layouts.
The field is added to the Primary section of the layout. Adding this field ensures that there is a country associated with data change requests that are submitted through the widgets.
This enhancement is added by default in new Network instances and in existing Network instances.
Network Widgets - Profile Layouts
Users can now view external data related to HCPs, HCOs, and custom objects directly from the Network UI using data components.
Administrators can create a component to query specific data from Salesforce orgs (for example, Veeva CRM and Salesforce Service Cloud™) so users can access Salesforce data from Network record profiles. Data stewards can also access the data from data change requests.
For example, to validate a primary address change, Data Stewards can access the latest call data from Salesforce to verify the recent addresses that have been visited for an HCP; this helps them to know if the change is valid.
This feature is enabled by default in your Network instance.
Profile layouts are updated to provide more information about each configuration and where it is being used.
These enhancements are enabled in your Network instance by default.
Parent HCOs that are included in subscription feeds will be dropped or rejected if the related entity is not Valid or Under_Review.
Occasionally, parent HCOs included in the feed have relationships to HCOs that have Invalid or Merged_Into record states. Now, to improve data integrity, these relationships will not be processed; the Parent HCO record will be dropped when the data is processed.
This enhancement is enabled by default. It applies to candidate records and opted-out records also.
Job warning
After Veeva OpenData subscriptions run, if any Parent HCO records were not downloaded, a job warning displays; for example:
A new PARENTHCO record was dropped from HCP <938061682273812525> due to related entity <938061682274730046> being not valid.
In Network Portal applications, the Advanced Settings section for Search widgets now includes the following settings for searching, downloading, and editing records:
Search Local Only - Search results display records that exist only in your Network instance. Records that have not yet been downloaded from Veeva OpenData will not display. This can help to reduce search results and prevent users from seeing results that are not relevant.
Background Search Exclusion Filter - Excludes specific records from all search results.
Display OpenData Download Button
- Choose whether
users can see the
option to download
the record from
Veeva OpenData.
Hide Edit button
- Do not display the
Edit button on the
profile page to prevent
users from making
changes to data.
Network Portal - Search Widget
The Advanced Settings section for Affiliation widgets in Network Portal applications is updated to include specific settings to restrict editing and to display HCO metrics.
Hide Edit Mode - To prevent users from making changes to data, do not display the Edit button on the profile page.
Display HCO Metrics - Display metrics for HCOs. The existing metrics that are used for HCPs can be applied to HCOs.
Network Portal - Affiliation Widget
The formatted_name__v field for HCPs is now available to add to data groups and match rules in match configurations. Previously, the field could be used but only in advanced mode. Now, you can select the field from the lists in the Match Configuration UI.
If the field is empty in the incoming data, it cannot be added to data groups. The default rules to populate the field typically take affect after the match process completes.
This enhancement is enabled by default in your Network instance.
Administrators can configure field and object settings on custom profile layouts to simplify add and change requests submitted through Network widgets.
Add requests are often rejected because the standard request form contains too many fields and too many field values. Profile layouts can be simplified to identify required fields and objects and to display only the relevant field values.
Administrators can:Designate required fields and
sub-objects
Mark specific fields and
sub-objects as required.Populate default field values
Select a default value for a field.
Users can change the value or
accept the default.Limit available values
Simplify field value choices by
identifying the specific reference
values that will be available.
Batch reject/approve change requests
You can now insert resolution note comments or codes for each data change request (DCR) when they are automatically accepted or rejected using the Batch API calls.
Previously, a default resolution note was applied to each DCR. Now, users can view the specific comments to know why the DCR was rejected.
Parameters
Two optional parameters have been added to the Batch Reject Change Request and Batch Approve Change Request API to support this enhancement.
comment - A text resolution note.
code - A code from your resolution note template will be inserted as the note.
You can use the comment parameter or code parameter (if you have a resolution note template). If you provide both, the comment will override the template.
Reporting Database Improvements
Infrastructure improvements have recently been made to the Network reporting feature. With these updates, you'll notice the following improvements:Reports complete faster.Reduced timeout errors.Fewer failures with saved reports.These improvements are part of our ongoing focus to improve your experience with the reporting feature.This enhancement is enabled by default in your Network instance.
Source Subscriptions - Wizard Mode
The subscription wizard is enhanced to support complex denormalized feeds that contain multiple objects of different types and the relationships between them.Additionally, usability improvements have been made to simplify the object configuration process throughout the wizard steps.
The following enhancements are included in this release:
File validation - Errors occur if column headers include spaces or special characters.Multiple object support - Files can now contain up to 10 objects, all object types (main objects, sub-objects, and relationship objects), and multiple objects of the same type.Custom keys - Keys can now be defined in the wizard.Field mappings - Usability improvements have been made to simplify mapping.These enhancements are enabled in your Network instance by default.
Network API
The Network API is updated to v24.0.
As with all version updates, Integration Users should continue to use v23.0 until there is a change for v24.0 that they want to apply.
Network now supports exporting data directly to your private cloud storage. In this release, exporting data from target subscriptions to Amazon's Simple Storage Service (Amazon S3™) is supported.
This feature is enabled in your Network instance by default.
Target Subscriptions - Exporting Data to Cloud Storage
A new property is now supported to restrict users to search results in your Network instance only; results from Veeva OpenData will not display.
Using this setting returns a significantly fewer number of results and prevents users from seeing records that might not be relevant.
search-local-only="true"
Web developers can add this property to the generated widget code in your internal application.
You can now drag and drop tables, fields, and reference codes from the SQL Query Editor tree view into the query box so you can easily build your query.
This enhancement is enabled by default in your Network instance.
SQL Query Editor
Administrators can assign a new user permission called Report Results so users can run reports without any data restrictions applied.
By default, when you run a report, the results are based on the data that you have permission to access. This means that each report query is rewritten to calculate your data visibility profiles, inbox task groups, and any dynamic access control restrictions for custom objects. This can cause the query to be slow or to timeout.
When your data permissions are ignored, the queries and reports will complete faster and fewer timeout errors will occur.
Reporting Permissions
Custom object support
Data validation rules can now be added for custom main objects, sub-objects, and relationship objects. Previously, data validation rules supported Veeva standard objects, sub-objects, and relationship objects only.
This enhancement is enabled in your Network instance by default.
When custom main objects and sub-objects are enabled in your Network instance, they will automatically display in the list on the Data Validation Rules page; data does not have to be loaded into the object before they display. Rules are not automatically created for new custom objects; they must be defined.
Operand support for field sets
Some operands have been extended to support field sets (for example, set_of_addresses__v). The operands can be used to create rules to check for a specific count of sub-objects and relationship objects.
These operands support field sets: Equals, Not Equals, Less Than, Greater Than, and Between.
Data validation rules page
The list on the Data Validation Rules page is updated to help you easily view the supported objects and their existing data validation rules:
All object sections - All sections are collapsed by default so you can easily browse the page. Previously, each section was expanded by default.
Main objects - These sections now contain the object icon and a count of the enabled rules. Expand the object to view the rules.
Sub-Objects- This section lists all enabled sub-objects and relationship objects in your Network instance. A count of the enabled rules for all listed objects displays.
Disabling fields
When you disable a data model field, the confirmation message now lists the impacted data validation rules so you remember to remove the field from the rule.
Disabled fields are not automatically removed from data validation rules. If a disabled data model field is included in a data validation rule, the rule can still trigger but the field is no longer accessible in the Network UI. This means that Data Stewards cannot resolve the rule violation and continue processing a record change.
Including this information in the confirmation message reminds administrators to update the data validation rule.
Profile page enhancements
When data validation rules are triggered on record profiles, they display in the right pane above the preview boxes. The pane now remains in place when you scroll through the profile page.
This is helpful when Data Stewards are resolving validation issues because the message remains in view as they scroll. This also means that the preview boxes are always in view on the profile for all users as they scroll the page.
Widget users can now take a screenshot of the Influence Map canvas using the new Take Screenshot tool.
Previously, it was difficult to take a high quality screenshot of the entire map. Using this tool, it's easy to snap an image to display in a presentation or to share with others.
This enhancement is enabled by default in your Affiliation widget.
Affiliation Widget - Influence Map
Advanced reporting users can report on the Affiliation widget data in their Network instance. Use the reports to summarize the data in your views. The reports can be downloaded and shared with other users or sent to your downstream systems.
The following new tables are available in the reporting tree view in the SQL Query Editor:
aw_view - List of all the views created for the
Affiliation widget in your Network instance.
aw_view_entity - List of entities that have
existed in a view.
aw_view_relationship - List of relationships
that have existed in a view.
These reporting tables are available if the
Affiliation widget is enabled in your Network
instance.
Affiliation Widget - Reporting
The text and nodes on the Influence Map have been increased to improve readability. The node size and font for HCOs and HCPs has been increased so they are the same size as health systems on the Influence Map. The font size for relationship labels has also increased so they are easier to read on large maps.
These enhancements are enabled by default in your Affiliation widget.
Affiliation Widget - Font Sizes
Custom Object Dependencies
You can now remove data domains from export packages if at least one domain remains in the package for the main custom object.
There is an automatic dependency between main objects and data domains. If you have a custom object in two different domains; both data domains are added when you move the custom object into the export package.
Previously, if you tried to remove a data domain and then you clicked Validate Selection, the domain would be moved back into the export package. Now, the domain is no longer added again if one domain remains in the package for the custom main object.
This is helpful if you have data domains in your development environment that you do not want to export to production environments.
Note: If you remove all data domains, they will all be moved back into the package when you validate the export package .
This enhancement is enabled in your Network instance by default.
Opt-Out Match Settings
The opt-out match settings can now be exported to target environments.
When you are creating an export package, you can select Opt Out Matching Settings in the Available Configurations pane.
This enhancement is enabled by default in your Network instance.
The inbox is updated to add sorting ability to more columns. This helps data stewards to quickly group tasks based on specific criteria.
For example, data stewards can now sort tasks by parent affiliations to find and verify multiple HCPs working at the same parent HCO. Previously, data stewards had to filter and search for specific criteria.
Highlighting has also been added to the inbox so you can easily identify the columns that are sorted, searched, or filtered.
This enhancement is enabled by default in your Network instance.
Inbox Sorting
Data change requests and suspect match tasks now include the completed date and time so data stewards can easily investigate closed tasks.
This enhancement is enabled by default in your Network instance.
Inbox - Date Completed
A custom calculation has been added for the formatted_name__v field for Singapore. The formatted name uses values from several name fields to display a complete name for an HCP.
This enhancement is enabled by default in your Network instance.
Name calculation
HCP names for Singapore are calculated using these Veeva fields in the following order:
prefix__v + first_name__v + middle_name__v + nickname__v + last_name__v
Data Model - Formatted Name
OpenData data models have been added for countries in the following regions, based on the Other Countries (ZZ) data model. Additional reference codes are provided by respective OpenData teams.Asia Pacific
A data model has been added for South Korea (KR).Localization - 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.Europe
A data model has been added for Albania (AL). The data model also includes additional fields so it is consistent with the EU OpenData data model.Localization - English translations will be used for the Network UI, data model fields, and reference data.Latin America
A data model has been added for Ecuador (EC) and Peru (PC). The data model also includes additional fields so they are consistent with other Latin American OpenData data models. Localization - 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.
Data Model - New Country Support
Data Model - ERD View
The ERD view in the data model is updated with increased font sizes, tooltips that do not scale, and scale percentages on the zoom control.
These updates are enabled in your Network instance by default.
Veeva OpenData now manages HCP opt outs in the following countries:
Albania (AL)Australia (AU)Singapore (SG)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 Privacy Opt Out Date
The Customer Data Privacy Opt Out Date field will become read-only in Network version 21R3.0. The field was introduced in version 20R3.1 to capture the date that the data privacy opt out flag is set to True.
The field has been editable so administrators could backfill the date on locally managed HCPs records that were opted out before the field existed.
If you are planning to backfill the Customer Data Privacy Opt Out Date field, the updates must be completed before version 21R3.0.
This update will be enabled by default in your Network instance in version 21R3.0.
Network instances that use the CRM Data Subscription will be migrated to the Network Bridge by October 1, 2021. The Veeva Network team will contact customers to help with the migration. To initiate the migration process now, contact Veeva Support.
The Network Bridge has been in production for early adopters since version 18R1.0. The migration process has been available to do (through a Veeva Support ticket) since Network version 20R2.1.
For more information, see the Network Bridge migration process topic in the Veeva Network Online Help.
Network Bridge Migration
Network Bridge Multi-Country Support
Administrators can now configure a Network Bridge to manage and maintain the CRM data subscription process for multiple countries.
Previously, a Network Bridge and target subscription was configured for each country which could be time-consuming and difficult to maintain for global customers. Now, you can create a single Network Bridge and apply the configuration and target subscription to many countries.
This enhancement is enabled by default in your Network instance.