Documentation Vision Library+ Documentation

Vision Library+ / Tables and monitoring

Event Frame Form+

Event Frame Form+ presents event frames as editable cards so operators can review event details and update permitted event-frame attributes without opening a separate application.

Overview

Event Frame Form+ presents event frames as editable cards so operators can review event details and update permitted event-frame attributes without opening a separate application.

Event Frame Form+ icon

When to use it

Use Event Frame Form+ when an operator must work through event frames individually, edit configured fields, acknowledge events, or run supported quick actions from a PI Vision display.

Use Events Table+ when comparison, grouping, bulk review, or tabular export is more important than a focused card workflow.

Before you begin

  • Confirm that PI Web API access and event-frame write permissions are available to the intended operators.
  • Prepare an event-frame search with the AF database, template, time range, and optional filters required by the workflow.
  • Decide whether fields should be discovered automatically or restricted to an approved configured list.

Important: Saving a card, acknowledging an event, or running a write-enabled quick action changes PI System data. Test the configured actions with a non-production event before publishing the display.

Add and set up the symbol

  1. Select Event Frame Form Plus in the PI Vision symbol gallery.
  2. Add event-frame attributes or configure the event search in the configuration pane.
  3. Under Event Frame Fields, choose Automatic or configure the fields operators may view and edit.
  4. Under Card options, select the header fields, density, expansion state, and missing-value behavior.
  5. Enable only the quick actions required by the operating procedure.
  6. Open a returned card and verify field types, write permissions, and save behavior.

Use the symbol

Expand a card to review its configured fields. Edit a permitted value, then select the card's save action to write the changes. Revert the card to discard unsaved edits.

The symbol warns before navigation when cards contain unsaved changes. Enumeration, Boolean, numeric, text, and time fields use controls appropriate to their AF data type.

Configure the symbol

Event-frame fields

  • Field source: Uses discovered event attributes or an explicit configured list.
  • Control type: Selects the editor used for a field, including automatic, text, numeric, Boolean, enumeration, and time controls.
  • Label and state names: Overrides the operator-facing field label or enumeration text without changing the stored value.
  • Limits and multi-state: Applies database or custom numeric limits and optional field or card coloring.

Quick actions

  • Acknowledge: Writes the configured acknowledgement state when supported by the event.
  • Copy, split, and details: Shows the enabled event actions in each card's action menu.

Card options

  • Start expanded: Opens cards when they are loaded.
  • Show children and comments: Adds related event information to the card workflow.
  • Density and field width: Controls how much information fits in each card.
  • Header fields: Selects the event properties shown before the editable field list.

Examples

Review and classify downtime events

Search for open downtime events, expose the classification and comment attributes, and enable acknowledgement only after the responsible role and write permissions have been verified.

Filtering

Event Frame Form+ receives Master and Linked filters. Under Filtering > Input, map a channel to a target property in the form's Event Frame data. The form rerenders from its loaded events without starting another Event Frame search. If a card is dirty or saving, the update is deferred so unsaved edits are not discarded. The symbol does not publish filters.

See [Filtering dashboards](../filtering.md) for channel setup and search limitations.

Troubleshooting and limitations

  • No cards appear: Verify the AF database, event-frame template, time range, and search filters.
  • A field is read-only: Confirm the attribute is writable and that the current account has PI Web API write permission.
  • A save fails: Review the field data type, enumeration value, server message, and event-frame permissions before retrying.
  • The display cannot be closed cleanly: Save or revert every dirty card before navigating away.