Link Search Menu Expand Document


Table of contents

  1. Overview
  2. Dynamic Content Page
  3. Inputs Page
  4. Best Practices


Inputs can either be used within Dynamic content as filters or can be used as Dynamic content themselves. Inputs are exposed to End Users and are used to fetch the necessary data to customize the template.

The appearance of Inputs to End Users is customizable.

  • Display Name: The name of the Input displayed in the front end to the End User
  • Description: This description is also displayed to the End User in the front end
  • Input Source:
    • User Input: there is no data source for the Input but rather requires the user to input
    • List: the values for the Input come from a fixed list of values
    • Query: the values in the Input are populated via a query
  • Input Type: depending what Input source you selected, you can select a type:
    • Date range
    • Single date
    • Single select dropdown
    • Multi select dropdown
    • Boolean
    • Text box

There are two ways to create an Input within the platform:

  1. Dynamic contents Page
  2. Inputs Page

Dynamic Content Page

If you are creating a piece of dynamic content with a SQL query then you can create new Inputs by typing the following syntax within your SQL query - &: - followed by the Input name. A grey pill will appear above the SQL editor. If the Input already exists then the pill will be orange. If you click on the pill a popup module will appear that will allow you to configure the Input.

Inputs Page

You can also create a new Input, as well as view all existing Inputs by going to the Inputs page by clicking on the Inputs icon in the navbar. On this page you can see a library of all the Inputs that have been created, how they are configured, and all the dynamic content that use a particular paramater.

Best Practices

It’s important that the Inputs you select in your queries have End User-friendly display names so when they attempt to generate presentations they understand what they need to input. Strategies to improve usability and reliability include:

  • Create dependent Inputs (e.g. contract IDs which updated when a company is selected)
  • Create Query or API-based Inputs which pull directly from data sources (e.g. select name in Salesforce or list of Quarters from a table) rather than self-made lists.
  • Use common names instead of table IDs to reduce friction in generating presentations.