using one of the following
options:eSignature, also known as eSigControl enables a user with CanBatchSign role permission to electronically sign a subject from the subject or grid view pages, sign a folder or form and/or all folders or forms requiring signature from the grid view page.
If a form, folder, or subject requires signature, the signature field appears on the form as configured with the configured pre-text. If a user cannot sign, the signature field does not display.
Signing a form signs all data points on the form that Require Signature.
Note: Any changes, with the exception of changing a field's code or translating a field, to a previously signed form will break the signature and will require the changed data point to be re-assigned. The status icon for the data point and form will both reflect the signature change.
Data points on a form can be flagged to Require
Signature using one of the following
options:
Place a signature field eSigPage on the form (configured in the Architect module)
Create an edit check with Check Action of RequireSignaturePage
Set a Form level property requiring signature (configured in the Architect module).
Signing a folder will sign all forms and their data points on the form that require signature.
Note: Any change to any form or data-point, with the exception of changing a field's code or translating a field, within a previously signed folder will break the folder’s signature and will require the folder to be resigned. The folder’s status will reflect these signature changes.
Data points within a folder can be flagged to Require
Signature using one of the following
options:
Place a signature field eSigFolder on a form within the folder (configured in the Architect module)
Note: If a user has permission to batch sign, then the folder can be signed from the Grid View page. If the user does have permission, then the folder can only be signed from the form containing the eSigFolder field.
Create an edit check with Check action of RequireSignatureFolder (configured in the Architect module). When this edit check is set, all forms within the folder may be signed individually or all forms in the folder requiring signature may be signed from the Grid View page.
Signing a subject will sign all folders, forms, and data points for the subject requiring signature.
Note: Any change to any data point under a previously signed Subject will break the signature on the data point in question, thereby breaking the signature on the form the datapoint resides in; the folder, the form resides in; and the subject the folder resides under. The changed data-point must then be re-signed. The Subject status will reflect these signature changes.
Data points for a subject can be set to Require
Signature using one of the following
action:
Place a signature field eSigSubject on a form for a subject (configured in the Architect module)
Note: If a user has permission to batch sign, then the subject can be signed from the Calendar on the subject page. If the user does have permission, then the subject can only be signed from the form containing the eSigSubject field.
Create an edit check with Check Action of RequireSignatureSubject (configured in the Architect module). When this edit check is set, all forms under the subject may be signed individually, or, if the user has permission to batch sign, the subject may be signed from the calendar on the subject page or from the Grid View page.
Note: If your role is configured with the See Sign role action permission, you can see the Require Signature status icon on folders, forms, and data points that are ready to be signed as well as any forms that require signatures listed in the Task Summary. However, you cannot save and sign the forms.
Copyright © 2014 Medidata Solutions, Inc. All rights reserved.