Using Product-Specific Monitoring Rules
- Browser
To reduce false-positive violations, compliance users can designate monitoring rules to only run against a defined combination of products, detail groups, and detail topics based on My Setup assignments. This also enables greater control over which rules run for a user's calls, as some monitored phrases may be appropriate for some users and not others.
Product-Specific Monitoring Rules link monitoring rules to any user assigned that product via My Setup. When a rule is linked to the user, the rule runs on all of the user's calls, not only the calls discussing the associated product.
For example, a compliance user at Verteo BioPharma creates the following product-specific monitoring rules:
- The phrase “RA” should not be mentioned when referring to Cholecap
- The phrase “A1C” should not be mentioned when referring to Labrinone
Sarah Jones is a user assigned in My Setup to Cholecap, but not Labrinone. She speaks with Dr. Ackerman about Cholecap and records the following in her post-call notes:
Explained that Cholecap can help lower A1C levels in diabetes patients and is a potentially promising treatment for RA.
When the post-call notes are processed by Approved Notes, only the Cholecap monitoring rule is applied to Sarah’s note, since she is assigned to Cholecap and not Labrinone. When the compliance user reviews violations, only RA displays as a violation on Sarah’s note, and not A1C.
Considerations
- This functionality can be combined with Creating Country-Specific Approved Notes Rules for even greater levels of specificity
- The Product_vod and Detail_Group_vod fields on the Monitored_Text_vod are available in the CSV download file of the Job History Table as long as the user has at least FLS read permission to the fields. These fields do not display if a user downloads the CSV file without FLS read access to the fields.
Prerequisites
Configuring Product-Specific Monitoring Rules
To configure this feature:
-
Grant admins and integration users the following permissions:
Object
OLS
Record Types
Fields
FLS
Monitored_Text_vod
CRU
n/a
- Product_vod
- Detail_Group_vod
FLS permission to this field is required even if Detail Groups aren’t used.
Edit
Monitoring_Rule_vod
CRU
n/a
- Product_vod
- Detail_Group_vod
Edit
My_Setup_Products_vod
R
n/a
Product_vod
Read
Product_vod
R
n/a
Product_Type_vod
Read
Product_Group_vod
R
n/a
- Product_vod
- Product_Catalog_vod
Read
-
Grant compliance users the following permissions:
Object
OLS
Record Types
Fields
FLS
Monitored_Text_vod
CRUD
n/a
- Product_vod
- Detail_Group_vod
FLS permission to this field is required even if Detail Groups aren’t used.
Read
Monitoring_Rule_vod
CRUD
n/a
- Product_vod
- Detail_Group_vod
Read
-
Place the following fields on the appropriate Monitoring_Rule_vod and Monitored_Text_vod object page layouts and Lightning Record Pages:
- Product_vod
- Detail_Group_vod
Creating Product-Specific Monitoring Rules
To create a product-specific monitoring rule:
- Edit the appropriate Monitoring_Rule_vod record or create a new one.
-
Populate the appropriate fields:
- Product_vod – Enables users to select the appropriate product or detail topic
- Detail_Group_vod – Enables users to select the appropriate detail group
These two fields can be used independently or used together for further specificity.
- Select Save.