Require Signature

Use application logic to require applicants to complete a Signature widget before they submit a Slate-hosted application. This approach uses the Signature widget Export Key and a Form Field Value export in a submission requirement.

If no signature value exists for the applicant's form response, the hard fail blocks submission and shows the applicant-facing warning text that you configure.

For background on the widget, see Signature Form Field Widget. For more information about hard fails and soft fails, see Introduction to Application Submission Requirements.

📝 Note

Create and test the submission requirement while it is inactive. Activate the hard fail only after you confirm that applicants with a completed signature can submit and applicants without a completed signature are blocked.

Adding an export key to the Signature widget

Application logic references the Signature widget by its export key. Add the export key before you build the submission requirement.

1. Go to Forms.

2. Open the Slate-hosted application page form that contains the Signature widget.

3. Select Edit Form.

4. Open the Signature widget settings.

5. Enter a computer-friendly value in the Export Key field. Use a value that clearly identifies the signature field, such as signature or certify_signature.

   

6. Select Save.

Creating the submission requirement

Create an inactive submission requirement in application logic. The hard fail controls whether the applicant can submit the application.

1. Go to Database → Application Logic.

2. Select Insert.

3. Configure the following settings:

   • Status: Inactive

   • Type: Submission Requirement

   • Section: Select the form or application page that contains the Signature widget.

   • Name: Enter the applicant-facing message that should appear when the signature is missing.

   • Warning: Hard Fail

   • Base: Configurable Joins - Application

   

Adding the signature filter

Add a subquery filter that looks for a submitted form field value with the Signature widget export key. The hard fail applies when that value does not exist.

1. In the hard fail, select Subquery Filter.

2. Enter a descriptive name, such as Not Exists - Signature.

3. Set Aggregate to Not Exists.

4. Add the Form Responses join.

5. For Type, select All forms and events.

6. Add the Form Field Value export.

7. Edit the Form Field Value export and enter the Signature widget export key in the Form Field Export Key field.

   

8. Select Save.

Testing the requirement

After you add the filter, save the hard fail and test both possible outcomes.

1. Select Save on the hard fail.

   

2. Open a test application that has not completed the Signature widget.

3. Attempt to submit the application and confirm that the hard fail appears.

4. Complete the Signature widget and submit the application again.

   

5. Confirm that the application can be submitted after the signature is complete.

6. Repeat the test with any relevant application populations, rounds, or page conditions.

⭐ Best practice

Test with records that should pass and records that should fail. This confirms that the hard fail requires the signature without blocking applicants who completed the Signature widget.

Activating the hard fail

After testing is complete, return to the application logic record, set Status to Active, and select Save.