Bookshelf v8.0: About Validation Rules

The Offline Client for Life Sciences provides a set of prebuilt validation rules for sample drops and signature capture in the Sales application and Message Plans in the Asset Message Planner application.

You can extend and reuse these rules, as required. The prebuilt validation rules are defined in the LSValidation.as script located, for example, in the following directory:

Table 4 provides a list of prebuilt validation rules available in the Offline Client for Life Sciences. All rules in this table return status and data values.

Table 4. Prebuilt Validation Rules
Validation Rule	Function	Application Used in	Related UI Operation
ActivityLicenseValidation	Validates if the activity has a valid license number.	Sales	This rule is started by the Sign button on the overlay menu on the Detailer page.
AreSamplesDroppedValid	Verifies that the quantity of samples dropped is greater than zero (0).	Sales	This rule is started by one of the following: Get Signature button. Save button in signature capture overlay.
IsOkToSample	Verifies if the primary contact associated with the activity can receive samples.	Sales	This rule is started by one of the following: Show Sign button in overlay of Detailer Page. Swap Signee button. Get Signature button.
IsQtySampleValid	Verifies that the quantity of the dropped sample is less than or equal to the maximum quantity allowed for the call. It also verifies that the quantity is less than or equal to MaxQtyPerAllocation for the sales representative allocation for the product.	Sales	This rule is started by one of the following: Get Signature button. Save button on signature capture overlay. Edit record in Sample Drop list applet.
IsStopSampling	Verifies that the Stop Sampling flag on the Sample Allocation for the product associated with the Sample Dropped Record is not set.	Sales	This rule is started by one of the following: Submit Call button. Get Signature button. Swap Signee button.
IsValidPositionToSubmit	Verifies that the owner of the call is the current user.	Sales	This rule is started by the Submit button in the Contact Call page.
IsValidCallDate	Verifies that the value for the call date of the activity is today.	Sales	This rule is started by one of the following: Get Signature button. Show Sign in overlay menu of Detailer page. Submit button in Contact Call.
StateLicenseValidation	This rule does the following: Validates if the activity has a valid license number. Verifies that the Contact field has a license number record for the contact address used with the current activity. The primary contact must have at least one license having the same state name as the PrimaryStateProvince field. Verifies that a contact's license number exists and that the field is not null. Verifies that the expiry date of a contact's license number's has not expired. Verifies that the status of the contact license is Active.	Sales	This rule is started by one of the following: Swap Signee button. Get Signature button.
ValidateDiscMandatoryFlag	This rule is used when a messaging plan status is set to Approved. This rule checks if the DisclosureMandatory value is set to Y. If so, the rule then checks if the child messaging plan items and disclosure messaging plan items exist.	Asset Message Planner	This rule is started when the status is changed to Approved when editing a message plan.
ValidateReqFields	Verifies that the required fields for the contact (First Name, Last Name) are present.	Sales	This rule is started by one of the following: Show Sign button in overlay menu of Detailer page. Swap Signee button. Submit button in Contact Call. Get Signature button

Configuration Guide for Siebel Offline Client for Life Sciences		Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.