Product Enhancements

eSignature Details Based on the Signature Captured for Each Request

#ID 1688814

The eSignature Details section on the Request Information page of a FOIAXpress request now reflects whether a signature was actually captured when that request was submitted from the Public Access Link (PAL), rather than the current eSignature configuration of its request type. Signature evidence is therefore never lost or hidden when eSignature settings change later, and staff can always see why a signature is or is not present on a request.

The section is displayed or hidden as follows:

• Signature captured: The section shows the full signature details, including the signature type, signer name, username, signature date and time with time zone, IP address, and the statement signed. These details are shown regardless of the current eSignature configuration of the request type.

• No signature captured, request type currently Disabled or not configured: The section is hidden for the request.

• No signature captured, request type currently Enabled: The section is displayed with a message stating that a signature does not apply, as eSignature was not configured for the request type when the request was submitted, or the request did not originate from PAL.

A captured signature record is never removed, hidden, or altered by later configuration changes. Requests that were signed while their request type was Enabled continue to display the original signature details after the request type is set to Disabled, removed from the eSignature configuration, or after the eSignature Module is turned off and on again. Editing a signature statement also leaves the statement on previously signed requests unchanged.

To view the signature details of a request:

1. Search for the request and select it from the search results.

2. On the Request Information page, navigate to the eSignature Details section.

3. Review the captured signature details, or the message explaining that a signature does not apply.

Bug Fix

We’ve addressed the following bug in this version of FOIAXpress: