Bookshelf Home | Contents | Index | PDF     

Siebel Pharma Handheld Guide > Siebel Handheld Application Administration > Process of Administering Siebel Pharma Handheld Applications >

Validation Logic of the Sign and Submit Buttons in Siebel Pharma Handheld Applications

You can edit the validation logic for the Signature and Submit buttons for professional and account calls.

Default Validation Logic Flowcharts

The default validation logic for the Signature and Submit buttons is shown in the following figures: Figure 4, Figure 5, and Figure 6. Not all implementations of Siebel Pharma Handheld require the extensive validation as shown in these figures. Before most validation steps, the procedure consults a user property to determine if the field must be used during the validation. For example, if it is not necessary to validate the License Number field, the user property Validate License Number is set to false. The Signature button validation then skips the validation question: Is the License Number field populated?

User Properties for altering validation logic are described in About Changing Validation Logic by Editing User Properties.

Figure 4 shows the default validation logic for the Signature button.

Figure 4. Default Validation Logic Flowchart for Signature Button

NOTE:  The numbers in Figure 4 correspond to the numbers of the user properties described in Table 21.

Figure 5 shows the default validation logic for the Professional Call Submit button.

Figure 5. Default Validation Logic Flowchart for Professional Call Submit Button

NOTE:  The numbers in Figure 5 correspond to the numbers of the user properties described in Table 21.

Figure 6 shows the default validation logic for the Account Call Submit button.

Figure 6. Default Validation Logic Flowchart for Account Call Submit Button

NOTE:  The numbers in Figure 6 correspond to the numbers of the user properties described in Table 21.

About Changing Validation Logic by Editing User Properties

Validation logic uses user properties to determine whether a field must be used during validation.

Table 21 explains the user properties that you can use to alter the validation logic of the Sign, Professional Call Submit, and Account Call Submit buttons.

Table 21. User Properties for Setting Sign and Submit Button Logic
Flowchart Reference
User Property
Action if Y...
Action if N...
Default Value

1

Validate OK to Sample

Use to enforce confirmation that the OK to Sample flag is selected before launching the Signature Capture display.

Enforce the OK to Sample validation.

Skip the OK to Sample validation.

Y

2

Validate License Number

Use to enforce validation that the License # is populated before launching the Signature Capture display.

Enforce the License Number validation.

Skip the License Number validation.

Y

3

Validate License Number Status

Use to enforce validation that the License # status = Active before launching the Signature Capture display.

Enforce the License Number Status validation.

Skip the License Number Status validation.

N

4

Validate License Number Expiration

Use to enforce validation that the Expiration date on the License # is later than Today before launching the Signature Capture display.

Enforce the License Number Expiration validation.

Skip the License Number Expiration validation.

N

Not applicable

Validate Address DEA Number

Use to enforce that the DEA number is valid (DEA # checksum algorithm) at the time the value is entered into the DEA # field on the Address child applet (on the Handheld application).

This user property applies to both the laptop and the Handheld applications.

NOTE:  DEA stands for Drug Enforcement Administration.

Enforce the Address DEA Number validation (field is populated and number is valid).

Skip the Address DEA Number validation (field is populated and number is valid).

Y

6

Validate Signature DEA Number

Use to enforce that the DEA number is populated and that the value is valid (DEA # checksum algorithm) before launching the Signature Capture display.

Enforce the DEA Number validation in the Signature button (field is populated and number is valid).

Skip the DEA Number validation in the Signature button (DEA number is valid for each checksum routing and the field is populated).

Y

7

Validate DEA Number Expiration

Use to enforce validation that the Expiration date on the DEA is later than Today before launching the Signature Capture display.

Enforce the DEA Number Expiration validation in the Signature button (expiration date is later than today).

Skip the DEA Number Expiration validation in the Signature button (expiration date is later than today).

N

8

Validate Professional Profile

Use to validate if the professional's Last Name, First Name, Title, and Address fields are populated before launching the Signature Capture display.

Enforce the Professional Profile validation.

Skip the Professional Profile validation.

Y

9

Validate Sign Lot Number

Use to validate if the lot number is populated on launching the Signature Capture display.

Enforce the Signature button Lot Number validation.

Skip the Signature button Lot Number validation.

N

10

Validate Submit Lot Number

Use to validate if the lot number is populated on submitting a call.

Enforce the Submit button Lot Number validation.

Skip the Submit button Lot Number validation.

Y

11

Sample Disbursed Required

Use to require that at least one sample be disbursed before submitting the call.

Enforce that at least one sample be disbursed.

Do not require at least one sample disbursed.

N

12

Must Detail Products

Use to require that at least one product be detailed before submitting the call.

Enforce that at least one product be detailed.

Do not require at least one product detailed.

N

13

Paper Reference Number Required

Use to require a sample reference number for calls with paper signatures.

Enforce the Paper Reference Number required validation.

Skip the Paper Reference Number required validation.

Y

14

SRE Reference Number Required"

Use to require a sample reference number for signature recorded electronically (SRE) calls.

Enforce the SRE Reference Number required validation.

Skip the SRE Reference Number required validation. (If the Ref # field is blank, it will be populated with the Row ID of the call.)

N

15

SRE Professional Type

Use to require that the professional type be valid for signature recorded electronically (SRE) calls.

The professional type (for example, Physician) must match the value of this user property.

If the value is null, all professional types are valid.

null

Not applicable

Submit Confirmation

Note: If this user property does not exist (for example, in the standard Siebel Pharma application), behavior is equivalent to Submit Confirmation = Y.

Confirmation message appears when the Submit button is tapped.

No confirmation message appears when Submit button is tapped.

Y

Not applicable

Submit On Sign OK

Note: If this user property does not exist (for example, in the standard Siebel Pharma application), behavior is equivalent to Submit On Sign OK = N.

Tapping the OK button on the Siebel Signature Capture display for new professional calls invokes the submit method. The submit method is not invoked for account calls nor for re-created professional calls.

Tapping the OK button on the Siebel Signature Capture display closes the display. To submit the call, tap the Submit button.

N
    
Siebel Pharma Handheld Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.