Changes for page 7. Events Setup

Last modified by Iaroslav Platonov on 2026/06/09 11:03

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Children
- Content
- Comments
- Attachments (60)
- Information
- Likes

From 63.1 to 63.2

From version 63.2

edited by Lana
on 2025/12/11 01:22

Change comment: There is no comment for this version

To version 65.1

edited by Iaroslav Platonov
on 2026/06/09 11:03

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Parent

@@ -1,1 +1,1 @@
--CENTO onboarding.WebHome
++CENTO Manuals.WebHome

Author

@@ -1,1 +1,1 @@
--XWiki.Lana
++XWiki.Iaroslav

Content

@@ -1,552 +1,690 @@
--= CONTENT =
++{{html clean="false"}}
++<style>
++.doc-content h1::before,.doc-content h2::before,
++.doc-content h3::before,.doc-content h4::before,
++.doc-content h5::before,.doc-content h6::before { content:none !important; display:none !important; }
++.doc-content { counter-reset:none !important; }
++#rn-prog { position:fixed;top:0;left:0;height:3px;width:0;background:#005AB4;z-index:9999;pointer-events:none; }
++.doc-wrap { position:relative; }
++.doc-content { margin-right:224px;border-left:1px solid #E8E8E8;border-right:1px solid #E8E8E8;padding:0 32px; }
++.doc-toc { position:absolute;top:0;right:0;width:200px;font-size:12.5px;line-height:1.55;padding:20px 0 20px 16px; }
++.doc-toc.is-fixed { position:fixed;width:200px;overflow-y:auto;z-index:10; }
++.toc-header { display:flex;justify-content:space-between;align-items:center;margin-bottom:10px; }
++.toc-header strong { font-size:13px;font-weight:700;color:#222; }
++.toc-toggle { background:none;border:none;cursor:pointer;color:#555;font-size:14px;padding:0 2px;line-height:1; }
++.toc-toggle:hover { color:#222; }
++.doc-toc ul { list-style:none;margin:0;padding:0; }
++.doc-toc li { margin:0; }
++.doc-toc a { display:block;padding:3px 0;color:#555;text-decoration:none;border-left:2px solid transparent;transition:color .12s; }
++.doc-toc a:hover { color:#222;text-decoration:underline; }
++.doc-toc a.toc-on { color:#222;font-weight:700;border-left:2px solid #005AB4;padding-left:5px; }
++.tl1 > a { font-weight:600;color:#222; }
++.tl2 > a { padding-left:14px; }
++.tl3 > a { padding-left:26px;font-size:12px; }
++.doc-content h2 { font-size:1.15em;font-weight:700;color:#222;margin:36px 0 10px 0;display:flex;align-items:baseline;gap:7px;scroll-margin-top:16px; }
++.doc-content h3 { font-size:1em;font-weight:700;color:#222;margin:22px 0 8px 0;display:flex;align-items:baseline;gap:6px;scroll-margin-top:16px; }
++.doc-content h4 { font-size:.93em;font-weight:700;color:#222;margin:14px 0 6px 0;scroll-margin-top:16px; }
++.doc-content p { font-size:.93em;color:#333;line-height:1.75;margin:0 0 12px 0; }
++.doc-content ul,.doc-content ol { font-size:.93em;color:#333;line-height:1.75;margin:0 0 12px 0;padding-left:24px; }
++.doc-content li { margin-bottom:4px; }
++.doc-content strong { color:#222; }
++.doc-content code { background:#f5f5f5;border:1px solid #E8E8E8;border-radius:3px;padding:1px 5px;font-family:Menlo,Monaco,Consolas,"Courier New",monospace;font-size:.82em;color:#222;line-height:1; }
++.anchor-icon { color:#E8E8E8;text-decoration:none;opacity:0;transition:opacity .15s;vertical-align:middle;margin-left:4px;display:inline-flex;align-items:center; }
++h2:hover .anchor-icon,h3:hover .anchor-icon { opacity:1; }
++.anchor-icon:hover { color:#005AB4; }
++.note { border-radius:6px;padding:12px 16px;margin:14px 0;border:1px solid transparent; }
++.note-info    { background:#e1f1f9 !important;border-color:#b3d4ee !important;border-left:4px solid #005AB4 !important; }
++.note-warning { background:#fff4ec !important;border-color:#f5cba7 !important;border-left:4px solid #DD5600 !important; }
++.note-tip     { background:#e5f3df !important;border-color:#b7dba5 !important;border-left:4px solid #73A839 !important; }
++.note-hd { font-weight:700;font-size:.85em;display:flex;align-items:center;gap:5px;margin-bottom:5px; }
++.note-info    .note-hd { color:#003d80 !important; }
++.note-warning .note-hd { color:#a03d00 !important; }
++.note-tip     .note-hd { color:#3d6b1a !important; }
++.note-body { font-size:.875em;color:#222 !important;line-height:1.65; }
++.section-index { list-style:disc;padding-left:20px;margin:0 0 20px 0; }
++.section-index li { margin-bottom:12px; }
++.section-index li a { color:#005AB4;font-weight:600;font-size:.93em;text-decoration:underline; }
++.section-index li p { margin:3px 0 0 0;font-size:.875em;color:#333;line-height:1.6; }
++.parent-topic { font-size:.82em;color:#555;margin:18px 0 24px 0;border-top:1px solid #E8E8E8;padding-top:10px; }
++.parent-topic a { color:#005AB4; }
++img.inline-icon { display:inline-block;height:28px;width:auto;vertical-align:middle;border:1px solid #E8E8E8;border-radius:4px;margin:0 3px;box-shadow:0 1px 2px rgba(0,0,0,.08); }
++img.inline-icon-sm { display:inline-block;height:20px;width:auto;vertical-align:middle;border:1px solid #E8E8E8;border-radius:3px;margin:0 3px;box-shadow:0 1px 2px rgba(0,0,0,.08); }
++.fig { margin:12px auto 24px auto;width:fit-content;max-width:100%; }
++.fig img { border-radius:4px 4px 0 0;border:1px solid #E8E8E8;display:block;cursor:zoom-in;max-width:100%;box-shadow:0 1px 4px rgba(0,0,0,.10);transition:box-shadow .15s; }
++.fig img:hover { box-shadow:0 3px 12px rgba(0,90,180,.18); }
++.fig-cap { font-size:.78em;color:#555;margin:0;padding:5px 8px;background:#f5f5f5;border:1px solid #E8E8E8;border-top:none;border-radius:0 0 4px 4px;display:block;width:100%;box-sizing:border-box; }
++#rn-lb { display:none;position:fixed;inset:0;z-index:9998;background:rgba(0,0,0,.8);cursor:zoom-out;align-items:center;justify-content:center; }
++#rn-lb.open { display:flex; }
++#rn-lb-wrap { position:relative;cursor:default;max-width:92vw;max-height:90vh; }
++#rn-lb-wrap img { max-width:100%;max-height:90vh;border-radius:5px;display:block; }
++#rn-lb-x { position:absolute;top:-13px;right:-13px;background:#005AB4;color:#fff;width:26px;height:26px;border-radius:50%;border:none;cursor:pointer;font-size:15px;display:flex;align-items:center;justify-content:center; }
++#rn-lb-cap { position:fixed;bottom:18px;left:50%;transform:translateX(-50%);color:#ddd;font-size:.78em;background:rgba(0,0,0,.55);padding:3px 12px;border-radius:14px;pointer-events:none; }
++#rn-top { position:fixed;bottom:60px;right:60px;z-index:9997;width:36px;height:36px;border-radius:50%;background:#005AB4;color:#fff;border:none;cursor:pointer;display:flex;align-items:center;justify-content:center;opacity:0;transform:translateY(8px);transition:opacity .22s,transform .22s;pointer-events:none;box-shadow:0 2px 8px rgba(0,90,180,.3); }
++#rn-top.on { opacity:1;transform:translateY(0);pointer-events:auto; }
++#rn-top:hover { background:#0066cc; }
++.rn-toast { position:fixed;bottom:66px;right:24px;z-index:9999;background:#222;color:#fff;font-size:.74em;padding:4px 11px;border-radius:4px;pointer-events:none;opacity:0;transition:opacity .18s; }
++.rn-toast.on { opacity:1; }
++.rn-table { width:100%;border-collapse:collapse;margin:8px 0 18px 0;font-size:.82em; }
++.rn-table th { background:#f5f5f5;text-align:left;padding:7px 10px;font-size:.78em;font-weight:700;text-transform:uppercase;letter-spacing:.04em;color:#555;border-bottom:2px solid #E8E8E8; }
++.rn-table td { padding:7px 10px;border-bottom:1px solid #E8E8E8;color:#333;vertical-align:top;line-height:1.6; }
++.rn-table tr:last-child td { border-bottom:none; }
++.rn-table tr:hover td { background:#f5f5f5; }
++.rn-table code { background:#f0f0f0;border:1px solid #ddd;border-radius:3px;padding:1px 4px;font-size:.88em;font-family:Menlo,Monaco,Consolas,monospace; }
++.tbl-wrap { overflow-x:auto;margin:8px 0 18px 0; }
++.var-badge { display:inline-block;font-family:Menlo,Monaco,Consolas,monospace;font-size:.8em;background:#deeaf7;color:#005AB4;border:1px solid #b3d4ee;border-radius:3px;padding:1px 6px; }
++</style>
--{{toc/}}
++<div id="rn-prog"></div>
++<div id="rn-lb">
++  <div id="rn-lb-wrap">
++    <button id="rn-lb-x" onclick="closeLightbox()">&#10005;</button>
++    <img id="rn-lb-img" src="" alt=""/>
++  </div>
++  <div id="rn-lb-cap"></div>
++</div>
++<button id="rn-top" onclick="window.scrollTo({top:0,behavior:'smooth'})" title="Back to top">
++  <svg width="14" height="14" viewBox="0 0 16 16" fill="currentColor"><path d="M8 4l5 5H3z"/></svg>
++</button>
++<div class="rn-toast" id="rn-toast">Link copied &#10003;</div>
--= 1. INTRODUCTION =
++<div class="doc-wrap">
++<div class="doc-content">
--CENTO is a multifunctional software platform for data collection, processing and display. This Manual describes the user tool in CENTO "Events".
++  <ul class="section-index">
++    <li><a href="#s-intro">1. Introduction</a>
++      <p>Overview of the Events tool — purpose, capabilities, and key concepts.</p></li>
++    <li><a href="#s-events">2. CENTO Events</a>
++      <p>Event editor, creating and editing events via UI or Excel, and flashing on diagrams.</p></li>
++    <li><a href="#s-notifications">3. Notifications Settings</a>
++      <p>Configuring email notifications, filter logic, and notification delivery examples.</p></li>
++    <li><a href="#s-sound-editor">4. Sound Editor</a>
++      <p>Uploading and managing .mp3 sound files for event alerts.</p></li>
++    <li><a href="#s-examples">5. Examples of Event Setup</a>
++      <p>Practical examples: events on tag value change and device status change.</p></li>
++    <li><a href="#s-annex">Appendix: Formula Reference</a>
++      <p>Variables and operators available in event condition formulas.</p></li>
++  </ul>
--It is assumed that the user is already familiar with the basic elements of the CENTO interface after reading the "User Manual" instructions.
--"Events" in CENTO are designed to increase the observability of system operation by tracking changes in the system status and process equipment, logging events, and notifying users. Events help the personnel to timely react to changes in the technological process and system operation. To achieve these goals, CENTO offers user notification and acknowledgement features alongside event logging.
++  <h2 id="s-intro">1. Introduction<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-intro')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>
--= 2. CENTO EVENTS =
++  <p>CENTO is a multifunctional software platform for data collection, processing, and display. This manual describes the <strong>Events</strong> user tool in CENTO.</p>
--== 2.1. Event editor ==
++  <p>It is assumed that the user is already familiar with the basic elements of the CENTO interface after reading the User Manual.</p>
--To go to the **Event editor**, select the item in the main menu:
++  <p>Events in CENTO are designed to increase the observability of system operation by tracking changes in the system status and process equipment, logging events, and notifying users. Events help personnel react in a timely manner to changes in the technological process and system operation. To achieve these goals, CENTO provides user notification and acknowledgement features alongside event logging.</p>
--Settings > Events > Event editor.
++  <h2 id="s-events">2. CENTO Events<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-events')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>
--[[image:Screenshot 2025-12-10 at 21.28.44.png||height="318" width="274"]]
++  <h3 id="s-event-editor">2.1. Event editor<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-event-editor')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>
--Fig. 2.1 - Event editor in the CENTO menu
++  <p>To open the <strong>Event editor</strong>, select from the main menu: <strong>Settings &rarr; Events &rarr; Event editor</strong>.</p>
--Figure 2.2. shows the interface of the **Event editor.**
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.28.44.png" alt="Event editor in the CENTO menu" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.1. Event editor in the CENTO menu</p>
++  </div>
--[[image:Screenshot 2025-12-10 at 21.29.15.png||height="483" width="1424"]]
++  <p>Figure 2.2 shows the <strong>Event editor</strong> interface.</p>
--Fig. 2.2 - Event editor
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.29.15.png" alt="Event editor" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.2. Event editor</p>
++  </div>
--The **Event editor** page provides the option to:
++  <p>The <strong>Event editor</strong> page provides the following capabilities:</p>
++  <ol>
++    <li>Add a new event to the system <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.29.51.png" alt="Add event"/></li>
++    <li>Activate <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.30.26.png" alt="Activate"/> or disable <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.30.54.png" alt="Disable"/> selected events</li>
++    <li>Edit <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.32.53.png" alt="Edit"/>, copy <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.33.40.png" alt="Copy"/>, and delete <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.34.05.png" alt="Delete"/> in the <strong>Actions</strong> column</li>
++    <li>Delete any number of events at once <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.35.15.png" alt="Delete selected"/></li>
++    <li>Edit the number of records displayed</li>
++    <li>Search for events by filtering <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.36.03.png" alt="Filter"/> (the filter is located to the right of the table headings)</li>
++    <li>Edit event configuration <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.36.56.png" alt="Edit configuration"/></li>
++    <li>Adjust setpoint text <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.37.32.png" alt="Adjust setpoint text"/></li>
++  </ol>
--1. Add a new event to the system [[image:Screenshot 2025-12-10 at 21.29.51.png||height="21" width="74"]]
--1. Activate [[image:Screenshot 2025-12-10 at 21.30.26.png||height="20" width="108"]] or disable [[image:Screenshot 2025-12-10 at 21.30.54.png||height="20" width="103"]] selected events
--1. (((
--Edit [[image:Screenshot 2025-12-10 at 21.32.53.png||height="25" width="24"]], copy [[image:Screenshot 2025-12-10 at 21.33.40.png||height="26" width="26"]], and delete [[image:Screenshot 2025-12-10 at 21.34.05.png||height="27" width="27"]]in the "Actions" column
--)))
--1. (((
--Delete any number of events [[image:Screenshot 2025-12-10 at 21.35.15.png||height="22" width="125"]]
--)))
--1. (((
--Edit the number of records to be displayed
--)))
--1. (((
--Search for events of interest by filtering [[image:Screenshot 2025-12-10 at 21.36.03.png||height="32" width="33"]] (the filter is located to the right of the table headings)
--)))
--1. (((
--Edit event configuration [[image:Screenshot 2025-12-10 at 21.36.56.png||height="22" width="86"]]
--)))
--1. (((
--Adjust the setpoint text [[image:Screenshot 2025-12-10 at 21.37.32.png||height="20" width="108"]]
--)))
--== 2.2. Creating and editing an event in web-interface ==
++  <h3 id="s-event-create">2.2. Creating and editing an event in the web interface<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-event-create')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>
++  <p>An event can be created manually or automatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the Setup Manual.</p>
--An event can be created manually and automatically. Events are automatically created when the setpoint parameter is enabled. For a detailed description, refer to the "Setup Manual".
++  <p>The text of setpoints can be edited in the <strong>Event editor</strong> interface. Click the button <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.38.47.png" alt="Adjust setpoint text"/>. The <strong>Setpoint editing</strong> window opens (Figure 2.3), where the wording of setpoints for Triggering and/or Return can be modified, including Upper/Lower warning limit, Upper/Lower alarm limit, and Upper/Lower physical limit.</p>
--The text of setpoints can be edited in the **Event editor** interface.
++  <p>One or more variables can be specified in the setpoint triggering message:</p>
++  <ul>
++    <li><code>{{.tag_name}}</code> &mdash; tag name</li>
++    <li><code>{{.tag_code}}</code> &mdash; tag code</li>
++    <li><code>{{.tag_id}}</code> &mdash; tag ID</li>
++    <li><code>{{.tag_code_or_id}}</code> &mdash; tag code, or ID if the code is empty</li>
++    <li><code>{{.tag_limit}}</code> &mdash; setpoint value</li>
++    <li><code>{{.tag_unit}}</code> &mdash; tag units</li>
++    <li><code>{{.device_name}}</code> &mdash; name of the device the tag is linked to</li>
++  </ul>
--To do this, click on the button [[image:Screenshot 2025-12-10 at 21.38.47.png||height="22" width="119"]]. After that, the **Setpoint editing** window opens (see Fig. 2.3), where the wording of the setpoints for Triggering and/or Return can be modified, such as Upper/Lower warning limit, Upper/Lower alarm limit, and Upper/Lower physical limit.
--One or more variables can be specified in the setpoint triggering message:
++  <div class="note note-warning"><div class="note-hd"><span>&#9888;</span> Important</div><div class="note-body">If curly braces or dots are missing when writing these parameters, a validation error will occur. If a non-existent parameter is entered (e.g. <code>{{.tag_name_2}}</code>), the Operating Journal will receive an event of the form: <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.39.52.png" alt="error icon"/> <strong>&lt;no value&gt; &gt; 10</strong>.</div></div>
--* ~{~{.tag_name}} - tag name;
--* ~{~{.tag_code}} - tag code;
--* ~{~{.tag_id}} - tag ID;
--* ~{~{.tag_code_or_id}} - tag code, if the code is empty, then its ID;
--* ~{~{.tag_limit}} - setpoint value;
--* ~{~{.tag_unit}} - tag units;
--* ~{~{.device_name}} - name of the device to which the tag is linked.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.40.35.png" alt="Setpoint editing page" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.3. Setpoint editing page</p>
++  </div>
--IMPORTANT: if {figure brackets} or dots are missing when writing these parameters, a validation error will occur.
++  <p>To create a new event, click the button <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.41.09.png" alt="Add new event"/>. Only an authorized user with appropriate rights can create and edit events.</p>
--If a parameter with an error (non-existent parameter) is entered, for example: ~{~{.tag_name_2}}, the Operating journal will receive an event of the following type: [[image:Screenshot 2025-12-10 at 21.39.52.png||height="18" width="18"]] **< no value> > 10**.
++  <p>Figure 2.4 shows the event creation page.</p>
--[[image:Screenshot 2025-12-10 at 21.40.35.png||height="788" width="874"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.41.54.png" alt="Event editor: creation page" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.4. Event editor: creation page</p>
++  </div>
--Fig. 2.3 - Setpoint editing page
++  <p>The <strong>Event editor</strong> window contains the following fields:</p>
++  <ul>
++    <li><strong>Identifier</strong> &mdash; the sequence number of the event (filled in automatically); can be changed if needed.</li>
++    <li><strong>Name</strong> &mdash; the name of the event.</li>
++    <li><strong>Object</strong> &mdash; an object from the CENTO Information Model (IM) to which the event refers. The IM object is selected from a drop-down tree.</li>
++    <li><strong>Device</strong> &mdash; the device to which the event refers, selected from the drop-down device tree.</li>
++    <li><strong>Event type</strong> &mdash; switches the event type between &ldquo;Single&rdquo; and &ldquo;With return&rdquo; <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.42.53.png" alt="Event type switch"/>.</li>
++    <li><strong>Tags</strong> &mdash; the ID of the telemetering tag to which the event belongs.</li>
++    <li><strong>Message</strong> &mdash; the message text output when the event is triggered.</li>
++    <li><strong>Formula</strong> &mdash; the condition for the event to be triggered. Click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.43.51.png" alt="Formula list"/> to open the list of available formulas (see Appendix).</li>
++    <li><strong>Dead time (ms)</strong> &mdash; delay time in milliseconds before the event is generated. Helps prevent false events caused by intermittent communication failures.</li>
++    <li><strong>Type</strong> &mdash; a drop-down list for the importance or category of the event.</li>
++    <li><strong>Acknowledgement</strong> &mdash; a switch to enable user acknowledgement of event notification.</li>
++    <li><strong>Sound</strong> &mdash; selects a sound for notification from those loaded in the Sound Editor (see section 4). The selected sound can be previewed using the button <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.44.31.png" alt="Play sound"/> to the right of the &ldquo;Sound&rdquo; field.</li>
++    <li><strong>Before acknowledgement</strong> &mdash; a switch to play the selected sound until the event is acknowledged.</li>
++    <li><strong>Sound repeats</strong> &mdash; number of repetitions of sound playback when the event occurs.</li>
++  </ul>
--To create a new event, click on the button [[image:Screenshot 2025-12-10 at 21.41.09.png||height="24" width="96"]].
--Only an authorized user with appropriate rights can create and edit events.
++  <div class="note note-warning"><div class="note-hd"><span>&#9888;</span> Important</div><div class="note-body"><strong>Modern browsers block sound playback by default.</strong> To allow CENTO to play sounds in Chrome:<ol style='margin:6px 0 0 0;padding-left:18px;'><li>Left-click to the left of the address bar (Figure 2.5) and select <strong>Site settings</strong>.</li><li>Go to <strong>Privacy and security &rarr; Site settings &rarr; Additional permissions &rarr; Sound</strong> and select <strong>Allow</strong> (Figure 2.6).</li><li>Refresh the CENTO page.</li></ol></div></div>
--Fig. 2.4. shows the page for creating a new event.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.45.18.png" alt="Site settings — opening permissions" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.5. Site settings — opening permissions</p>
++  </div>
--[[image:Screenshot 2025-12-10 at 21.41.54.png||height="606" width="1425"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.48.19.png" alt="Allowing sound playback for the site" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.6. Allowing sound playback for the site</p>
++  </div>
--Fig. Event editor: creation page
++  <p>After filling in all required fields, click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.48.55.png" alt="Save"/> and update the configuration (Figure 2.7).</p>
--The** Event editor** window contains the following fields:
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.49.27.png" alt="Update configuration" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.7. Update configuration</p>
++  </div>
--**Identifier **contains the sequence number of the event (filled in automatically), can be changed if necessary.
++  <div class="note note-info"><div class="note-hd"><span>&#8505;</span> Note</div><div class="note-body">There are two event types in CENTO: <strong>Single</strong> and <strong>With return</strong>. Events with return are used for important persistent states (e.g. &ldquo;Ground fault in isolated-neutral network&rdquo;). The <em>opening event</em> reports the state start; the <em>closing event</em> reports its end. <strong>Events with return must always be paired</strong> &mdash; the second event always closes the first. Active (unclosed) events are shown in a separate tab of the operational log.</div></div>
--**Name **is a field for entering the name of the event.
++  <p>When <strong>With return</strong> is selected as the event type, the Event editor displays additional fields with the heading <strong>With return</strong> (Figure 2.8). These fields are identical to those for the Single event type.</p>
--**Object **field is used to add an object from the CENTO Information Model (IM), to which the event refers (see "Information Model Setup Manual"). The IM object is selected from the IM drop-down tree.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.49.59.png" alt="Event editor with &ldquo;With return&rdquo; type" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.8. Event editor with &ldquo;With return&rdquo; type</p>
++  </div>
--**Device **is** **the device to which the event refers is added in this field. The device is selected from the drop-down device tree.
++  <h3 id="s-event-excel">2.3. Creating and editing events using Excel<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-event-excel')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>
--**Event type **switches the event type between "Single" and "With return" [[image:Screenshot 2025-12-10 at 21.42.53.png||height="27" width="135"]].
++  <p>Events can be configured using Excel files. This function is available at <strong>Settings &rarr; Configuration Files</strong> (Figure 2.9).</p>
--There are two types of events in CENTO – single and with return events. For system objects, there may be important state that the user should see in the active status (e.g., "Ground in a network with isolated neutral", "Switching on a sectionalizer", "Opening the emergency exit door"). Events reporting this important state are opening events. Events reporting the end of an important object state are closing events. These two types of events are events with return. **Events with return should ALWAYS be paired: the second event ALWAYS closes the first one. **Events in the active state are displayed in a separate tab of the operational log and disappear from there after triggering the closing event. Other events (regardless of their importance) are single events.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.51.04.png" alt="Import/Export configuration file page" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.9. Import/Export configuration file page</p>
++  </div>
--**Tags **field requires to specify the ID of the telemetering tag to which the event belongs;
++  <p>To configure events, download the <code>events.xlsx</code> file by clicking <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.51.37.png" alt="Download"/>, then fill in the appropriate cells in a new row in the <strong>Events</strong> tab (Figure 2.10).</p>
--**Message **is the message text that should be output when the event is triggered;
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.52.08.png" alt="Events tab in events.xlsx" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.10. Events tab in events.xlsx</p>
++  </div>
--**Formula **field is used to enter a formula that describes the condition for the event to be triggered. Clicking on [[image:Screenshot 2025-12-10 at 21.43.51.png||height="28" width="163"]] will open the list of formulas for forming the event. Description of formulas is given in the Appendix.
++  <p>Fill in the following columns to create an event:</p>
++  <ul>
++    <li><strong>Event ID</strong> &mdash; unique event number. Must not duplicate existing IDs in the system.</li>
++    <li><strong>Name</strong> &mdash; event name.</li>
++    <li><strong>Event type</strong> &mdash; <code>one_position</code> or <code>two_position</code>.</li>
++    <li><strong>Event status</strong> &mdash; <code>1</code> = enabled, <code>0</code> = disabled.</li>
++    <li><strong>Device ID</strong> &mdash; device identifier the event refers to.</li>
++    <li><strong>Device</strong> &mdash; auto-generated when downloading; shows the device path for debugging. Do not fill in manually.</li>
++    <li><strong>Object ID</strong> &mdash; IM object identifier the event refers to.</li>
++    <li><strong>Object</strong> &mdash; auto-generated when downloading; shows the object path for debugging. Do not fill in manually.</li>
++    <li><strong>Tags</strong> &mdash; tag (parameter) ID the event refers to.</li>
++    <li><strong>Formula</strong> &mdash; condition for triggering the event (see Appendix).</li>
++    <li><strong>Dead time, ms</strong> &mdash; delay time in milliseconds before event generation.</li>
++    <li><strong>Event type code</strong> &mdash; code from the <strong>Event type</strong> directory in the separate tab of this file.</li>
++    <li><strong>Event type name</strong> &mdash; filled in automatically when uploading/downloading.</li>
++    <li><strong>Message</strong> &mdash; message text displayed in logs when the event is triggered.</li>
++    <li><strong>Acknowledgement</strong> &mdash; <code>True</code> = enabled, <code>False</code> = disabled.</li>
++    <li><strong>Sound ID</strong> &mdash; ID of a sound file loaded through the Sound Editor.</li>
++    <li><strong>Sound name</strong> &mdash; filled in automatically when uploading/downloading.</li>
++    <li><strong>Repeat count</strong> &mdash; number of sound repetitions when the event is triggered.</li>
++    <li><strong>Infinity repeat</strong> &mdash; <code>True</code> = repeat until acknowledged, <code>False</code> = use repeat count.</li>
++  </ul>
--**Dead time, (ms)** field specifies the delay time for the event to be generated in milliseconds. It helps prevent false events, such as those caused by frequent device polling failures due to poor communication.
--**Type** is** **a drop-down list used to specify the importance or category of the event.
++  <p>After filling in all required fields, upload the file using the <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.53.38.png" alt="Upload"/> button on the Import/Export configuration file page (Figure 2.9). In the dialog (Figure 2.11), select the filled-in <code>events.xlsx</code>. The system will automatically validate the file (Figure 2.12).</p>
--**Acknowledgement **is a switch to activate the function of user acknowledgement of event notification;
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.54.07.png" alt="Upload configuration file window" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.11. Upload configuration file window</p>
++  </div>
--**Sound **field is used to select a sound for notification. The drop-down list contains those sounds that are loaded through the Sound Editor (see item 3). The selected sound can be listened to using the button [[image:Screenshot 2025-12-10 at 21.44.31.png||height="24" width="27"]] to the right of the "Sound" field.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.54.41.png" alt="Validating the configuration file" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.12. Validating the configuration file</p>
++  </div>
--**Before acknowledgement** is a switch to play the selected sound before the event is acknowledged;
++  <p>If errors are detected, they will be displayed in the upload window. After all errors are corrected, the <strong>Write configuration</strong> button becomes available. After uploading, refresh the configuration to apply changes (see Figure 2.7).</p>
--**Sound repeats **field is used to set the number of repetitions of sound playback when the event occurs.
++  <div class="note note-info"><div class="note-hd"><span>&#8505;</span> Note</div><div class="note-body">For <strong>partial editing</strong>, CENTO also allows downloading and uploading only a filtered subset of events. In the Event editor, filter for the events of interest using <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.55.29.png" alt="Filter"/>, then click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.55.55.png" alt="Config"/> and select <strong>Download</strong>. The downloaded <code>events.xlsx</code> will contain only the filtered events. To upload changes, click the same button and select <strong>Upload</strong>. Events not included in the download will remain unchanged.</div></div>
--**Warning! **Modern browsers block playback of sounds in a browser by default, so sound alerts may not be played. To allow CENTO to play sounds in the browser, follow the steps below (an example is given for Chrome):
++  <div class="note note-warning"><div class="note-hd"><span>&#9888;</span> Important</div><div class="note-body">Partial upload/download is <strong>not compatible</strong> with Excel files downloaded using an earlier version of the service. Attempting to upload an old file will result in a &ldquo;Version incompatibility&rdquo; error. When adding a new event, the new Event ID must not match any existing ID in the system.</div></div>
--~1. Left click to the left of the address bar (see Fig. 2.5).
++  <h3 id="s-event-flash">2.4. Flashing on the diagram<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-event-flash')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>
--2. Select "Site settings".
++  <p>An object on a mimic diagram can be configured to flash (blink) when an event is active. There are two methods:</p>
--[[image:Screenshot 2025-12-10 at 21.45.18.png||height="350" width="366"]]
++  <h4>Method 1: Flashing by tag</h4>
--Fig. 2.5 - Site settings
++  <p>Use this method if the information model is not configured or not planned. Steps:</p>
++  <ol>
++    <li>
++      <strong>Set up an event</strong> with the triggering formula, for example, connection loss
++      (<code>ti40027171 != 1</code>) or restoration (<code>ti40027171 == 1</code>) — any tag
++      registered in the system can be used (Figure 2.13).
++    </li>
++    <li>
++      <strong>Create a calculated tag</strong> with the formula <code>[devstatusNN]</code> where
++      NN is the device ID (Figure 2.14). The tag to be used for the designated purpose may get
++      its value from a real device or may be based on other tags.
++    </li>
++    <li>
++      <strong>Set up an object on the diagram</strong>, referencing the calculated tag from step 2
++      in its rules (Figure 2.15).
++    </li>
++    <li>
++      After saving the diagram and updating the configuration, if the status of the NN device
++      changes, the system will start flashing the bound diagram object until it is acknowledged.
++    </li>
++  </ol>
--3. In the opened window, go to Privacy and security → Site settings → Additional permissions → Content → Additional content settings → Sound, and select Allow (see Fig. 2.6).
--[[image:Screenshot 2025-12-10 at 21.48.19.png||height="264" width="1104"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.58.43.png" alt="Event configured for tag-based flashing" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.13. Event configured for tag-based flashing</p>
++  </div>
--Fig. 2.6 - Allow sound
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.59.17.png" alt="Calculated tag for diagram flashing" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.14. Calculated tag for diagram flashing</p>
++  </div>
--4. Refresh the CENTO page.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2021.59.53.png" alt="Diagram object rules referencing the calculated tag" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.15. Diagram object rules referencing the calculated tag</p>
++  </div>
--After filling in all the required fields, click [[image:Screenshot 2025-12-10 at 21.48.55.png||height="25" width="70"]] and update the configuration (see Fig. 2.7).
++  <h4>Method 2: Flashing by information model object</h4>
--[[image:Screenshot 2025-12-10 at 21.49.27.png||height="338" width="340"]]
++  <p>For this method, the information model must be configured and the required IM object must be selected in the event's <strong>Object</strong> field. The diagram object must be <em>active</em> (see the Diagrams Development Manual) and bound to the same IM object. Steps:</p>
++  <ol>
++    <li><strong>Create an event</strong> with the IM object selected in the <strong>Object</strong> field (Figure 2.16).</li>
++    <li><strong>Create an active diagram object</strong> bound to the same IM object (Figure 2.17).</li>
++  </ol>
--Fig. 2.7 - Update  configuration
--If selecting **With return** in the Event type, the **Event editor** window displays additional fields with the general heading **With return** (see Fig. 2.8). These fields are the same as those used for the **Single** event type.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.01.01.png" alt="Creating an event with an information model object" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.16. Creating an event with an information model object</p>
++  </div>
--[[image:Screenshot 2025-12-10 at 21.49.59.png||height="600" width="1390"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.02.05.png" alt="Diagram object bound to the information model" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 2.17. Diagram object bound to the information model</p>
++  </div>
--Fig. 2.8 -  With return event editor window
++  <h2 id="s-notifications">3. Notifications Settings<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-notifications')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>
--== 2.3. Creating and editing events using Excel ==
++  <h3 id="s-notif-create">3.1. Creating and editing notifications<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-notif-create')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>
--Events can be configured using Excel files. This function is available on the page /CENTO/web/ui/configuration_loader/index (Settings > Configuration Files) (see Fig. 2.9).
++  <p>CENTO can notify users about triggered events via email. To configure notifications, go to <strong>Settings &rarr; Events &rarr; Notifications</strong>. Mail server configuration is described in the Setup Manual, Mail Servers.</p>
--[[image:Screenshot 2025-12-10 at 21.51.04.png||height="474" width="1388"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.03.45.png" alt="Notifications interface" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.1. Notifications interface</p>
++  </div>
--Fig. 2.9 - Import/Export configuration file page
++  <p>The notification table contains the following columns:</p>
++  <ol>
++    <li><strong>Name</strong> &mdash; notification name.</li>
++    <li><strong>Emails</strong> &mdash; email addresses configured to receive notifications.</li>
++    <li><strong>Dispatch period</strong> &mdash; the time of day allowed for sending notifications.</li>
++    <li><strong>Iteration period</strong> &mdash; minimum time interval between notifications (notifications cannot be sent more frequently than this period).</li>
++    <li><strong>Operation threshold</strong> &mdash; number of event triggers required before a notification is sent.</li>
++    <li><strong>State</strong> &mdash; on/off.</li>
++    <li><strong>Actions</strong> &mdash; edit <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.05.05.png" alt="Edit"/>, copy <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.05.32.png" alt="Copy"/>, delete <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.05.55.png" alt="Delete"/>.</li>
++  </ol>
--To configure events, download the events.xlsx file by clicking the button [[image:Screenshot 2025-12-10 at 21.51.37.png||height="28" width="97"]], then fill in the appropriate cells in the new line of the table in the **Events** tab (see Fig. 2.10).
--[[image:Screenshot 2025-12-10 at 21.52.08.png||height="565" width="1397"]]
++  <p>To create a new notification, click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.06.27.png" alt="Create notification"/>. Only an authorized user with appropriate permissions can create and edit notifications.</p>
--Fig. 2.10 - Events tab in the events.xslx file
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.07.01.png" alt="Notifications: creation page" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.2. Notifications: creation page</p>
++  </div>
--To create an event, fill in the following columns:
++  <p>Fill in the following fields in the <strong>Notification settings</strong> tab:</p>
++  <ul>
++    <li><strong>Name</strong> &mdash; notification name.</li>
++    <li><strong>State</strong> &mdash; enables or disables the notification.</li>
++    <li><strong>Operation threshold</strong> &mdash; number of event triggers required before a notification is sent.</li>
++    <li><strong>Dispatch period</strong> &mdash; the time of day allowed for sending notifications.</li>
++    <li><strong>Iteration period</strong> &mdash; minimum time interval between notifications.</li>
++    <li><strong>Delay (s)</strong> &mdash; accumulation window starting from the first event before the notification is sent.</li>
++    <li><strong>E-mail server</strong> &mdash; mail server for sending notifications (configured in Settings &rarr; Email servers).</li>
++    <li><strong>Recipients</strong> &mdash; email addresses of notification recipients.</li>
++  </ul>
--**Event ID **is an event unique number.
--**Name **is the name of the event.
++  <p>In the <strong>Event selection</strong> tab (Figure 3.3), tick the events required for notification in the left column and click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.08.29.png" alt="Move right"/> to move them to the right column. To remove events, mark them in the right column and click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.08.55.png" alt="Move left"/>.</p>
--**Event type **is one_position or two_position event.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.07.55.png" alt="Event selection tab" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.3. Event selection tab</p>
++  </div>
--**Event status **is responsible for the event status: 1 - event is enabled, 0 - event is disabled.
++  <p>After filling in all fields, click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.09.48.png" alt="Save"/> and update the configuration.</p>
--**Device ID **is a device identifier to which the event refers.
++  <h3 id="s-notif-logic">3.2. Notification operation<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-notif-logic')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h3>
--**The device** is not required to be filled in, it is generated when downloading an Excel file to help with debugging (displays the path of the linked device).
++  <p>There are three filter types that control when notifications are sent:</p>
++  <ol>
++    <li><strong>Operation threshold</strong></li>
++    <li><strong>Iteration period</strong></li>
++    <li><strong>Dispatch period</strong></li>
++  </ol>
--**Object ID **is an IM object identifier to which the event refers.
--**Object** does not need to be filled in, it is generated when downloading an Excel file to help in debugging (displays the path of the linked object).
++  <p>When configured without any restrictions, a notification is sent whenever any of the configured events is triggered.</p>
--**Tags **is a tag (parameter) Identifier to which the event refers.
++  <h4>Operation threshold</h4>
--**Formula** defines the condition under which the event is to be triggered. Description of formulas is given in the Appendix.
++  <p>A notification is triggered when the total number of triggered events in the notification reaches the configured threshold. If the threshold is 0, the notification is generated immediately after any event triggers, provided the other filters allow it.</p>
--**Dead time, ms **is a field to enter the delay time, in milliseconds, for the event to be triggered.
++  <h4>Iteration period</h4>
--**Event type code **is a code, which is entered according to the **Event type** directory using a separate tab in this file.
++  <p>The iteration period starts from the time the last notification was triggered. It is set in days and hours. If set to 0 days 0 hours, notifications are generated and sent immediately when the other filter conditions are met.</p>
--**Event type name **is a name of the event type, the field is filled in automatically when uploading-downloading the configuration file.
++  <h4>Dispatch period</h4>
--**Message **is a message text that should be displayed in the logs when the event is triggered.
++  <p>If set to 0:00&ndash;24:00, notifications can be sent at any time of day. If set to a specific time (e.g. 8:00), notifications are batched and sent once at that time. The dispatch period can only be set within a single calendar day.</p>
--**Acknowledgement **is responsible for the event acknowledgement. True - acknowledgement is enabled, False - acknowledgement is disabled.
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.11.07.png" alt="Logic of filter settings when generating notifications" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.4. Logic of filter settings when generating notifications</p>
++  </div>
--**Sound ID **specifies an ID of a sound file loaded through the sound editor.
++  <h4>Changing notification settings</h4>
--**Sound name **is a name of the sound file, the field is filled in automatically when loading-unloading the configuration file.
++  <p>When notification settings are changed at any time:</p>
++  <ul>
++    <li>The <strong>operation threshold counter</strong> is preserved but the notification will not trigger until the next event after the threshold is reached.</li>
++    <li>The <strong>iteration period</strong> is reset.</li>
++  </ul>
--**Repeat count **is used to set the number of repetitions of sound playback when the event is triggered.
--**Infinity repeat **is responsible for repeating the sound until the user acknowledges the event. True - infinite repetition is enabled, False - infinite repetition is disabled.
++  <p>Examples:</p>
++  <ol>
++    <li>Threshold = 5, 3 events triggered. User increases threshold to 10 &rarr; notification fires after 7 more events (total 10).</li>
++    <li>Threshold = 10, 7 events triggered. User reduces threshold to 5 &rarr; notification fires after the next event (total 8 triggered events).</li>
++    <li>Iteration period = 10 hours, last notification sent 2 hours ago. Settings changed &rarr; iteration period resets and notification fires on the next event trigger.</li>
++    <li>Threshold = 10, notification has 3 events, event #1 triggered twice. User deletes event #1 from notification. When total reaches 10, notification is sent without event #1&rsquo;s messages.</li>
++  </ol>
--After all required fields are filled in, the file should be uploaded using the button [[image:Screenshot 2025-12-10 at 21.53.38.png||height="22" width="77"]] on the **Import/Export configuration file** page (see Fig. 2.9). In the window that appears (see Fig. 2.11), select the filled in events.xlsx file. The system will automatically validate the file to ensure it is correctly filled in and formatted (see Fig. 2.12).
--[[image:Screenshot 2025-12-10 at 21.54.07.png||height="234" width="379"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.12.07.png" alt="Notification with operation threshold" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.5. Notification with operation threshold</p>
++  </div>
--Fig. 2.11 - Upload configuration file window
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.12.39.png" alt="Notification with dispatch period" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.6. Notification with dispatch period</p>
++  </div>
--[[image:Screenshot 2025-12-10 at 21.54.41.png||height="413" width="477"]]
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.13.08.png" alt="Notification with all restrictions active" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 3.7. Notification with all restrictions active</p>
++  </div>
--Fig. 2.12 - Validating the configuration file
++  <h2 id="s-sound-editor">4. Sound Editor<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-sound-editor')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>
--If errors are detected, they will be displayed in the file upload window. After all errors are eliminated, the **Write configuration** button will become available.
++  <p>Sound notifications are managed at <strong>Settings &rarr; Events &rarr; Sound editor</strong>.</p>
--After uploading the file, the configuration should be refreshed to apply the changes (see Fig. 2.7).
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.13.46.png" alt="Sound Editor page" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 4.1. Sound Editor page</p>
++  </div>
--To make working with events more convenient, CENTO provides the option to edit the event configuration partially using Excel.
++  <p>The Sound Editor shows a table with the following columns: <strong>ID</strong>, <strong>Name</strong>, <strong>File name</strong>, <strong>Uploaded</strong> (date), and <strong>Actions</strong> (edit, play, delete).</p>
--To do this, on the page /CENTO/web/ui/event_editor/index (menu item Settings > Events > Event editor (see Fig. 2.1 - Fig. 2.2), search for an events using the filtering [[image:Screenshot 2025-12-10 at 21.55.29.png||height="24" width="25"]], then click on the button [[image:Screenshot 2025-12-10 at 21.55.55.png||height="25" width="95"]]and select **Download** in the drop-down list. After that, the file events.xlsx will be downloaded to the PC, containing only the filtered events from the **Events editor**.
++  <div class="note note-info"><div class="note-hd"><span>&#8505;</span> Note</div><div class="note-body">The Sound Editor only supports <strong>.mp3</strong> files.</div></div>
--Actions when filling/editing the columns of the Excel table are similar to the actions during uploading from the** Import/Export configuration file** menu (see Fig. 2.9 - Fig. 2.10).
++  <p>To add a new sound, click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.14.32.png" alt="Add new sound"/>. In the pop-up (Figure 4.2), specify the name, select or drag-and-drop the .mp3 file, and click <img class="inline-icon" src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.15.48.png" alt="Upload"/>.</p>
--NOTE: when adding a new event, crossing **Event ID** is unacceptable as an incomplete event configuration is unloaded. The new **ID** should not match the existing one in the system (configuration).
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.15.12.png" alt="New sound upload window" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 4.2. New sound upload window</p>
++  </div>
--To upload the changes made to the file, click on the button [[image:Screenshot 2025-12-10 at 21.55.55.png||height="25" width="95"]] select **Upload** from the drop-down list. Events that were not taken into account when downloading the Excel file will remain unchanged
++  <div class="note note-warning"><div class="note-hd"><span>&#9888;</span> Important</div><div class="note-body">If CENTO is open in multiple browser tabs (e.g. Sound Editor in one tab, a mimic diagram in another), the old sound will continue to play on the diagram tab after changing the sound in the editor. The new sound will play only after the user interacts with the diagram tab (e.g. clicking the mouse).</div></div>
--IMPORTANT: partial upload/download is not compatible with previously downloaded Excel files. If an Excel file was downloaded using an earlier version of the service (prior to the introduction of the partial upload/download feature), it cannot be uploaded back - an error message saying "Version incompatibility" appears.
++  <h2 id="s-examples">5. Examples of Event Setup<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-examples')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>
--== 2.4. Flashing on the diagram ==
++  <p>The following examples use the web interface on the event creation page described in section 2.2.</p>
--The flashing of an object on the diagram can be configured in the following ways:
++  <h4>Example 1: Event on tag value change</h4>
--**~1. Flashing by tag**
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.17.31.png" alt="Event setup on tag value change" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 5.1. Event setup on tag value change</p>
++  </div>
--This method is relevant if the system does not have and does not plan to customize the information model.
++  <p>Figure 5.1 shows the event <em>Switch position f.1.1 (1QF1)</em> configured as a one-position event bound to an IM object and a device. The formula <code>ti11013008 == 2</code> triggers the event when tag 11013008 equals 2. Dead time is 0 (no delay), acknowledgement is enabled, and the default sound plays 5 times.</p>
--To customize the flashing of a diagram object by tag:
++  <h4>Example 2: Event on device status change (with return)</h4>
--A) Set up an event that will contain the formula, for example, connection loss (ti40027171 != 1) or restoration of connection (ti40027171 == 1) with the device (see Fig. 2.13). The formula can refer not only to the device status, any tags registered in the system can be applied here, in this example, the device status is used as a special case. For more details on the available formulas and expressions, please refer to the** Setup Manual. **
++  <div class="fig">
++    <img src="https://wiki.centosoftware.com/xwiki/bin/download/CENTO%20Manuals/6.%20Events%20Setup/WebHome/Screenshot%202025-12-10%20at%2022.19.25.png" alt="Event setup on device status change" style="max-width:100%;" onclick="openLightbox(this)"/>
++    <p class="fig-cap">Figure 5.2. Event setup on device status change</p>
++  </div>
--[[image:Screenshot 2025-12-10 at 21.58.43.png||height="824" width="1407"]]
++  <p>Figure 5.2 shows a paired event with return. Two notifications are configured:</p>
++  <ol>
++    <li>
++      <strong>Lost connection with Mikrotik SW1.2</strong> &mdash; formula
++      <code>(devstatus100 == 3) AND (devprevstatus100 != 3)</code>, meaning device ID 100
++      just entered error status. Dead time = 3000 ms; alarm type with acknowledgement;
++      sound plays until acknowledged.
++    </li>
++    <li>
++      <strong>Restored connection with Mikrotik SW1.2</strong> &mdash; formula
++      <code>(devstatus100 == 1) AND (devprevstatus100 != 1)</code>, meaning device ID 100
++      just returned to normal status. Informational type; no acknowledgement required;
++      sound plays 3 times.
++    </li>
++  </ol>
--Fig. 2.13 - Event for tag flashing
--B) Create a calculated tag with the formula [devstatusNN], where NN is the device id (see Figure 2.14). The binding to devstatus is used for example. The tag to be used for the designated purpose may get the value from the real device or may be based on other tags.
++  <h2 id="s-annex">Appendix: Formula Reference<a class="anchor-icon" href="javascript:void(0)" onclick="copyAnchor('s-annex')" title="Copy link"><svg width="12" height="12" viewBox="0 0 16 16" fill="currentColor"><path d="M7.775 3.275a.75.75 0 001.06 1.06l1.25-1.25a2 2 0 112.83 2.83l-2.5 2.5a2 2 0 01-2.83 0 .75.75 0 00-1.06 1.06 3.5 3.5 0 004.95 0l2.5-2.5a3.5 3.5 0 00-4.95-4.95l-1.25 1.25zm-4.69 9.64a2 2 0 010-2.83l2.5-2.5a2 2 0 012.83 0 .75.75 0 001.06-1.06 3.5 3.5 0 00-4.95 0l-2.5 2.5a3.5 3.5 0 004.95 4.95l1.25-1.25a.75.75 0 00-1.06-1.06l-1.25 1.25a2 2 0 01-2.83 0z"/></svg></a></h2>
--[[image:Screenshot 2025-12-10 at 21.59.17.png]]
++  <p>Formulas can include arithmetic operations, conditions, mathematical and special functions, and pre-calculated measurements (up to three levels of nesting).</p>
--Fig. 2.14 - Calculated tag to create tag flashing on the diagram
++  <div class="tbl-wrap">
++  <table class="rn-table">
++    <caption style="text-align:left;font-size:.8em;color:#555;padding:6px 0;font-weight:700;">Table A.1 &mdash; Variables in formulas</caption>
++    <thead>
++      <tr>
++        <th style="min-width:160px;">Variable</th>
++        <th>Description</th>
++      </tr>
++    </thead>
++    <tbody>
++      <tr><td><code>[tiN]</code></td><td>Current value of tag with ID&nbsp;N</td></tr>
++      <tr><td><code>[prevN]</code></td><td>Previous value of the tag with ID&nbsp;N</td></tr>
++      <tr><td><code>[statusN]</code></td><td>Current status of tag with ID&nbsp;N</td></tr>
++      <tr><td><code>[prevstatusN]</code></td><td>Previous status of tag with ID&nbsp;N</td></tr>
++      <tr><td><code>[lasttimeN]</code></td><td>Current timestamp of the tag with ID&nbsp;N</td></tr>
++      <tr><td><code>[beforetimeN]</code></td><td>Previous timestamp of the tag with ID&nbsp;N</td></tr>
++      <tr><td><code>[devstatusN]</code></td><td>Current device status: 0&nbsp;= disabled; 1&nbsp;= normal; 2&nbsp;= at least one TI with abnormal quality; 3&nbsp;= polling error (unavailable); 4&nbsp;= manual input; 7&nbsp;= waiting for data</td></tr>
++      <tr><td><code>[devprevstatusN]</code><br><code>[prevdevstatusN]</code></td><td>Previous device status (same status codes as above)</td></tr>
++      <tr><td><code>[devlastdtN]</code></td><td>Time when the latest device data was received</td></tr>
++      <tr><td><code>[devpingtimeN]</code></td><td>Response time (ms) to ICMP ping of device&nbsp;N</td></tr>
++      <tr><td><code>[connectedN]</code></td><td>Connection with device&nbsp;N restored</td></tr>
++      <tr><td><code>[!connectedN]</code></td><td>Connection with device&nbsp;N is lost</td></tr>
++    </tbody>
++  </table>
++  </div>
--C) Set up an object on the diagram, in the rules of which the calculated tag from point b will be applied (see Fig. 2.15).
--[[image:Screenshot 2025-12-10 at 21.59.53.png]]
++  <div class="tbl-wrap">
++  <table class="rn-table">
++    <caption style="text-align:left;font-size:.8em;color:#555;padding:6px 0;font-weight:700;">Table A.2 &mdash; Operators in formulas</caption>
++    <thead>
++      <tr>
++        <th style="min-width:80px;">Operator</th>
++        <th>Description</th>
++        <th>Example</th>
++        <th>Result</th>
++      </tr>
++    </thead>
++    <tbody>
++      <tr><td><code>+</code></td><td>Addition</td><td><code>5 + 5</code></td><td>10</td></tr>
++      <tr><td><code>-</code></td><td>Subtraction</td><td><code>5 - 3</code></td><td>2</td></tr>
++      <tr><td><code>*</code></td><td>Multiplication</td><td><code>0.01 * [val]</code></td><td>0.01 &times; val</td></tr>
++      <tr><td><code>/</code></td><td>Division</td><td><code>[val] / 1000</code></td><td>val / 1000</td></tr>
++      <tr><td><code>%</code></td><td>Modulo (remainder)</td><td><code>10 % 3</code></td><td>1</td></tr>
++      <tr><td><code>=</code></td><td>Assigns a value to a tag</td><td><code>[ti123] = 5</code></td><td>5</td></tr>
++      <tr><td><code>==</code></td><td>Equal (returns true/false)</td><td><code>2 == 2</code></td><td>true</td></tr>
++      <tr><td><code>&lt;, &gt;, &lt;=, &gt;=</code></td><td>Arithmetic comparison</td><td><code>2 &gt;= 3</code></td><td>false</td></tr>
++      <tr><td><code>&amp;&amp;</code>, <code>&amp;</code>, <code>AND</code>, <code>and</code></td><td>Logical AND</td><td><code>(devstatus1==1) AND (devstatus2==1)</code></td><td>true if both</td></tr>
++      <tr><td><code>||</code>, <code>|</code>, <code>OR</code>, <code>or</code></td><td>Logical OR</td><td><code>(devstatus1==3) OR (devstatus2==3)</code></td><td>true if either</td></tr>
++    </tbody>
++  </table>
++  </div>
--Figure 2.15 - Example rules with the tag created in step b.
--D) After saving the diagram and updating the configuration, if the status of the NN device changes, the system will start it flashing on the diagram until acknowledged.
++  <div class="parent-topic">Parent topic: <a href="[[CENTO Manuals>>doc:CENTO Manuals.WebHome]]">CENTO Manuals</a></div>
--**2. Flashing by the information model object**
++</div><!-- /doc-content -->
--For this method to work, the information model should be configured, and the required information model object should be selected in the event setting (**Object** field). In this case, the diagram object should be active (see more details in the "Diagrams Development Manual") and bound to the information model object selected in the event.
++<nav class="doc-toc">
++  <div class="toc-header">
++    <strong>On This Page</strong>
++    <button class="toc-toggle" id="toc-tog" title="Collapse">&laquo;</button>
++  </div>
++  <ul id="toc-list">
++    <li class="tl1"><a href="#s-intro" data-toc>1. Introduction</a></li>
++    <li class="tl1"><a href="#s-events" data-toc>2. CENTO Events</a></li>
++    <li class="tl2"><a href="#s-event-editor" data-toc>2.1. Event editor</a></li>
++    <li class="tl2"><a href="#s-event-create" data-toc>2.2. Creating events (UI)</a></li>
++    <li class="tl2"><a href="#s-event-excel" data-toc>2.3. Creating events (Excel)</a></li>
++    <li class="tl2"><a href="#s-event-flash" data-toc>2.4. Flashing on diagram</a></li>
++    <li class="tl1"><a href="#s-notifications" data-toc>3. Notifications</a></li>
++    <li class="tl2"><a href="#s-notif-create" data-toc>3.1. Creating notifications</a></li>
++    <li class="tl2"><a href="#s-notif-logic" data-toc>3.2. Notification logic</a></li>
++    <li class="tl1"><a href="#s-sound-editor" data-toc>4. Sound Editor</a></li>
++    <li class="tl1"><a href="#s-examples" data-toc>5. Examples</a></li>
++    <li class="tl1"><a href="#s-annex" data-toc>Appendix: Formulas</a></li>
++  </ul>
++</nav>
--Let us consider an example of this solution.
++</div><!-- /doc-wrap -->
--A) Create an event with the selected object of the information model in the **Object** field (see Fig. 2.15).[[image:Screenshot 2025-12-10 at 22.01.01.png]]
--
--Fig. 2.15 - Creating an event with the information model object.
--
--B) Create an active object on the diagram bound to the object of the information model, which was selected in the event settings (see Fig. 2.16).
--
--[[image:Screenshot 2025-12-10 at 22.02.05.png]]
--
--Fig. 2.16 - Creating a diagram object bound to the information model.
--
--= 3. NOTIFICATIONS SETTINGS =
--
--== 3.1. Creating and editing notifications ==
--
--CENTO has the function to notify users about an event triggered via e-mail.
--
--To configure notifications, go to the /CENTO/web/ui/notifications_configuration/index page (menu item Settings > Events > Notifications (see Fig. 2.1). The configuration of the mail server is described in the "Setup Manual, Mail servers".
--
--
--[[image:Screenshot 2025-12-10 at 22.03.45.png]]
--
--Fig. 3.1 - Notifications interface
--
--In the interface presented, the user has the ability to:
--
--~1. Create notifications;
--
--2. Edit notifications.
--
--The notification table has the following columns.
--
--1. **Name **is the name of the notification.
--1. **Emails **are the e-mail addresses that have been configured to receive notifications.
--1. **Dispatch period **is the time of the day allowed for sending notifications.
--1. **Iteration period** is the minimum time interval between notifications, meaning notifications cannot be sent to the recipient more frequently than this set period.
--1. **Operation threshold **is the number of event triggers required before a notification is sent.
--1. **State **is on/off.
--1. **Actions** are operations available to the user that can be performed in response to an event (edit [[image:Screenshot 2025-12-10 at 22.05.05.png||height="25" width="27"]], copy [[image:Screenshot 2025-12-10 at 22.05.32.png||height="26" width="26"]], delete [[image:Screenshot 2025-12-10 at 22.05.55.png||height="26" width="23"]]).
--
--To create a new notification, click the button [[image:Screenshot 2025-12-10 at 22.06.27.png||height="33" width="151"]].
--
--Only an authorized user with appropriate permissions can create and edit notifications.
--
--The notifications creation is shown in Fig. 3.2.
--
--[[image:Screenshot 2025-12-10 at 22.07.01.png]]
--
--Fig. 3.2 - Notifications: creation page
--
--To create a notification, fill in the following fields in the **Notification settings** tab:
--
--**Name** is used to specify the name of the notification.
--
--**State **is a switch that enables or disables the notification.
--
--**Operation threshold **is the number of event triggers required before a notification is sent.
--
--**Dispatch period** is the time of the day allowed for sending notifications.
--
--**Iteration period** is the minimum time interval between notifications, meaning notifications cannot be sent to the recipient more frequently than this set period.
--
--**Delay (s) **is** **set to accumulate events during the delay from the first event.
--
--**Notification method:**
--
--**E-mail server **is a mail server used for sending messages. Mail servers are configured in the Settings > Email servers menu (for details on configuring mail servers, refer to the "Setup Manual").
--
--Recipients is a field for entering e-mail addresses of notification recipients.
--
--[[image:Screenshot 2025-12-10 at 22.07.55.png]]
--
--Fig. 3.3 - Event selection tab
--
--In the "Event selection" tab (Fig. 3.3), tick the events required for notification in the left column and use the "Right" button [[image:Screenshot 2025-12-10 at 22.08.29.png||height="27" width="24"]]to move them to the right column. Unnecessary events can be moved from the right column using the "Left" button [[image:Screenshot 2025-12-10 at 22.08.55.png||height="28" width="25"]], having previously marked them with checkmarks.
--
--After filling in all the fields, click the button [[image:Screenshot 2025-12-10 at 22.09.48.png||height="24" width="60"]] and update the configuration.
--
--== 3.2. Notification operation ==
--
--There are three types of filters in the notifications:
--
--1. Operation threshold;
--1. Iteration period;
--1. Dispatch period.
--
--When configured without restrictions, the notification comes whenever any of the configured events added to the notification are triggered.
--
--**Operation threshold**
--
--The notification is triggered when the total number of triggered events in the notification reaches the number the user set.
--
--If the operation threshold is 0, the notification is generated immediately after any of the events in the notification are triggered, unless the Iteration period is set and the Dispatch period is allowed.
--
--**Iteration period**
--
--The iteration period report starts from the time when the last notification was triggered. The iteration period is set in days and hours.
--
--If the iteration period is set to 0 days 0 hours, notifications will be generated and sent immediately if the conditions of other filters are met.
--
--**Dispatch period**
--
--If the dispatch period is set to 0:00 - 24:00, notifications can be sent at any time of the day.
--
--If the dispatch period is set to a specific time, such as 8:00, notifications will be sent once a day at that time.
--
--Currently, the dispatch period can only be set within a single day. For example, it is not possible to set a period from 20:00 to 6:00 of the next day.
--
--[[image:Screenshot 2025-12-10 at 22.11.07.png]]
--
--Fig.3.4 - Logic of settings operation when generating notifications
--
--**Changing notification settings**
--
--If you change the alert settings (name, addresses, mail servers, triggering limits, message set, etc.) at any time, the following will happen:
--
--If the notification settings (name, recipients, email servers, operation limits, message set, etc.) are changed at any time, the following will occur:
--
--The operation threshold is saved, but the notification will not be triggered until the next event in the notification if the operation threshold is reached.
--
--The iteration period is reset.
--
--**Examples of changing notification settings:**
--
--1. The operation threshold limit was set to 5, and 3 events were triggered. After the user increases the threshold to 10, the notification will be triggered after 7 more events.
--1. The operation threshold was set to 10, and 7 events were triggered. After the user reduces the operation threshold to 5, a notification will be sent after the next event, for a total of 8 triggered events.
--1. The iteration period was set to 10 hours, and the first notification was sent 2 hours ago. Events are triggered periodically. If the notification settings are changed, the iteration period will be reset, and a notification will be sent the next time an event is triggered. The iteration period counter will start again.
--1. The operation threshold was set to 10. There are 3 events in the notification. The 1st event triggered 2 times. Then the User deleted the first event from the notification. The triggering counter is not reset. When the triggering counter reaches the value of 10, the notification with 8 triggering messages will be sent. The first event (which was deleted) will not be included in the notification text.
--
--**Examples of alert notification logic**
--
--[[image:Screenshot 2025-12-10 at 22.12.07.png]]
--
--Fig.3.5 - Notification with operation threshold
--
--[[image:Screenshot 2025-12-10 at 22.12.39.png]]
--
--Fig. 3.6 - Notification with dispatch period
--
--[[image:Screenshot 2025-12-10 at 22.13.08.png]]
--
--Fig. 3.7 - Notification with all restrictions
--
--The types of sound notifications are configured on the /CENTO/web/ui/sound_editor/index page (Settings > Events > Sound editor (see Fig. 2.1)) (see Fig. 4.1).
--
--[[image:Screenshot 2025-12-10 at 22.13.46.png]]
--
--Fig. 4.1 - "Sound Editor" page
--
--The **Sound editor** page shows a table with available sounds. The table contains the following columns:
--
--**ID **is a unique digital identifier of the sound.
--
--**Name** is the name of the sound.
--
--**File name **is the name of the uploaded sound file.
--
--**Uploaded **is the date when the sound was uploaded to the system.
--
--**Actions **is used to manage sounds: edit sound, play sound file, and delete.
--
--**Note: t**he sound editor allows only ".mp3" to be uploaded.
--
--To create a new sound, click the button [[image:Screenshot 2025-12-10 at 22.14.32.png||height="25" width="110"]]. After that a pop-up window appears (see Fig. 4.2).
--
--[[image:Screenshot 2025-12-10 at 22.15.12.png||height="242" width="376"]]
--
--Fig. 4.2 - New sound upload window
--
--In the window that appears, specify the name of the new sound, select a file from your computer or drag and drop the sound file into the special field. After clicking the button [[image:Screenshot 2025-12-10 at 22.15.48.png||height="22" width="43"]], the created sound will appear in the Sound Editor.
--
--**Attention! **If CENTO is opened in multiple browser tabs, for example, with the sound editor in the first tab and the diagram in the second tab, the old sound will continue to play on the diagram tab after changing the sound in the sound editor. The new sound will only play on the diagram tab once the user interacts with the diagram page (e.g., by clicking a mouse button on the diagram tab).
--
--= 5. EXAMPLES OF EVENT SETTING =
--
--Let’s look at some examples of event settings using the web interface. All actions are performed on the event creation page, as described in section 2.1 of this manual.
--
--Example No.1: Setting up an event on tag value change.
--
--[[image:Screenshot 2025-12-10 at 22.17.31.png]]
--
--Fig. 5.1 - Event setting on tag value change
--
--Fig.5.1 shows that the event //Switch position f.1.1 (1QF1)// is configured with a one-position event type bound to the IM object and the device, from which the tag value changes come with the ID number 11013008. The text in the **Message** field will be written in the CENTO **Event logs,** which gets there when the tag value 11013008 is equal to 2, the formula //__ti11013008==__// 2 tells about it (formula operators are given in the Annex). This event will be configured with dead time 0 (there will be no delay in event generation), with acknowledgment and with playing the default sound, which will sound 5 times and then turn off.
--
--Example No. 2: Setting up the event on device status change.
--
--Let’s consider an example of configuring an event for changing the device status (see Fig. 5.2). The event is configured with a return. Fill all the necessary fields with information similar to the previous example. This event is divided into two notifications:
--
--1. The event //Lost connection with the device Mikrotik SW1.2 switch //enters the event log under the condition described in the formula //(devstatus100== 3) AND (devprevstatus100 !=3)//, which indicates that the status of the device with ID100 came equal to 3 and the previous status does not equal 3. This event will be configured with dead time 3000 (delay on event generation will be equal to 3000 ms) as an alarm event with acknowledgment and with sound playing until the user acknowledges this notification.
--1. The event //Restored connection with device Mikrotik SW1.2 switch //is logged in the event log under the condition described in the formula //(devstatus100== 1) AND (devprevstatus100 !=1)//, which indicates that the status of the device with ID100 came equal to 1 and the previous status is not equal to 1. This event will be configured as informative without acknowledgment and with a sound that will be played 3 times and then turned off.
--
--[[image:Screenshot 2025-12-10 at 22.19.25.png]]
--
--Fig. 5.2 - Setting up the event on device status change
--
------
--
--Annex: description of formula
--
--Arithmetic operations, conditions, mathematical and special functions, etc., are allowed. Up to three levels of nested pre-calculated measurements are permitted.
--
--Table A.1 - Variables in formulas
--
--|(% style="width:404px" %)Variable|(% style="width:472px" %)Description
--|(% style="width:404px" %)(((
--[tiN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Current value of tag with id N
--|(% style="width:404px" %)(((
--[prevN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Previous value of the tag with id N
--|(% style="width:404px" %)(((
--[statusN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Current status of tag with id N
--|(% style="width:404px" %)(((
--[prevstatusN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Previous status of tag with id N
--|(% style="width:404px" %)(((
--[lasttimeN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Current timestamp of the tag with id N
--|(% style="width:404px" %)(((
--[beforetimeN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Previous timestamp of the tag with id N
--|(% style="width:404px" %)(((
--[devstatusN],
--
--where N is the device number (ID)
--)))|(% style="width:472px" %)Current status of the device (0 - disabled in configuration; 1 - normal; 2 - at least one TI has abnormal quality (out of limits or error in formula); 3 - device polling error (device unavailable); 4 - manual input in tags or channels of the device, 7 - waiting for data)
--|(% style="width:404px" %)(((
--[devprevstatusN] or
--
-- [prevdevstatusN]
--
--where N is the device number (ID)
--)))|(% style="width:472px" %)Previous device status (0-disabled in configuration; 1 - normal; 2 - at least one TI has abnormal quality (out of limits or formula error); 3 - device polling error (device unavailable); 4 - manual input in device tags or channels, 7 - waiting for data)
--|(% style="width:404px" %)(((
--[devlastdtN],
--
--where N is the device number (ID)
--)))|(% style="width:472px" %)The time when the latest device data was received
--|(% style="width:404px" %)(((
--[devpingtimeN],
--
--where N is the device number (ID)
--)))|(% style="width:472px" %)Response time (in ms) to the ping command of the device polled by ICMP
--|(% style="width:404px" %)(((
--[connectedN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Connection with the device with id N restored
--|(% style="width:404px" %)(((
--[!connectedN],
--
--where N is the sequence number of TI
--)))|(% style="width:472px" %)Connection with the device with id N is lost
--
--Table A.2 - Operators in formulas
--
--|Operator|Description|Utilization|Result
--|+|Adds up numbers or tag values|5 + 5|10
--|-|Subtracts the first number or tag value from the second number or tag value|5 - 3|2
--|*|Multiplies numbers or tag values|0.01 * [val]|0.01 * [val]
--|/|Divides the first number or tag value by the second number or tag value|[val] / 1000|[val] / 1000
--|%|Returns the remainder of the division|10 / 3|1
--|= |Assigns a specific value to a tag|[ti123] = 5|5
--|==|Returns true if the compared values are equal, and false if they are not equal|2 == 2|true
--|<, >, <=, >=|Returns true if the arithmetic condition is met and false if it is not met|2 >= 3|false
--|&&, &, &, &|Logical operator "and"| |
--|~|~|, OR, or|Logical operator "or"| |
--
--
--
--
++<script>
++(function(){
++  var bar=document.getElementById('rn-prog');
++  var top=document.getElementById('rn-top');
++  window.addEventListener('scroll',function(){
++    var d=document.documentElement;
++    var pct=d.scrollTop/(d.scrollHeight-d.clientHeight);
++    bar.style.width=(pct*100)+'%';
++    d.scrollTop>280?top.classList.add('on'):top.classList.remove('on');
++  },{passive:true});
++  var links=Array.from(document.querySelectorAll('[data-toc]'));
++  var secs=links.map(function(a){return{el:document.getElementById(a.getAttribute('href').slice(1)),a:a};}).filter(function(s){return s.el;});
++  var busy=false;
++  var obs=new IntersectionObserver(function(entries){
++    if(busy)return;
++    entries.forEach(function(e){
++      if(!e.isIntersecting)return;
++      var i=secs.findIndex(function(s){return s.el===e.target;});
++      if(i<0)return;
++      secs.forEach(function(s){s.a.classList.remove('toc-on');});
++      secs[i].a.classList.add('toc-on');
++      var toc=document.querySelector('.doc-toc');
++      var link=secs[i].a;
++      toc.scrollTop=link.offsetTop-toc.offsetTop-toc.clientHeight/2+link.clientHeight/2;
++    });
++  },{rootMargin:'-8% 0px -60% 0px',threshold:0});
++  secs.forEach(function(s){obs.observe(s.el);});
++  links.forEach(function(a){
++    a.addEventListener('click',function(e){
++      var id=a.getAttribute('href').slice(1);
++      var el=document.getElementById(id);
++      if(!el)return;
++      e.preventDefault();
++      busy=true;
++      secs.forEach(function(s){s.a.classList.remove('toc-on');});
++      a.classList.add('toc-on');
++      el.scrollIntoView({behavior:'smooth',block:'start'});
++      setTimeout(function(){busy=false;},900);
++    });
++  });
++  var tocList=document.getElementById('toc-list');
++  var togBtn=document.getElementById('toc-tog');
++  var collapsed=false;
++  togBtn&&togBtn.addEventListener('click',function(){
++    collapsed=!collapsed;
++    tocList.style.display=collapsed?'none':'';
++    togBtn.textContent=collapsed?'»':'«';
++  });
++  var lb=document.getElementById('rn-lb');
++  var lbI=document.getElementById('rn-lb-img');
++  var lbC=document.getElementById('rn-lb-cap');
++  window.openLightbox=function(img){lbI.src=img.src;lbI.alt=img.alt;lbC.textContent=img.alt;lb.classList.add('open');document.body.style.overflow='hidden';};
++  window.closeLightbox=function(){lb.classList.remove('open');document.body.style.overflow='';};
++  lb.addEventListener('click',function(e){if(e.target===lb)closeLightbox();});
++  document.addEventListener('keydown',function(e){if(e.key==='Escape')closeLightbox();});
++  var toast=document.getElementById('rn-toast');
++  var t;
++  window.copyAnchor=function(id){
++    var url=location.href.split('#')[0]+'#'+id;
++    if(navigator.clipboard)navigator.clipboard.writeText(url).catch(function(){});
++    else{var x=document.createElement('textarea');x.value=url;document.body.appendChild(x);x.select();document.execCommand('copy');document.body.removeChild(x);}
++    toast.classList.add('on');clearTimeout(t);t=setTimeout(function(){toast.classList.remove('on');},1600);
++  };
++  (function(){
++    var toc=document.querySelector('.doc-toc');
++    var wrap=document.querySelector('.doc-wrap');
++    if(!toc||!wrap)return;
++    var navbar=document.querySelector('.navbar,nav.navbar,#topBar,header');
++    var navH=navbar?navbar.offsetHeight:0;
++    var footer=document.querySelector('footer,.xwikifooter,#xwikifooter,.bottombar,.sticky-container');
++    function update(){
++      var wr=wrap.getBoundingClientRect();
++      if(wr.top<=navH){
++        var footerTop=footer?footer.getBoundingClientRect().top:window.innerHeight;
++        var h=Math.max(0,Math.min(window.innerHeight,footerTop)-navH);
++        toc.classList.add('is-fixed');toc.style.top=navH+'px';toc.style.left=(wr.right-200)+'px';toc.style.height=h+'px';
++      }else{toc.classList.remove('is-fixed');toc.style.top=toc.style.left=toc.style.height='';}
++    }
++    requestAnimationFrame(function(){requestAnimationFrame(function(){update();window.addEventListener('scroll',update,{passive:true});window.addEventListener('resize',update,{passive:true});});});
++  })();
++})();
++</script>
++{{/html}}