Alarm Graphic Attachment - SEAL Script

[StefanLundin]

Purpose

This SEAL Script links Alarm objects in EcoStruxure Building Operation (EBO) to the “right” visualization by analyzing real bindings. It can attachTGML Graphicsdirectly, or—when you choosePanels—it prefers Panels that reference those Graphics. Run it in Preview to validate what would change, then Apply to write to the database.

---

What the script does

• Scans your selected Alarm objects.
• Resolves binds to discover the TGML Graphics that are related to each alarm.
• Optionally expands discovery via the alarm’s MonitoredVariable/ObjectPropertyReference (if enabled).
• Optionally prefers Panels that reference the discovered Graphics (when “Panels” is selected).
• Applies a candidate whitelist you paste from EBO Workstation Search to ensure only allowed Graphics/Panels are attached.
• Writes attachments to alarm objects (and optionally enables Display attachment on alarm) when you choose Apply.

---

Typical use cases

• Batch‑link alarms to their operating Graphics after commissioning.
• Prefer a full Panel view (menu + viewers + graphics) where available; otherwise link the Graphic.
• Standardize attachments across systems or sites using Workstation Search selection and a controlled candidate list.

---

UI overview

Run Mode

• Preview (no changes): Dry run. Prints candidates that would be attached.
• Apply (write changes): Writes attachments to alarms and optionally enables Display on alarm.

Paste from Workstation Search
Copy the search result from EBO Workstation and paste it into these inputs. The script extracts valid paths automatically and uses them to:

• Alarm objects: Which alarms to evaluate and update.
• Candidate attachments (Graphics or Panels): Which visuals are allowed to be attached (whitelist).
• Menu Objects (optional): Menus whose linked Graphics should be added automatically to your candidate list (useful when Graphics are referenced indirectly through menus).

Attachment Type

• Graphics only: Attach Graphics found from binds that are allowed by your candidate list.
• Panels (fallback to Graphics): Try to attach Panels that reference those Graphics; if none is found (or allowed), attach the Graphic instead. Include Panels in your candidate list for this to work as intended.

Options

• Also consider monitored‑variable bindings: Include Graphics discovered via the alarm’s MonitoredVariable/ObjectPropertyReference (good when visuals are related indirectly through the monitored variable).
• Display attachment on alarm: If enabled, the attached item opens automatically when the alarm becomes active.

---

Copy/paste from EBO Workstation — how and why

The script relies on your Workstation searches to define scope and control attachments. You can paste the entire search result; the script extracts valid paths automatically (paths starting with “/”).

1. Alarm objects

   • Search for the alarms you want to update (e.g., alarms within a building, system folder, or entire server).
   • Copy the search result.
   • Paste into Alarm objects.
   • Why: This defines exactly which alarms the script will examine and update.

2. Candidate attachments (Graphics or Panels)

   • Decide what you intend to attach (see “Attachment Type”).
   • If you selected Graphics only, search and paste Graphics.
   • If you selected Panels (fallback), search and paste Panels (you may also paste Graphics to allow fallback).
   • Why: This acts as a whitelist. The script will only attach items that appear in this list (plus any Graphics discovered from Menu Objects below).

3. Menu Objects (optional)

   • Search for Menu objects and paste the result.
   • The script will scan these menus for any linked Graphics and add those Graphics to your candidate whitelist automatically.
   • Why: This explicit captures Graphics that are referenced from menus and uses those as a whitelist for alarm attachments.

Tip: Start with a narrow scope (one system) to validate outcomes in Preview, then expand.

---

Safety first

• Back up your system before bulk updates.
• Start with a limited scope (one system) and Preview to validate.

---

Availability

The script is available in SEAL Script → Standard Scripts.

---

[Adam_Tri-M]

This doesn't seem to work for Bacnet Alarms on MPx Controllers. Any ideas?

[APA]

I could not replicate the issue. I works just fine with MPx and RPx controllers. But I did find another issue where graphic is added as a content to a panel and not as work area initial path, it would not find the panel.

I attached a test version where that issue I found is fixed. 

Remember to set the Base Path to the root of the Automation Server or use the "Servers" folder if setting in multiple automation servers at once. 

Are you getting any errors?

[Adam_Tri-M]

Thanks!

I just tested it again (at least with your updated version) and is does work.

No idea what I did wrong before.

Appreciate the help!

[APA]

Awesome! I will update this version to the standard later.