Automated visit validations at scheduling and launch
Key Takeaway
Scheduling validations follow one pattern: set the value in the Admin Console, then activate the matching trigger handler. For example, to block double-booking, set "Visit Conflict Validation Period in Days" and "Visit Conflict Validation Mode", then activate the VisitConflictValidationHandler.
Automated visit validations are checks that an admin configures to warn or stop a field rep when a visit breaks a business or regulatory rule. Some checks run while the rep schedules visits. Others run while the rep executes and closes the visit. Most are turned on in the Life Sciences Commercial Admin Console (Admin Console for short), often by pairing a setting with a trigger handler.
Two checkpoints
Validations run at two checkpoints. The first is scheduling, while the rep schedules visits on the Field Calendar. Admin-controlled guardrails there can warn about or block a visit that overlaps time off, falls on a holiday, breaks frequency rules, or is booked too far ahead. Double-booking is another scheduling check: a visit that falls within a defined window of another visit to the same healthcare professional (HCP).
The second checkpoint is visit execution, when the rep creates, runs, and closes the visit. Checks there cover licenses, product restrictions, sample limits, sample inventory, configured frequency rules, and territory guardrails such as territory allocations.
Group visits validate each HCP individually, so one ineligible attendee is caught even when the rest of the group passes. A single visit can't include more than one healthcare organization.