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 
17min

WebApps - Front End Edit

Introduction

If a logged-in visitor to your Site has submitted a WebApp Item, they can now edit it too.

The WebApp Creator

Most WebApps, including those created by the Admin and those created by visitors who are not logged in will not store the ID of a creator. 

However, any WebApps created Front-End by a logged in User will store their creator's ID in the creator field. 

Filtering a WebApp List by creator

Finding WebApp Items created by the current user

HTML
|

Finding WebApp Items created by any specific user

In this example we create a variable by hard-coding a specific User ID.

HTML
|

Outputting information about the creator in the WebApp Layout

You can now access the following fields inside a WebApp Layout:

  • {{this.creator.id}} 
  • {{this.creator.name}} 
  • {{this.creator.first_name}} 
  • {{this.creator.last_name}}
  • {{this.creator.created_at}} 

Only owners of a WebApp Item that are logged in can view an Edit Form for that Item.

Find other WebApp items with the same creator

You could of course combine both of these features- creating a link to the same page including the creator_id as a query parameter and then filtering by that ID using context.params to fetch the ID from the URL.

Syntax for the Edit Form

Including the Form inside a WebApp Layout

Unlike the "Add" Form, the Front End WebApp Edit Form must be linked to the specific WebApp Item it will Edit. This means you can only output the Form inside a WebApp Detail or List Layout file. 

To include the Edit Form inside a WebApp Layout, add the Liquid tag: {% include 'webapp_form_edit', layout: 'default' %} Parameters: 

  • layout - Optional - Choose the name of your Layout file

Important

Even if you include the Liquid Tag, the Form will only display for visitors who are logged in and are registered as that WebApp's creator.

Developing the Form Layout

The Edit Form will work if you use the same Layout as you used for your add Form.  However, you may wish to use an alternative Layout so you can add some additional features.

Dynamic Fields from the WebApp

As you're including the Edit Form inside a WebApp Item, you have access to the WebApp fields that are inherited from the WebApp Layout.

One example might be adding a Title to the Form which dynamically references the WebApp Item: <h3>Edit {[this.name}}</h3> Another example might be displaying the creator's name: <h4>By {[this.creator.name}}</h4>

Pre-filling values 

In a Form Layout, we use the form_builder variable to dynamically add the correct name Attribute to inputs. You can use this to output the pre-filled value; instead of the name property, output the value property. For this example WebApp field: <input name="{{form_builder.fields.properties.webapp_field_1_1.name}}"> ...you can use the name field and replace .name with .value to add a value attribute:

HTML
|
Updated 19 Oct 2021
Did this page help you?
Yes
No
UP NEXT
WebApps - Delete owned WebApps from front-end
Docs powered by archbee 
TABLE OF CONTENTS
Introduction
The WebApp Creator
Filtering a WebApp List by creator
Finding WebApp Items created by the current user
Finding WebApp Items created by any specific user
Outputting information about the creator in the WebApp Layout
Find other WebApp items with the same creator
Syntax for the Edit Form
Including the Form inside a WebApp Layout
Important
Developing the Form Layout
Dynamic Fields from the WebApp
Pre-filling values