Skip to content

BrightLeaf Digital

BrightLeaf Digital
  • Home
  • Gravity Forms Plugins
    • Integrate Asana with Gravity Forms
    • Mass Email Notifications for Gravity Forms
    • Global Variables
    • Recurring Form Submissions
    • Folders4Gravity
    • GravityOps Search
  • Docs
  • Snippet Library
  • Blog
  • Contact Us
BrightLeaf Digital
  • Home
  • Gravity Forms Plugins
    • Integrate Asana with Gravity Forms
    • Mass Email Notifications for Gravity Forms
    • Global Variables
    • Recurring Form Submissions
    • Folders4Gravity
    • GravityOps Search
  • Docs
  • Snippet Library
  • Blog
  • Contact Us

BL Digital Guidelines & Policies

2
  • Using the Plugin on a Client Site
  • BrightLeaf Digital Refund Policy

Integrate Asana with Gravity Forms

29
  • Getting Started
    • Integrate Asana with Gravity Forms — Welcome & Overview
    • Finding the Plugin in Your Dashboard
  • Setup
    • Connect Asana (OAuth)
    • Create Your First Feed (5-Minute Quickstart)
  • Settings Reference
    • Feed Settings — Name, Conditional Logic & Trigger
    • Asana Task Settings Reference
    • Feed Triggers
    • Mapping Custom Fields
    • Workflow Steps — Create Task
    • Workflow Steps — Update Task
  • How-to Guides
    • Use Conditional Logic to Route Tasks
    • Choosing the Right Feed Trigger
    • Attach File Uploads to Tasks
    • Use Asana Custom Fields as Automation Signals
    • Workflow Steps: Create Task
    • Workflow Steps: Update Task
  • Troubleshooting
    • Basics
    • Reconnecting / Resetting Credentials
    • Task Creation Failed → Backup Task Behavior
    • Items Not Showing in Drop-downs
    • Feed Page Unavailable
    • Task Description Caused Errors
    • Duplicate Tasks
  • Explanations & Concepts
    • OAuth and Scopes
    • Permissions & Workspaces
    • How Feeds Run
    • Performance Considerations
  • Changelog/Roadmap
    • Changelog
    • Roadmap

Mass Email Notifications for Gravity Forms

38
  • Getting Started
    • Mass Email Notifications — Welcome & Overview
    • Finding the Plugin in Your Dashboard
    • Before You Begin: Email Limits & SMTP
    • How Batches Are Created & Sent (5-Minute Delay)
    • Recommended Setup Pattern — Master Control Notification Form
  • Setup
    • Configure Global Send Limits (Throttling)
    • Create Your First Feed (5‑Minute Quickstart)
    • Use a GF Notification as Your Email Template
    • Schedule Batches for a Future Date
  • Settings Reference
    • Global Settings — Limits Reset Rules, Old Batch Cleanup, Cron Toggle & Next Run
    • Feed Settings — Name, Label, Dedupe, Completion Email
    • Choose Target Form & Email Field
    • Email Settings — From, Reply-To, Subject, Message, Merge Tags
    • Merge Tag Fallbacks & CSV Column Mapping
    • Schedule Based on Date Field
    • Conditional Logic — Feed Form vs. Target Form
    • CSV Ingestion
  • How‑to Guides
    • Send an Update to Everyone Who Used Another Form
    • Using Target-Form Merge Tags
    • Segment Recipients with Target-Form Conditional Logic
    • Import a CSV List and Personalize with Merge Tags
    • Build a Front-End “Trigger” Form for Non-Admin Staff
    • Use Populate Anything for Dynamic, Person-Specific Emails
  • Troubleshooting
    • Basics
    • Batches Not Sending / Cron Not Running
    • Preview Shows 0 Recipients with Target-Form Filters (Premium)
    • Hitting Rate Limits
    • Emails Going to Spam
    • Entries/Batches Missing After Deletions
  • Explanations & Concepts
    • How Batching & Cron Work
    • Throttling Models Explained
    • Deduplication Strategy
    • Batch Statuses & Actions
    • What Gets Logged
    • Limitations & Design Trade‑offs
    • Security & Permissions Considerations
  • Changelog / Roadmap
    • Changelog
    • Roadmap

