Requiring Medical Inquiry Signatures
Who can use this feature?
- Browser, iPad, iPhone, Windows Users
- Users do not require an additional license
- Business Admin Users, End Users
Configuring Required Signatures
Business Admin Users
To configure this feature:
- Ensure Configuring Medical Inquiries is complete.
- Add the signature_date__v field to the appropriate medical_inquiry__v layout.
- Navigate to Business Admin > Objects > Veeva Settings and edit the Global Veeva Settings record.
- Select the DISABLE_MI_SIGN_BUTTON check box Veeva Setting to prevent users from clearing a signature and changing the medical inquiry details after an initial signature is captured. This step is optional.
Using Required Signatures
End Users
If the signature_date__v field is on the medical_inquiry__v layout, the Signature Date field displays when an end user creates or edits a medical inquiry. Once the end user enters the current date and time, these values are stamped on the signature_date__v field. The delivery_method__v, delivery details, account__v, and inquiry_text__v field values are locked on the record. If multiple product inquiries are configured, the product__v field is also locked.
If the signature_date__v field is on the medical_inquiry__v layout, the Sign action displays when an end user creates or edits a medical inquiry. Once the end user accepts the signature, the signature is stored in a Base64 encoded string in the signature__v field. The current date and time are stamped on the signature_date__v field. The delivery_method__v, delivery details, account__v, and inquiry_text__v field values are locked on the record. If multiple product inquiries are configured, the product__v field is also locked.
The Sign button does not display on the medical inquiry after a signature has been accepted if the DISABLE_MI_SIGN_BUTTON__v Veeva Setting is selected, preventing users from clearing a signature and changing the medical inquiry details after an initial signature is captured. Users cannot delete signed records.
If the signature_date__v field is on the medical_inquiry__v layout, the Sign action displays when an end user creates or edits a medical inquiry. Once the end user accepts the signature, the signature is stored in a Base64 encoded string in the signature__v field. The current date and time are stamped on the signature_date__v field. The delivery_method__v, delivery details, account__v, and inquiry_text__v field values are locked on the record. If multiple product inquiries are configured, the product__v field is also locked.
The Sign button does not display on the medical inquiry after a signature has been accepted if the DISABLE_MI_SIGN_BUTTON__v Veeva Setting is selected, preventing users from clearing a signature and changing the medical inquiry details after an initial signature is captured. Users cannot delete signed records.
If the signature_date__v field is on the medical_inquiry__v layout, the Sign action displays when an end user creates or edits a medical inquiry. Once the end user accepts the signature, the signature is stored in a Base64 encoded string in the signature__v field. The current date and time are stamped on the signature_date__v field. The delivery_method__v, delivery details, account__v, and inquiry_text__v field values are locked on the record. If multiple product inquiries are configured, the product__v field is also locked.
The Sign button does not display on the medical inquiry after a signature has been accepted if the DISABLE_MI_SIGN_BUTTON__v Veeva Setting is selected, preventing users from clearing a signature and changing the medical inquiry details after an initial signature is captured. Users cannot delete signed records.
