Jenzabar Campus Portal Features Help Hub

FormFlow Forms FAQ and Troubleshooting

Tip

For additional information about resolving common issues, see the FormFlow Forms Troubleshooting Guide.

Yes. When you add a rule to a button or question, you can specify which workflow tracks you want the submission to be associated with.

File uploads behave the same all other Campus Portal file uploads based on your server configuration. For additional information about document security, contact your campus support team.

Since multiple choice fields require multiple rows by design, they cannot be flattened into a single row for the view. They are, however, included in the CSV export available in the View Reports page.

Yes, you can concatenate multiple fields in custom tables by creating a custom stored procedure. If you need assistance, contact our Services team.

Yes, but the process would need to be done with a custom stored procedure. If you need assistance, contact our Services team.

Important

The form types available are dependent on the licenses you have.

The following form types can be submitted to Process Internet Submissions:

  • Personal Information with Gift (Constituent)

  • Admissions Inquiry (New) (Candidate)

  • Admissions Application (New) (Candidate)

  • Student Request (Student)

  • Housing Application (EXi/J1 Web Student Life)

  • Data Privacy Request - Update Consents (Common)

  • Data Privacy Request - Access Data/Forget Data (Common)

Use the View Reports link on the FormFlow - Forms page to see the form's submission status. When the form has a Submitted status, payment was successful. If the status is Payment Pending, payment has not gone through.

There may be a rule that targets questions without a group name. When the rule is executed, it could potentially hide several questions on your form.

When the form moves into a workflow, the context of the literal string replacer query changes if the value of the literal string replacer depends on the user viewing the form. For example, a question with a literal string replacer is populated with the submitters information by default when they are viewing the form. When an approver views the form, the questions that use those same literal string replacers will use the currently logged in user's information to populate the questions rather than the original submitter's information.