📚 Part of the series Application Building Phase II: The Slate-hosted Application

The Slate-hosted application can collect applicant signatures and require them for submission.

Depending on when your database was provisioned, your application may look different:

• Newer databases come with a signature page that collects signatures as free text, which is then mapped to an application-scoped field called Application Signature. This form page can be customized like any other custom application page.

• Older databases used the standard signature page, identified by the part ID certify. This page has fewer options for customization.

You can replace the default certify page with a custom form page by following these steps:

✅ Five steps required to create a custom signature page

1. Create a Slate-hosted-application-page-scoped form

2. Either use the Signature form field widget, or create a custom field to collect the signature.

3. Create an application requirement for the signature

4. Replace the Certify page in the application base with the form and comment out <part id =”certify”> from the /apply/base.xml.

5. Activate the application logic.

Let’s go through these steps in more detail:

Step 1: Creating the Slate-hosted application page

This form serves as the host for the widgets you'll create later.

1. Go to Forms.

2. Select New Form.

3. Configure the following settings:

   • Page Title: The page title will display to an applicant as the name of the page.

   • Folder: Keep organized by saving application pages within a clear folder structure.

   • Status: Set the status to Confirmed/Active.

4. Select Save.

5. Select Edit Form.

6. Select Edit Properties.

7. Set Scope to Slate-Hosted Application Page.

8. Select Save.

9. Delete all default form fields.

Step 2: Collecting signatures

You can capture the applicant’s signature in one of two ways:

Option 1: Add the Signature widget

Collects cryptographically-secured, timestamped signatures on the person record.

📝 Note

Signatures do not currently map to system fields, and there are instances where signatures collected in the Signature form field widget may not render as expected—for example, in data containers, document export queries, or when exporting to Auto PDF or certain scoped forms in the Reader. If you depend on these methods, consider using option 2 (an application-scoped field).

1. Select Edit Form.

2. From the form palette, select the Signature widget.

3. Configure the widget settings as desired.

4. Select Save.

📖 Learn more about the Signature form field widget

Option 2: Create a custom application-scoped field  

Collects signatures as a free text form field mapped to an application-scoped field.

1. Go to Database → Fields.

2. Select New Field

3. Configure the following settings:

   • Scope category: Records

   • Scope: Application

   • ID: Enter a computer-friendly field ID, for example, custom_signature

   • Name: Enter a name for the field.

   • Folder: Keep fields organized by placing them in folders. To create a new folder, select Other.

   • Field type: Free Text

   • Unique for Merging: Do not use value for merging

4. Select Save.

5. Return to Database → Fields.

6. Select the Force refresh cache link.

7. Go to Forms.

8. Select the form you created in the previous section.

9. Select Edit Form.

10. From the form palette, select Text Box.

11. Configure the following settings:

    • Label: Enter an applicant-facing label for the signature field.

    • System Field: Select Application Fields, then select your custom signature field.

12. Select Save.

Step 3: Creating an application submission requirement

To create the application logic that requires applicants submit their signature:

1. Go to Database → Application Logic.

2. Select Insert.

3. Configure the following settings:

   • Status: Inactive

   • Type: Submission Requirement

   • Section: Select the form you created in Step 1.

   • Name: Enter an applicant-facing name for the submission requirement.

   • Warning: Hard Fail

   • Base: Configurable Joins - Application

4. Select Subquery Filter.

5. Configure the following settings:

   • Status: Active

   • Name: Enter a name, like “Custom signature exists”.

   • Type: Dependent subquery

   • Aggregate: Not Exists

   • Exports: Configure the following settings:

     1. Select Export.

     2. Select either your custom signature field, or Signature, depending which option you chose in Step 2.

     3. Select Save.

        

6. Select Save.

Step 4: Configuring the application base

To add our custom signature page to the application base and remove the default signature page:

1. Go to Database → Application Editor.

2. Select an application base.

3. Select Edit Menu.

4. From the list of application pages, select Signature.

5. Select Delete.

6. Select Add Link.

7. Configure the following settings:

   • Type: Custom Form Page

   • Subtype: Select the form you created in Step 1.

   • Label: Enter an applicant-facing title for the page.

8. Select Save.

📖 The Application Editor

The default certify application page has standard application logic of its own, which we must disable in the application base file:

1. Go to Database → Files.

2. In Search Files…, enter the name of your application base. For example, /apply/.

3. Select the application base file, which ends in base.xml.
   

4. Press cmd/ctrl + F to open the WYSIWYG editor’s search bar.

5. In the search bar, enter <part id="certify">.

   

6. Add a comment around the entire tag to disable it:

   <!-- <part id="certify>
        </part> -->

7. Select Save.

Step 5: Activating the application submission requirement

1. Go to Database → Application Logic.

2. Select the requirement you created in step 3.

3. Set the requirement’s Status to Active.

4. Select Save.