No. Rule evaluation happens at submission time inside Ninja Forms. SleekView reads the outcome that was stored to postmeta and displays it. Editing data in SleekView does not re-fire rules. If you need to re-run rules after editing, use the add-on's own hooks to trigger a re-evaluation.

Whatever the add-on writes. Common keys include _cl_actions_fired and per-rule trace data. The column picker reads what's actually in postmeta for each nf_sub row, so updates to the add-on's storage format appear without configuration changes.

If the add-on stored the trace (some versions do, others don't), it appears as a meta-key column. SleekView's expandable cell view can show a JSON-shaped trace without overflowing the table. For installations without trace storage, the audit is at the outcome level (branch and actions fired).

Pivoted entry-field columns use the form's field definitions to know which fields were configured as conditional. A blank value with the field flagged conditional + rule-hidden in the meta trace is presented as (hidden); a blank value with the field shown to the user but left empty is just blank. Visual distinction makes diagnosis quick.

Yes. Group on a branch-derived column (either a meta key directly, or a virtual column computed from rule outcomes) and SleekView shows row counts per group with sums and averages on numeric columns. Useful for shipping a weekly form report without writing a query.

Editing field values in SleekView changes the stored values in postmeta. It does not retrospectively re-run conditional rules. If a rule's branch was decided by a now-edited value, the recorded branch stays. To force a re-evaluation, use the add-on's own re-process hooks; SleekView's audit log tracks the edit so the discrepancy is traceable.

SleekView reads postmeta via indexed joins; the number of rules per form doesn't affect read performance. What can matter is the number of meta rows per submission, since heavily conditional forms produce more meta rows per nf_sub. Indexing on (post_id, meta_key) keeps queries fast; SleekView's default joins use this index automatically.

Conditional outcomes don't typically contain sensitive data; they're decisions about which fields and actions fired. Per-role view scoping means you can expose branch and actions-fired to marketing for reporting, while reserving field-value columns for support. Each saved view picks its own column set, so sensitive data stays in restricted views.