✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Breezing Forms Pro: submissions as customizable tables

Read directly from breezingforms_submissions and pivot breezingforms_submission_values into named columns. Build cross-form inboxes, status-filtered audit views, and bulk-edit triage state without per-entry click-through.

♾️ Lifetime License available

SleekView table view for Breezing Forms Pro

Submissions as a workspace, not a per-form list

Breezing Forms Pro persists each submission as a row in breezingforms_submissions with per-field values written long-format to breezingforms_submission_values, one row per field per submission. The default admin renders per-form lists with a fixed column set, so cross-form views, value-based filters, and bulk operations on multi-form inboxes need either custom queries or a lot of click-through.

SleekView reads both tables and pivots breezingforms_submission_values at query time, so each submission is one row with named columns drawn from the form's element names. Add form_id as a column and you get a unified inbox across every Breezing form on the site, filterable by date, status, and any pivoted field value.

Inline edits update both tables with conflict detection, and the plugin's submission hooks fire so downstream integrations behave the same as a normal admin edit. Bulk operations iterate through the plugin's update layer, not a single bulk-replace, which keeps validation behaviour intact.

Workflow

From per-form lists to one cross-form workspace

1

Point at breezingforms_submissions

Pick the submissions table as the base. SleekView joins breezingforms_submission_values and reads the form definitions so the column chooser knows the real element names.
2

Pivot the values

Add any element name from breezingforms_submission_values as a column. The pivot runs at query time so changes to forms surface immediately.
3

Compose your filter

Combine form_id, status, submission date, and pivoted-value filters into one saved view. Triage inboxes and per-form audits share the same engine.
4

Edit inline and in bulk

Mark reviewed, discard spam, or update element values across many rows. The plugin's submission update layer fires the standard hooks for each change.

Sample columns

A typical Breezing Forms Pro submissions view

Cross-form submissions with the pivoted element values from breezingforms_submission_values rendered as named columns.
Source: wp_breezingforms_submissions + wp_breezingforms_submission_values
Submission # Form Submitted Email Country Status
#371 Contact Apr 24 alex@studio.co DE New
#370 Newsletter Apr 24 ria@design.io UK Reviewed
#369 Survey Apr 23 tom@hello.dev US Reviewed
#368 Contact Apr 23 mia@brew.coop NL Discarded

Comparison

Default Breezing Forms admin vs SleekView

Default Breezing Forms admin

  • Submissions are scoped per form with no cross-form inbox
  • Per-field values from breezingforms_submission_values only show inside the detail view
  • Bulk-changing submission status is limited and tied to one form at a time
  • Filtering on a specific element value across forms is not a first-class workflow
  • Custom column sets are not savable as named team views

SleekView

  • Cross-form submission table with form name and pivoted element values
  • Pivot breezingforms_submission_values into typed columns automatically
  • Inline-change status (new, reviewed, discarded) across many rows
  • Filter by form_id, status, submission date, and pivoted values together
  • Save filtered views per workflow and scope them per WordPress role

Features

What SleekView gives you for Breezing Forms Pro

Pivot element values into columns

Each submission's per-field rows in breezingforms_submission_values pivot into named columns at query time, so each row is one readable record instead of a long list of key/value pairs.

Combine filters across forms

Filter by form_id, status, submission date, and any pivoted element value in a single saved view. Cross-form inboxes load in one query, not three.

Bulk inline-edit status

Mark submissions reviewed or discarded across many rows. The plugin's submission update layer handles validation; conflict detection guards against stale edits.

Audience

Who uses SleekView for Breezing Forms Pro

Front desk & support

All inbound submissions in a unified table filtered to new plus last seven days. Mark reviewed inline, discard spam in bulk, keep the queue clean without bouncing between forms.

Research teams

Survey submissions across multiple forms with the response values pivoted into columns. Sort, filter, and slice without exporting to a spreadsheet for basic analysis.

Site administrators

Audit which forms still receive submissions, which sit idle, and which generate the most spam. A grouped view by form_id tells the maintenance story in one screen.

The bigger picture

Why long-format submissions need a pivot layer

Breezing Forms uses a long-format value store, with one row per field per submission, which is what lets the plugin support arbitrary form schemas without migrations. The trade-off is that the data is unreadable until you pivot it, and the per-form admin assumes that one form is the unit of work. Sites that run a handful of Breezing forms with low volume might not feel the cost, but the moment you have ten active forms and a moderator who needs to see today's inbound across all of them, the gap becomes obvious.

SleekView is the pivot layer that lets the same schema be read as a normal table. Add the element columns you care about, compose filters across forms, and edit through the plugin's own functions so downstream integrations behave correctly. The schema is fine, the storage is fine, only the way humans read the data needed to change.

Questions

Common questions about SleekView for Breezing Forms Pro

The Pro edition is what most teams run for real submission storage and the additional element types. The free edition uses the same breezingforms_submissions table structure, so SleekView reads from both, but Pro's extra element types and integrations add meta keys that surface as columns.

 

Yes. SleekView writes back through the plugin's submission update functions where available so registered actions still fire, and uses direct writes with conflict detection for fields the API does not fully expose. Validation rules registered on a form continue to apply on edit.

 

SleekView reads the distinct element names from breezingforms_submission_values for submissions in scope and exposes each as an addable column. The pivot runs at query time using a join, so newly added form elements appear immediately in the column chooser.

 

Yes. Add form_id as a column and either filter to a subset of forms or leave it open. For cross-form views, only element names shared across forms become useful columns; SleekView indicates which names belong to which form so the chooser stays sensible.

 

File-upload elements store either a URL string or an attachment ID in breezingforms_submission_values. SleekView renders those as clickable links or attachment previews depending on storage, so a moderator can review uploads without opening each submission's detail screen.

 

Yes. Save views and scope them per WordPress role or capability. Reception sees new submissions cross-form, research sees survey-only views with response columns, admins see grouped per-form audit views.

 

Filter to one email address for a complete picture of what Breezing stored about that person across forms. Export to CSV for a data-subject access request; bulk-delete to honor erasure, routed through the plugin's submission deletion functions so any registered cleanup logic runs.

 

No. SleekView is purely a read/edit layer over the submission tables. Form definitions and the builder remain untouched. Add or change form fields as normal; the pivot picks them up at query time on the next view refresh.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView