Skip to Content

Changes for page 7. Events Setup

Last modified by Iaroslav Platonov on 2026/06/09 11:03
From version 36.2
edited by Lana
on 2025/12/11 00:56
Change comment: There is no comment for this version
To version 40.2
edited by Lana
on 2025/12/11 01:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -218,13 +218,56 @@
218 218  
219 219  To make working with events more convenient, CENTO provides the option to edit the event configuration partially using Excel.
220 220  
221 -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="29" width="110"]]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**.
221 +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**.
222 222  
223 223  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).
224 224  
225 225  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).
226 226  
227 -To upload the changes made to the file, click on the button [[image:Screenshot 2025-12-10 at 21.55.55.png||height="22" width="83"]]
227 +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
228 228  
229 +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.
229 229  
231 +== 2.4. Flashing on the diagram ==
232 +
233 +The flashing of an object on the diagram can be configured in the following ways:
234 +
235 +**~1. Flashing by tag**
236 +
237 +This method is relevant if the system does not have and does not plan to customize the information model.
238 +
239 +To customize the flashing of a diagram object by tag:
240 +
241 +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. **
242 +
243 +[[image:Screenshot 2025-12-10 at 21.58.43.png]]
244 +
245 +Fig. 2.13 - Event for tag flashing
246 +
247 +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.
248 +
249 +[[image:Screenshot 2025-12-10 at 21.59.17.png]]
250 +
251 +Fig. 2.14 - Calculated tag to create tag flashing on the diagram
252 +
253 +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).
254 +
255 +[[image:Screenshot 2025-12-10 at 21.59.53.png]]
256 +
257 +Figure 2.15 - Example rules with the tag created in step b.
258 +
259 +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.
260 +
261 +**2. Flashing by the information model object**
262 +
263 +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.
264 +
265 +Let us consider an example of this solution.
266 +
267 +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]]
268 +
269 +​​​​​​​
270 +
230 230  
272 +
273 +
Screenshot 2025-12-10 at 21.58.43.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +112.9 KB
Content
Screenshot 2025-12-10 at 21.59.17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +160.3 KB
Content
Screenshot 2025-12-10 at 21.59.53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +69.5 KB
Content
Screenshot 2025-12-10 at 22.01.01.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +126.0 KB
Content