Avoid naming components with common values. Header and footer modules cannot have components with the same Property ID. Otherwise, neither display in Express View. It's a best practice to differentiate components with a descriptive name—for example, dwFooterOutput.
Connecting a Footer Module to an Application
Now that you have a footer module, connect it to your application.
To connect a footer at the Application level:
1.
Navigate to the application that contains your footer module.
2.
At the top of the page, click ···(options).
3.
Select Settings.
4.
From the Footer Module drop-down, enter or select the footer module.
5.
Click Save & Close.
Previewing a Footer Module
It's important to note that all modules you plan to have navigate to using your footer module must exist in the same application. Otherwise, you'll receive a 403 error.
To preview the footer module at the Application level:
1.
Navigate to the application that contains your footer module.
2.
At the top of the page, click ···(options).
3.
Select Preview. The application displays on a new page with the footer module present at the bottom.
To successfully preview your footer module, you must preview it at the Application level. Otherwise, you must manipulate the browser URL to consider any redirects. The URL looks like the following: https://www.{your-environment}.io/app/{appPath}#/display/{{moduleId}}/{{submissionId}}/{{moduleId}}.
Disconnecting a Footer Module
If you decide you do not want a footer in your application anymore, you can remove it.
To disconnect a footer at the Application level:
1.
Navigate to the application that contains your footer module.
2.
At the top of the page, click ···(options).
3.
Select Settings.
4.
From the Footer Module drop-down, click the X next to the Footer Module’s name.
You'll need to create a footer module before connecting it to your application. The best way to achieve this task is to add your footer module to the Library. After adding your module to the Library, you can share it with all other applications in your environment.
If you plan to create a footer, be mindful when naming components. Both the header and footer modules cannot have components with the same Property ID. Otherwise, neither display in Express View. It's a best practice to differentiate components with a descriptive name—for example, dwFooterOutput.
1.
At the top right of the Unqork Designer Platform, click the Library ▾ drop-down.
2.
Select Library Elements.
3.
Click + Create New.
4.
In the Module Name field, enter a name for your footer module.
To make it easier to locate your footer later, begin your module name with Footer. For example, Footer: Acme Corp.
5.
Click Create.
From here, open the module and customize your footer. Here are the following supported components:
Now that you have a footer, connect it to your application.
To connect a footer module to your application:
1.
Navigate to your workspace and locate your application tile.
2.
Click the ellipsis (···) button.
3.
Select Settings.
4.
From the Footer Module drop-down, enter or select a footer module.
5.
Click Save.
Previewing a Footer Module
It's important to note that all modules you plan to have navigate to using your footer module must exist in the same application. Otherwise, you'll receive a 403 error. The following image shows you how to preview a module at the Application level:
To successfully preview your footer module, you must preview it at the Application level. Otherwise, you must manipulate the browser URL to consider any redirects. The URL looks like the following: https://www.{your-environment}.io/app/{appPath}#/display/{moduleId}/{submissionId}/{moduleId}.
Disconnecting a Footer Module
If you decide you do not want a footer in your application anymore, you can remove it.
To remove a footer module from an application:
1.
Navigate to your workspace and locate your application.
2.
Click the ellipsis (···) button.
3.
Select Settings.
4.
From the Footer Module drop-down, click the X next to the Footer Module’s name.
Button and 
Hidden components.
Columns, 
Field Group, HTML Element, and Panel components.
Decisions, 
Initializer, and Plug-In components.
Settings
