How to configure an eSignature sequence in NuGenesis SDMS that requires unique signatures at each signature reason - WKB51349

OBJECTIVE or GOAL

Configure an eSignature sequence in SDMS that requires unique signers at each level of the sequence. For example, a user who signs the report with "Completed" as the reason cannot sign "Approved" on the same report.

ENVIRONMENT

• NuGenesis 9 SDMS
• NuGenesis 8 SDMS
• eSignature reason codes are defined in the SDMS projects
• All users in a project have privileges to use all of the signature codes in the sequence

PROCEDURE

1. This modification cannot be accomplished solely through the "eSignature Sequence Builder" in SDMS Administrator. First build the basic sequence through the builder, and then save it to the NuGenesis database.
2. Select the Scripts tab in the project properties window.
3. Select the eSig Sequencing script and click Edit.
4. Make the necessary changes to the Visual Basic script and save it.

ADDITIONAL INFORMATION

Given that each eSignature sequence is custom, it is not possible to provide an "off the shelf" script to customers.

Some knowledge of Visual Basic programming is expected in order to edit the script.

The knowledge necessary to edit a script is beyond the scope of a Knowledge Base article. If you want to have a custom eSignature sequence, contact Waters Professional Services for assistance.

Custom sequences of this nature are required generally in the cases where there is more complex logic than that allowed by the eSig Sequence Builder. The most common case is where users have access to all of the reason codes for a project and are expected to sign, for example, "Completed" on some reports and "Approved" on others. For a given report, one user is not allowed to sign "Completed" and "Approved". In this case, the custom sequence would be necessary. If the Approval action is assigned to a separate group of users, this sequence would not be necessary.