Jadu Forms Production Readiness Checklist

This checklist should be completed prior to submitting a request to have your form moved to production. It is intended to guide you through the list of items on your form that will be checked and will help prevent a delay in moving your form to production.

Details tab

 

Categories

Verify there is only 1 category selected for your form

Required

Metadata

Make sure there is a meaningful Description.

  • Ex: "The Tuition Refund Appeal is for students who wish to appeal tuition and related fees for a particular term (in part or whole) due to extenuating circumstances."

Required

Registered Users Only

If you are using digital signatures or Integrated Components, your form must have Registered users only enabled.

Required

Enable ReCAPTCHA

If you aren't using Registered users only, then you need to have reCAPTCHA enabled. (This is to ensure the form submitter is a human)

Required

Pages tab

 

Form Structure

 

Number of fields

It is recommended to limit the number of fields on a page for end user experience. We've found that 6-8 per page is optimal, but this can vary.

  • Makes it easier for end users to read
  • Form data saves every time the user moves to the next page

Suggested

Integrated Component Inputs

Check that there are no red triangles next to your pages. If there are, this means one or more of your Integrated Component inputs is not set.
Integrated Component Inputs - Red Triangle

.

Required

Pages Templates

 

Page Template Names

All page template names must include the Category as the prefix.

  • Ex: T-OIT - Requester Information

Required

Fields / Elements

 

Repeatable Questions

Check to make sure that the fields you want displayed in the table have the Show in Details table flag selected

Suggested

File Upload

Ensure max number of files is set. You are limited to 5 attachments per form - this can be split across multiple file upload fields if necessary.

Required

Make sure to add help text or visible text that indicates the maximum number of files that can be attached to the form (up to 5) and the maximum file size accepted (up to 5MB per file).

  • Example:

file upload - help text example

Required

Matrix / Repeatable Questions

Make sure the table is viewable on a mobile device

Suggested

Text Block

If you write your text block in HTML, verify accessibility to meet UofM standards.

Suggested

Event Booking

Do not use this element (not in use at the UofM).

Required

Location

Do not use this element (not in use at the UofM).

Required

Publish tab

Health Check

Check for any health check warnings in the top right side of the page
health check warnings

Required

Live

Set this to TRUE

  • This allows you to test your form.

Required

Visible

Set this to FALSE.

  • This is to prevent the form from appearing in search engine results which we do not currently support.

Required

Internal Only

Set this to FALSE.

  • We do not currently support this functionality

Required

Embeddable

Set this to FALSE.

  • We do not currently support this functionality

Required

Advanced tab

Logic

Make sure the Internal Only flag is set to false for all logic definitions

  • We do not currently support this functionality

Required

Rules tab

Order of Actions

If you are attaching a PDF to an email or submitting to Perceptive Content, then you need to add a Create PDF action as the first action in the rule.

Required

Order of Actions

If your actions need to run in a certain order, they need to be in the same rule.

Suggested

Templates tab

Unused Templates

Remove all templates that are not being used in a Rule.

Required

Template Names

Make sure the template has as meaningful name.

  • Example: "Send Email to Requester"

Required

Email Templates

Make sure to include the Form-Reference Number (Standard) placeholder somewhere in the email body or subject.

  • This is a key identifier that is needed by 1-HELP and the Jadu support team for troubleshooting

Required

If you write your email body in HTML, verify accessibility to meet UofM standards.

Suggested

Show content on completion

If you write your content in HTML, verify accessibility to meet UofM standards.

Suggested

File Export

Make sure the Connector title includes a prefix of your Category (ex: T-OIT)

Required

Perceptive Submit Data

Make sure fields are being truncated using the UMN - Perceptive Index - Trim Value logic if the field has the potential for having more than 39 characters

Required

Make sure you are passing through a Literal Logic that combines your Category and the Form-Reference Number (ex: T-OIT-12345)

Required

Event Booking

Do not use this template type (not in use at the UofM).

Required

Jadu CXM

Do not use this template type (not in use at the UofM).

Required

Jadu Directories

Do not use this template type (not in use at the UofM).

Required

Testing

Note: OIT is not responsible for testing the form functionality or data accuracy. Complete and thorough form testing is the responsibility of the business unit.

Form Behavior

Required fields

Are all required fields working as expected?

Integrated Components

Test all use cases for Integrated Components.

Prefills and Logic

Verify form logic is working properly and fields are prefilled as expected.

Field Validation

If using a validation on a field, make sure it works as expected.

Form Branching

Make sure to test all paths that a form can branch to.

Submission Actions

Emails

Are emails being sent to the correct person, and is the data from placeholders and variables coming through as expected?

PDF Generation

Are all fields mapping correctly and populating the PDF correctly?

Perceptive Content

Verify documents are being sent to Perceptive with the correct index values and the right workflow queue.

Verify attachments are being sent (if applicable)

Submission Logs

Check submission logs for any errors