Â鶹ÊÓƵ

Web Communication

Enrollment Management and Marketing

Formstack Requirements and Reminders

Creating online forms using Formstack is easy, but there are guidelines each user must follow. Following these guidelines ensures your continued use of Formstack.
1

Formstack requires log-in using Single Sign-on. 

Enter your LEA@lamar.edu email and choose the option to sign in with your Lamar LEA. You will be taken to the Â鶹ÊÓƵ log-in page to sign in using your LEA and password.

 welcome screen for formstack with arrows pointing to username field and link to sign in with lamar lea


2

You must embed ALL forms on a Â鶹ÊÓƵ branded page located at www.lamar.edu/forms within the CMS. This includes internal forms used for staff and faculty.


Form links hosted through Formstack are not allowed and are disabled when the form is embedded, when the form begins receiving submissions, or after 3 days of creation, whichever comes first. Users reinstating Formstack-hosted links after they have been disabled run the risk of having their Formstack access rescinded.


formstack embed page with arrow pointing to green share box and arrow pointing to embed this form on your website javascript field If you do not have access to www.lamar.edu/forms in the CMS, please create your form and send the embed code to your department liaison to set up your branded page. Embed codes are found under the "share" tab.


3

Your form must redirect to a submission confirmation page after the user submits.


Create your confirmation page in the CMS and paste the published URL into Formstack.

Welcome and submission message; arrow pointing to add a submission message button; submission message settings, arrows pointing to redirect to a custom url radio button and external link entry field
Submission message options are found under the "Settings" tab through Welcome & Submission Message.


4

Images within forms are not recommended but if used must be placed in a description field.

 
Images and text placed at the top of forms above form fields should be placed within the CMS page above where the form is embedded.

We suggest you avoid using images inside of Formstack. 

advanced fields box with arrow pointing to description area button If you feel an image is important, simply drag a description area into the form builder and insert your image through the text editor.


5

Every form must contain a link to Â鶹ÊÓƵ's privacy policy.


Drag the privacy policy, located at the end of the "Your Saved Sections" area, right above your submit button.

privacy policy above submit button; location of privacy policy saved section at bottom of list


6

Configuration of notification and confirmation emails should use a custom address with the From Name being "Â鶹ÊÓƵ" and the From Email Address being "notifications@forms.lamar.edu.

Confirmation "reply to" emails can use department or individual @lamar.edu accounts where appropriate. Notification emails being sent to employees/departments upon form submission should be sent to a @lamar.edu email address.

notification email settings show custom address field, name as Â鶹ÊÓƵ, email address as notifications@forms.lamar.edu; confirmation email settings show FROM field as being "Â鶹ÊÓƵ" <notifications@forms.lamar.edu>

Notification and confimation email settings are found under the "Settings" tab through Emails & Actions.


7

When including a signature line on your form, ADA compliance requires that you include an option for a typed name to serve as signature.


Field logic must be used for the appropriate choice to appear at the time of selection.

template showing fields for type name and signature options


8

When including an upload field or signature field in your form, you MUST contact Web Communication to ensure viewing access for upload links.


Uploaded documents and signature images are stored securely in Formstack and require access in order to be viewed. Contact Christy Swanson at clswanson@lamar.edu to have this access granted to additional departmental employees who need to view items uploaded through these form fields.