Footer Module

Estimated Reading Time:  2 minutes

Overview

A footer is the bottom section of a web page. You might add a logo, calls to action, navigational elements, search fields, or other features to the footer. You’ll create this in its own module, then connect it to your application.

It's important to note that Footer module RBAC (role-based access control) is defined by the RBAC of the embedded components.

What You’ll Learn

In this article, you'll learn how to create, preview, connect, and disconnect footer modules to an application.

Creating a Library Element Footer

You'll need to create a footer module before you can connect it to your application. The best way to do this is to add your footer module to the Library. By adding your module to the library, you can share it throughout your applications and even the entire environment.

NOTE  If you plan to create a footer, be mindful when naming components. Both the header and footer modules can't have components with the same Property ID. Otherwise, neither display in Express View. It's best practice to differentiate components with a descriptive name — for example, dwFooterOutput.

1.

From the Library menu in the bar at the top of the page, select Library Elements.

2.

Click Create New.

3.

In the Module Name field, enter a name for your module.

4.

Select where you want to share the footer. You can select individual workspaces or the whole environment.

5.

Click Create.

From here, you can open the module and customize your footer. Here are the following supported components:

• Primary Field: All components.

• Secondary Field: Button and Hidden components.

• Display & Layout: Columns, Content, Field Group, HTML Element, and Panel components.

• Data & Processing: Data Workflow, Decisions, Initializer, and Plug-In components.

Previewing a Footer Module.

It's important to note that all modules to plan to navigate to using your footer module must exist in the same application of your workspace. Otherwise you'll receive a 403 error. The following image shows you how to preview a module at the application level:

Also, to successfully preview your footer module, you must preview it at the application level. Otherwise, you need to manipulate the browser URL to take into account any redirects. The URL looks something like the following: https://www.{your-environment}.io/app/{appPath}#/display/{moduleId}/{submissionId}/{moduleId}.

Connecting an Existing Footer Module to Your Application

If you already have an existing footer within your workspace or Library, you can connect it to your application.

1.

Navigate to your workspace and locate your application tile.

2.

From the ellipsis (…) menu, click Settings.

3.

From the Footer Module drop-down, select your footer module.

4.

Click Save.

Disconnecting a Footer Module

If you decide you don’t want a footer in your application anymore, it’s simple to remove.

To remove a footer module from an application:

1.

Navigate to your workspace and locate your application.

2.

From the ellipsis (…) menu, click Settings.

3.

From the Footer Module drop-down, click the X next to the footer module’s name.

4.

Click Save.

Best Practices

• Set RBAC (role-based access control) for footer modules to Anonymous. If RBAC is not set to anonymous, end-users can't view the footer in your application.