User Tools

Site Tools


Guide Section: An EASAP GUI

ESIGNER is a GUI object with:

  • login and password fields
  • a 'Select Status' dropdown list
  • a 'Sign EASAP' button

In an eSignature EASAP:

  1. an 'approver' certifies the EASAP or case record state at the 'current stage' by clicking 'Sign EASAP' button
    • the first eSignature generates a hash code derived from the current EASAP or case record state and writes it to the database
    • each later eSignature retrieves the hash code and certifies none of the EASAP or case record data has changed
  2. the EASAP or case record transitions to a 'next stage' selected from the 'Select Status' dropdown menu
  3. the ESIGNER (eg. %esigner1%) takes the name of the new 'stage'

ESIGNER has at least one child STAGE OPTIONS which will define the requirements for each 'approval' for an ESIGNER EASAP.

ESIGNER VIEWER provides a table showing the status and history of an ESIGNER.

Essential Parameters:
Stages:            List of names, in any order, for each 'stage' of 'approval' of EASAP or case record data
For example 'new', 'submitted', 'accepted','rejected' 'published', 'closed', 'reopened'
A stage name must be added here before approval conditions are set for it in a child STAGE OPTIONS
An ESIGNER object (eg. %esigner1%) will have the value of one of these strings at any moment in time
The default stage START may be renamed or removed
Start Stage: Initial starting stage (default: START )
A transition from this stage generates a hash code which is then stored in the database.
Every subsequent, successful stage transition retrieves and compares this code to the current hash value to certify that EASAP data has not changed.
Optional Parameters:
Show if:Display this object when this logical expression evaluates to true.
Require Submit:Require an EASAP run be 'EASA Submitted' (MENU ACTION > Action: Submit) and completed before ESIGNER is active.
(default: false, meaning EASAP will automatically be submitted upon first 'Sign EASAP' request)
Lock at Stage:Disable any further signatures once this stage is reached.
Beyond merely validating the integrity of EASAP or case data, this parameter allows a validated data set to be input into another process (often another tab in an EASAP) while providing validation of its integrity by displaying all prior signatures in the ESIGNER VIEWER.
Result:Enter a name for a new SCALAR to store the status string returned when an User attempts to 'esign' an EASAP.
Is Locked:Enter a name for a new SCALAR.
This SCALAR will be true if the ESIGNER is locked, and false otherwise.
An Author may set this SCALAR to true which will 'lock' the ESIGNER.

Below we have added eSignature functionality to the Cantilever Plate example EASAP.

An ESIGNER GUI object creates a horizontal region with 'Username', 'Password', 'Select Status' fields and a 'Sign EASAP' button.

To add an ESIGNER and an ESIGNER VIEWER to the Mortgage Calculator example EASAP follow these instructions.

Lock ESIGNER button

Disable any subsequent signing of the EASAP. This allows editing a signed EASAP while retaining the signature history being shown.

In general, Lock on Stage: will be a terminal stage where the EASAP data with signatures is passed to further processing after completing the sequence of necessary stages of data processing and data integrity validation.

The signatures in ESIGNER VIEWER are the visible record of this completed sequence.

ESIGNER with an Excel Client case data

Data from an Excel Desktop Client or EDC session may be 'authorized as valid' with an electronic signature in the EASAP GUI.

In this case any ESIGNER and ESIGNER VIEWER objects will each need a REFRESH OBJECTS ACTION triggered by a VALUE CHANGED with Objects: case_viewer1 (for example). If a named range cell or the spreadsheet file is changed and the User clicks EASA Ribbon > Save, the CASE VIEWER will update and changes will be propagated to ESIGNER and ESIGNER VIEWER.

If no named range cell (or the spreadsheet file) is modified in an Excel Client but the User clicks EASA Ribbon > Save the case record will be updated but the ESIGNER will not generate a new signature in order to save computational time as generating an electronic signature is computationally expensive.

The reference implementation below allows a mortgage calculation to be created/modified/saved as an EDC case then eSigned: