website logo
⌘K
Introduction
PORTAL
Agency Whitelabelling
PAGES
Pages - Accessing Page Data
Pagination Layouts
Page Templates
FORMS
Form Confirmation Pages
Adding a Progress Bar
Adding Custom CSS To Show Form Submit Process
Dynamic Content in Workflow and Autoresponder Emails
How to output Custom Field Set fields in a Form's Custom Layout
Custom JavaScript Validation for Forms
File Upload Previews
FAQ
CATEGORIES
Filtering WebApps and Modules by Categories
Outputting Categories on WebApp / Module / eCommerce Layouts
Outputting Category Fields in any Location
Category Detail Layouts
FAQ
COMPANY INFORMATION
Company Information
SITE SEARCH
Site Search
PUBLIC API/ZAPIER
Zapier - Formatting arrays correctly
Public API/Zapier Changelog
MODULES
Module Marketplace
Building Custom Modules
Siteglide Modules
Front-end Submit Modules
DATA STRUCTURES
Automations
Creating WebApps from the CLI
Field Types
WEBAPPS
Front-end Submit WebApps
Layouts
Search and Filtering
Understanding Custom Field Names and IDs
FAQ
CRM
User Details
User Secure Zones
Storing User's Favourite WebApp / Module Items
User's Form Submissions (Cases)
How Users Edit their Email and Password Front End
Editing a User's CRM record Front End with Custom Field Sets
CLI
Introducing Siteglide CLI
CLI Changelog
Secure Zones with CLI
Page Templates with Siteglide CLI
Pages with Siteglide CLI
Includes with Siteglide CLI
Managing Email Templates
Migrate - Manual Form setup
Migrate - Convert existing Forms
Liquid
Accessing Assets
Liquid Dot Notation
Using WebApp Collections- Tutorial
Using the current_user object with Secure Zones
Preventing Duplicate Content with Query Parameters- Canonical URL and Robots.txt
FAQ
GraphQL
Tutorial Overview
About GraphQL
Tutorial 1- Your First Query
Tutorial 2 - Pagination
Tutorial 3 - Filtering the Results
Tutorial 3 - Answers to the First Filtering Challenge
Tutorial 4 - Advanced Filtering
Tutorial 4 - Challenge Answers
Tutorial 5 - Using Liquid to run GraphQL queries on your Site
Tutorial 6 - Variables
Tutorial 6 - Answers to the Variables Challenge
Tutorial 7 - Sorting
Tutorial 8 - Building a Liquid API GET Endpoint Page powered by GraphQL queries
Best Practice and Performance
Module/WebApp Caching
Getting Started with Liquid Caching - to Reduce Server Response time and Improve Performance
Includes
ecommerce/checkout_standard
Frequently Asked Questions
Using Liquid Logic to Check if a field exists, or is empty on the Front End
How do I learn more about Liquid?
How to setup a multi domain start page
Docs powered by archbee 
16min

User's Form Submissions (Cases)

Allow Users to keep track of their communication history with your Client by outputting Form Cases.

Prerequisites

  • This Layout must be outputted inside a Page protected by a Secure Zone

You can use the following links to learn how to set up a Secure Page and the means to access it:

  • Create a Secure Zone
  • Create a Secure Zone Sign Up Form
  • Add a Secure Zone to a Page

Introduction

Allow Users to keep track of their communication history with your Client by outputting Form Cases.

Syntax

{% include 'user_form_submissions', layout: 'default' %}

Parameters:

  • layout

File Structure

You can find the user_form_submissions Layouts at the following path in Code Editor: layouts/modules/module_5/user_form_submissions/

Inside this folder, a single Liquid file can be created to act as your Layout. There is no "wrapper" and "item" file needed for this kind of Layout.

Developing the Layout

The Loop

You'll need to use a Liquid For Loop to loop over the records in this Layout.

One of the benefits of this is that you can rename the variable under which your fields are kept. If you like you can store the variables under the namespace "this".

HTML
|

Or, if you want to output the form_submissions layout inside a user_details Layout for example, you can store the variables under a different namespace e.g. case and continue to use this to refer to the user_details (Liquid variables are always inherited by Layouts included within them).

HTML
|

Available Fields (within the loop)

In the following examples, we'll use the namespace "case", but you can substitute this for the namespace you chose when creating your loop.

  • {{case.form_name}} - The user-friendly name of the Form
  • {{case.name}} - The model_schema_name of the Case- e.g. form_3. This can tell you the Form's ID.
  • {{case.id}}
  • {{case.created_at}} - The date the Form was submitted. Use the "| date" filter with Ruby formatting to format.
  • {{case.properties.name}}
  • {{case.properties.email}}
  • {{case.properties.user_id}}
  • {{case.properties.form_field_1_1}} - Access any of your custom Form Fields with a variation of this output tag. The first number refers to the ID of the Form. The second number refers to the ID of the Field. You can check these IDs for your own custom fields in the Siteglide Admin.

To see the available data on Page load as JSON, output your namespace within the loop:

e.g. <p>{{case}}</p>

Updated 19 Oct 2021
Did this page help you?
Yes
No
UP NEXT
How Users Edit their Email and Password Front End
Docs powered by archbee 
TABLE OF CONTENTS
Prerequisites
Introduction
Syntax
File Structure
Developing the Layout
The Loop
Available Fields (within the loop)