Displaying a form

Related videos

After you have created your form and are ready to display it on a page for user access, you would use the Form content item.

Important! Do not add more than one form to a content record. Adding more than one form to a content record is not currently supported.

Using the Forms content item to display the form

Do the following to display the form:

  1. Go to RiSE > Page Builder > Manage content.
  2. Locate an existing content record you want to add the form to, or choose a non-system folder to store the form and select New > Website Content.
  3. Title the content record, then select Add content.

    4. Adding the forms content item

  4. From the Content folder, choose Forms.
    5. Adding the forms content item
  5. Define the Forms content item options:
    • Form – Select the form to be displayed.
    • Default success message – Displays a successful submission message. The default message is Successfully updated. Use this option to override the default message. If you have defined button-specific messages, these messages are appended to theDefault success message.
    • Default failure message – Displays a failed submission message. The default message is Form not saved. Use this option to override the default message. If you have defined button-specific messages, these messages are appended to the Default failure message.
    • Display additional error/success message (at the top of the page) – The standard location for submission-related error and success messages is at the bottom of the page. When enabled, the Display additional error/success message option also displays submission-related error messages at the top of the page.
    • This form creates a new contact account – Enables account creation features on a specific form. New accounts have a status of Active in all cases. To create a valid contact record, a form must require the First Name, Last Name, and Email fields to be filled in by the user. The following options appear:
      • Contact type - Assigns either the Individual or Company role to the new contact account.
      • Customer type – Assigns a specified member type to the new contact account.
      • Billing category – Assigns a specified billing category to the new contact account.
      • For logged in non-staff users, auto-assign new contact to user’s primary org – When creating an associate account, this option ties the associate account directly to the company of the Company Administrator.
      • Duplicate prevention options – Managing duplicates is an important part of ensuring that new accounts are on-boarded correctly.

        Note: These options only apply when the username and password fields are present. See Displaying a form for more information about duplicate checking.

        Use the following options to help manage duplicates:
        • Email – Provides basic validation that a user’s email address does not already exist in iMIS.
        • Query based – Uses a custom query to check for duplicates. Fields marked Use for duplicate check will be used by an IQA query. If the IQA returns a match, the account-creation process is halted.

          Note: Fields on the form marked Use for duplicate check must be added as filters to the IQA query. If a duplicate check field is not added as a filter or a filter does not use a duplicate check field, the query will not return matches for the field.

        • Use custom duplicate found message – Displays when a duplicate is found. It is recommended to suggest a corrective course of action for the form user, such as, “An account already exists with the email you have provided. Please visit our sign-in page.”
        • Allow user to proceed when duplicate is found– Allows users that have been identified as potentially having accounts to continue to sign-up and create an account which will likely be a duplicate. This will not allow a duplicate username to be created if that username is already in iMIS.
    • Lock form to update specific contact – Anonymous forms using Locked to an ID allows you to deploy forms to collect submissions from anonymous users. Form data is stored for the selected contact. For example, a non-member account called Event Evaluations can be set up in iMIS and used to record submissions for a post-event survey. All submissions recorded using that form are recorded as being submitted by the specified ID, regardless of whether the information is received from a logged-in user or anonymously. Using a multi-instance table data source, you can capture detailed submissions from as many individuals as you want and have them grouped together for analysis.

      • Note: Forms that use this feature must reference a multi-instance data source.

      • Contact to update - Select the specific iMIS record that will be updated by this form.

        • Important! When Lock form to update specific contactis enabled, the selected contact should never be a system account, such as Manager, Guest, Administrator, system, or IMISLOG.

  6. Click OK, then Save & Publish the content record.
  7. Add the Form where you want users to have access to it.
  8. To edit the form directly from the page, see Using the Forms content item to edit the form.

Using the Forms content item to edit the form

The Edit source form link is available to all staff users from the Forms content item. This link to opens a limited view of the form designer which supports adding, editing, removing, and rearranging form elements.

To edit forms displayed using the Forms content item, do the following:

  1. Navigate to the page containing the form.
  2. Select Edit source form. The source form opens in a limited view of the form designer.

    3. Editing a source form

  3. Add, edit, remove, and rearrange the form elements as necessary.

    4. Note: To update components of the form not available in this window, edit the form in Form Builder.

  4. Save the changes. Once saved, all pages containing the form reflect the changes.

    5. Saving an example form

Using URL parameters in forms

Forms Builder has native access to the following:

  • Any URL parameters provided to the page - URL parameters such as Year=2021 or NewMember=1 are available to forms. URL parameters can be used to:

    • Select specific records from a multi-instance data source.
    • Set default values on fields where this option is available.
    • Pass values to other pages or forms.

  • On Behalf Of - Using the On Behalf Of feature allows you to display information for a specific individual on forms used as part of your staff site or if you have appropriate permissions.
  • Form field values - Whenever an action button is invoked, all of the current field values saved on the form are available as parameters to be passed onwards.

    • Example 1

    A special invitation is sent out to encourage individuals to sign up for an event. The URL contains the parameter ?EventKey=2021Conference. After the individual uses a form to answer some qualifying questions, the individual can be sent to the event registration page by passing this parameter. The details the individual provided on their form submission will allow a discount to be calculated.

    Example 2

    A staff-facing page is created to review submissions. The parameter ?ID=48484 retrieves the record for 48484 automatically.