What's New in 23R3.5
Our release notes offer brief, high-level descriptions of enhancements and new features.
Not all functionality documented is available in Vault CRM as we work towards full parity with Veeva CRM.
Features
Call Planning
To streamline call planning and scheduling for recurring calls, users can save sets of calls as a call cycle, then apply the call cycle to create all their upcoming calls for the day or the week at once.
Users create call cycles in My Schedule, then apply the call cycles by week or by day. To better identify cycles when selecting them from the call cycle list, users can add a label to each day within a call cycle week. After creating a call cycle, users can edit or delete entries to reflect changes in their call patterns.
When users create calls in My Schedule, the following default values are automatically set on the new call report:
- Default duration, based on the default value for the duration__v field on the call2__v object
- Default address, based on the TSF address or the primary address for the account
- If an address is not available for the account on the call, or the default_call_address_none__v Veeva Setting is enabled, a default address is not selected
- If Call Address Dependency is enabled, the default address is controlled by the default location. Both the default address and location are selected on the new call report according to Call Address Dependency logic.
- Default territory, based on the territories assigned to the user and the selected account
- Default location, if Selecting the Call Location is enabled
Call Reporting
Detailing Products on the Call Report
Product detailing provides a way for users to select which products and detail topics are discussed in a call. This enables users to record key information about their activities during a call. When a user has access to detail groups and detail topics, the product detailing section organizes products and topics by detail group. Products without a detail group display first, under the Common heading.
Product detailing is currently available for users who do not have product favorites enabled. Users must not have access to the favorites__v field on the my_setup_product__v object.
By using the allowed products feature, customers can ensure that planned calls created through data load comply with restrictions on product detailing. If planned calls for users are created through an automated process, the allowed products feature restricts the products that a user can detail on a call to only those allowed for the particular call or territory. This is useful because call and product restrictions do not apply when call records are created through data load.
Restricting Products by Account
Product detailing can be restricted by account. This helps ensure users comply with regulations or organization policies concerning product detailing. For example, by United States regulations, users are not supposed to detail a specific product to HCPs who do not have DEA licenses. Users cannot add the restricted product to the product detailing section on call reports for the specified accounts.
Capturing Product Discussions on the Call Report
Product discussions enable the user to further classify what types of discussions or indications were covered with respect to each product detailed in a call. While product detailing enables users to capture which products were detailed in a call, it does not allow any additional information about product discussions during the call. The product discussions section fulfills this need by enabling users to capture additional information on general comments, discussion topics, and product indications.
Filtering Picklist Values Based on Product Discussions
For efficiency in call reporting, picklist values can be filtered based on the products users select on the call report. When the user selects a product for detailing or discussion, the product__v field is set to the selected product. The value of the product_map__v field is then automatically set to the same value as the product__v field, and all dependent picklists display values based on the selected product.
Capturing Expenses on the Call Report
For easy expense tracking, users can record expenses incurred during a call on the call report. This enables users to record all expenses associated with a specific interaction on the call report, along with other information about the call.
Supporting Detail Groups for Key Messages
For users who detail products that have different indications or are prescribed for different species, featuring the detail group helps distinguish between Key Messages for each application of the product. When detail groups are associated with Key Messages, the Key Messages are grouped according detail group.
In the 23R3.5 release, users must be granted at least Read field permission to the detail_group_v fields on the key_message__v and call2_key_message__v objects, regardless of whether detail groups are enabled for key messages.
Increasing the Character Limit for Key Message Names
To allow for longer Key Message names and match conventions for name fields in Vault CRM, the character limit for the key_message_name_v field on the call2_key_message__v object is increased to 128 characters.
Supporting Layout Profiles for Call Reporting
To enable differing call report layouts based on the user's profile, admins can configure layout profiles for the call report. Layout profiles are used to control the object layouts users see when viewing an object record detail page, enabling users to view different layouts depending on their assigned profile.
Multichannel
To simplify configuration, dedicated admin tabs are available for CRM Vault Metadata Sync, CLM Admin, Approved Email Administration, and Veeva Process Scheduler.
Territory Management
Territory Assignment Rule Updates
Territory Managers can create more robust Territory Assignment Rules using additional operators and account-based criteria.
