Verify a CoSignature

Overview

Starting with TIER WFS 8.3.7, you can use the VerifyCoSignature() button action so someone can cosign a document without having to be logged in to TIER.

Details

The VerifyCoSignature() button action is similar to VerifySignature(), except VerifyCoSignature() additionally prompts for the cosigner's login name and password and adds the cosigner's User ID to a given edit control if the supplied login name and the password match. Otherwise, it changes the edit control to 0 (zero).

Example

When the user clicks the Cosign button, they are prompted to enter their login name and then their signature password. When the login is successful, the system will capture the UserID in a TIEREdit. (Normally this TIEREdit would be on the Invisibles tab.)

Steps

1. On the design for the form, create a button named Cosign.
2. Create a TIEREdit to hold the User’s Login ID.
3. Next, create two buttons, each with its own action for signature success and signature failure.
   The Cosign button will have one of the following multi-commands on it:

VerifyCoSignature(BtnValidSign, BtnInvalidSign, EdtCoSignUserID)

OR

VerifyCoSignature(BtnValidSign, Null, EdtCoSignUserID)

When the supplied login name and the cosigner's password match, the system takes the op__id of the login name that is entered and writes it into the edit control (EdtCoSignUserID) and clicks the first button (BtnValidSign). The second button is optional, but if provided it is clicked when the signature does not match (BtnInvalidSign). Otherwise (if the second button is null), it provides a standard error message about the password mismatch.

The idea of the command clicking the given buttons is to allow the form designer to design additional functionality through those buttons. As an example, the cosigner's User ID can be picked up with :EdtCoSignUserID for passing it to a stored procedure.