To configure this feature:

1. Navigate to Business Admin > Objects > Veeva Settings.
2. Select the appropriate veeva_settings__v record.
3. Ensure the disable_validation_rules__v Veeva Setting is not selected. When selected, this setting disables validation rules for mobile devices.

To create validation rules for object records, see How to Create Validation Rules for more information.

Supported Objects

Generic data entry is defined as data entry made using the standard edit/save features for an object. For example, editing the in-line TSF control on Account does not trigger validation rules; whereas, editing via the related list does trigger validation rules.

Generic data entry is supported for the following objects:

• Custom objects
• account__v
• account_authorization__v
• account_plan__v
• account_tactic__v
• action_item__v
• address__v
• affiliation__v (not from the Sphere of Influence, only from a related list)
• assessment__v
• benefit_design__v
• benefit_design_line__v
• business_event__v
• business_event_target__v
• call2__v
• call2_detail__v
• call2_discussion__v
• call2_expense__v
• call2_key_message__v
• call2_sample__v
• call_objective__v
• campaign__v
• campaign_target__v
• child_account__v
• clinical_trial__v
• coaching_report__v
• contact__v (standard save, not from the Call Report)
• em_attendee__v
• em_budget__v
• em_business_rule__v
• em_business_rule_configuration__v
• em_catalog__v
• em_event__v
• em_event_history__v
• em_event_material__v
• em_event_override__v
• em_event_session__v
• em_event_session_attendee__v
• em_event_speaker__v
• em_event_team_member__v
• em_expense estimate__v
• em_speaker__v
• em_speaker_cap__v
• em_speaker_nomination__v
• em_speaker_qualification__v
• em_vendor__v
• em_venue__v
• event_attendee__v
• expense_type__v
• formulary_product__v
• inventory_order__v
• inventory_order_line__v
• inventory_order_allocation__v
• key_message__v
• medical_discussion__v
• medical_event__v
• medical_inquiry_fulfillment_response__v (iPad only)
• medical_insight__v
• order__v
• order_line__v
• product__v
• product_group__v
• product_group_map__v
• product_plan__v
• product_strategy__v
• product_tactic__v
• publication__v
• rep_roster__v
• sent_email__v
• speaker_evaluation__c
• territory_budget__v
• territory_budget_transaction__v
• time_off_territory__v
• tsf__v (not from the Territory Fields component, only from a related list)
• unsubscribe__v
• unsubscribe_product__v

Areas of the application which rely on object controls to display data or record data in multiple objects from a single page are supported selectively. Currently support areas:

• Call Reporting
• Account Hierarchy
• Medical Inquiry
• Order Management
• Inventory Management
• Event Attendee Management

Areas not currently supported:

• Acknowledgment of Content
• Account Partner
• My Schedule
• Sphere of Influence
• Product Metrics
• New Account Wizards
• Multichannel Consent
• Multichannel Activity Lines
• Office Best Times
• CLM
• Surveys
• Contracts

Supported Functions, Operators, and System Variables for Validation Rules

Some functions, operators, and system variables cannot be supported due to API and application limitations.

The following functions are supported:

• Abs
• Ceiling
• Floor
• Max
• Min
• Round
• Sqrt
• Value
• And
• BlankValue
• Case
• If
• IsBlank
• IsChanged
• IsNew
• IsNumber
• Not
• Or
• PriorValue
• Date
• Day
• Month
• Today
• Year
• DateTimeValue
• DateValue
• Now
• Begins
• Contains
• Find
• Includes
• Left
• Lower
• Regex
• Right
• Substitute
• Text(date/datetime/number, format)
• Trim
• Upper

The following operators are supported:

• (
• &&
• ||
• Or
• <
• <=
• >
• >=
• =
• !=
• +
• -
• *
• /
• ^
• %
• &
• )

Additionally, the @User system variable is supported. See System Variables for more information.

Every time a validation rule is executed on a mobile device, the following validation rule logging information automatically writes to the user's activity log, enabling easier debugging of validation rules. See Downloading Activity Logs for Troubleshooting for more information about user activity logs. Each line represents a line in the log if the rule is executed as a part of a block of validation rules (i.e. call2__v, medical_inquiry__v):

• VALIDATION_RULE_BLOCK_START | [ObjectType1, ObjectID1], [ObjectTypeN, ObjectIdN],...
• VALIDATION_RULE_EVAL|[PASS/FAIL]
• VALIDATION_RULE_ERROR|[Error Message]
  
• VALIDATION_RULE_BLOCK_END

When end users sync their mobile devices, all active validation rules for all objects the end users have access to are synced. When end users create or update records, the appropriate validation rules run when end users save the records. If fields on the record violate a validation rule, the record is not saved and an error displays for all fields violating the rule.

• Formula fields still evaluate at sync time and are subject to the pre-existing limitations of the Vault CRM app. See Using Autosync for more information.
• Validation rules on mobile devices execute against the data downloaded to the device. If the data needed by a validation rule does not exist or is different from what is expected on the Browser platform, inconsistencies may occur.
• A sync error occurs if data passes a validation rule on the mobile device, but fails the validation rule online
• Nulls are treated as zeros for number fields. Validation rules comparing a numeric field to 0 should also include the ISBLANK() function
• In order to ensure consistent behavior across platforms, use the & text operator when concatenating strings

Additionally, the following should be considered when using validation rules in each of the following areas:

Call Reporting

• Validation rules execute against the call and any in-scope child call data. For example, if a Call Report contains Call Discussion, Call Detail, and Call Sample data, validation rules are executed against each of the child records when saving, signing, or submitting a Call. This means multiple validation errors can occur for the same object.
• Validation rules are executed when selecting Sign from the All Actions menu of a CLM presentation
• If a validation rule is violated, the Call Report displays so the issue can be corrected. The CLM session ends.
• Selecting Done from the All Actions menu of a CLM presentation does not run validation rules
• Selecting Launch Media from a Call Report does not run validation rules
• Validation rules are not executed during implicit save of the Call Report

Medical Inquiries

• Validation rules execute against the medical_inquiry__v header record, as well as any related Medical Inquiry objects created in the transaction (ones created using the Multiple Product Inquiries section attribute)
• Rules execute when saving, signing, or submitting a Medical Inquiry

Medical Events and Event Attendee Management

• Validation rules execute against the medical_event__v header object
• Validation rules are executed when:
• Using the Add My Attendance feature. The rule message displays as an iOS modal.
• Using the Manage Attendees feature. This feature allows the user to add multiple attendees at once. If there are violations when the user selects Add Selected, an error message displays all of the violations. If both violating attendee records and non-violating attendee records are selected, non-violating records are added.
• Using the Add Attendee feature to add attendees one at a time

Order Management

• The Split Order feature does not support validation rules
• Validation rules execute on the order__v record and all related order_line__v records when saving, signing, or submitting an order, as well as selecting Void
• When executing validation rules against order__v and order_line__v, the rules are not evaluated against child Orders

Inventory Monitoring

Validation rules execute against the inventory_monitoring__v record and all related inventory_monitoring_line__v records when saving, signing, or submitting a record.

Data Change Requests

• iPad platform
• Validation rules execute when submitting DCRs for account__v, address__v, and child_account__v records
• Using the Include Optional Fields feature for the New Account and Parent Account Wizards, the user is directed to the expanded edit screen for the Account object during the DCR process. Validation rules execute on only the Account__v record when saving data on this expanded edit screen.
• Validation rules are not supported on the data_change_request__v and data_change_request_line__v objects