GravityOps Search

5
  • The Display Attribute
  • Nesting Shortcodes
  • Using Search Operators
  • Multi-Input Field Support
  • General Notes
View Categories
  • Home
  • Docs
  • GravityOps Search
  • The Display Attribute

The Display Attribute

The display attribute for GravityOps Search controls what is shown for each matching entry. You can use it in two different formats:

 1. Basic Comma-Separated Field List #

You can pass a simple comma-separated list of field or property IDs, like:

display="13,14,15"
  • This will output the values of fields 13, 14, and 15 for each matching entry.
  • By default:
    • Single field per entry → results are separated by commas
    • Multiple fields per entry → fields are separated by commas; entries are separated by semicolons
  • You can override the entry separator with the separator attribute (supports HTML).
  • Note: The behavior of the separator applies to both the basic comma-separated field list and the custom
    formatting with placeholders options. The separator is only applied when there is more than one entry returned by the
    search. To configure a blank separator, enter __none__.

2. Custom Display String with Placeholders #

You can build a custom display using placeholders inside a string. This gives you full control over formatting, including HTML, text, and shortcodes.

display="Name: {13}, Email: {14}"

Placeholder Formats #

You can use placeholders to insert entry values into the output:

  • {id} – standard numeric field or entry property (e.g., {13}, {id}, {form_id})
  • {gos:id} – for non-numeric properties when used in contexts where merge tags may be parsed, such as Gravity View custom content widgets, confirmations, or notifications
  • gos:id – used only in nested shortcodes
  • Tip: Use {id} for most numeric fields, and {gos:id} for text-based meta like created_by, date_created, etc.

Default Values for Placeholders #

You can include a fallback/default value inside a placeholder using ;:

{5;No Name Found}
{gos:created_by;Current User}
  • Only curly-brace formats ({}) support default values.
  • Plain format (gos:id;default) is not supported.

Placeholder Behavior Notes #

  • If the first placeholder in your display string resolves to an empty value, the entire result will be treated as empty and skipped (unless a default value is configured).
  • Always match placeholders to real field or entry property IDs in your form.
  • Avoid nesting " inside the display string if you’re already using double quotes to wrap it — prefer single quotes inside instead.
display="<a href='mailto:{13}'>{13}</a>"  ✅
display="<a href="{13}">"                 ❌

Special Placeholders #

  • {num_results} or {gos:num_results} will be replaced with the total number of results returned.
    Useful when using limit=”all” or for showing counts like: “{num_results} entries found.”
  • To see which keys are available for use in the display or search attributes:[gravops_search display="meta"]This will return a list of all meta keys for the matched entry. You can customize the layout with the separator attribute.
  • Tip: You can also find meta-keys by hovering or clicking on column headers in Forms → Entries in the WP admin. The meta key appears in the URL.

Nested Shortcodes #

You can include shortcodes inside the display attribute using double curly braces ({{ ... }} syntax). This allows you to embed other shortcodes—like gravitymath, gravops_search or any other shortcode—within the output for each entry. See the dedicated doc for more info.

Updated on September 18, 2025

What are your Feelings

  • Happy
  • Normal
  • Sad

Share This Article :

  • Facebook
  • X
  • LinkedIn
  • Pinterest
Nesting Shortcodes
Table of Contents
  •  1. Basic Comma-Separated Field List
  • 2. Custom Display String with Placeholders
  • Placeholder Formats
  • Default Values for Placeholders
  • Placeholder Behavior Notes
  • Special Placeholders
  • Nested Shortcodes
© 2025 BrightLeaf LLC dba BrightLeaf Digital
  • Home
  • Gravity Forms Plugins
    • Integrate Asana with Gravity Forms
    • Mass Email Notifications for Gravity Forms
    • Global Variables
    • Recurring Form Submissions
    • Folders4Gravity
    • GravityOps Search
  • Docs
  • Snippet Library
  • Blog
  • Contact Us