ezeio2:userinterface:manage:destinations

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
ezeio2:userinterface:manage:destinations [2024-10-03 16:19] – andrehezeio2:userinterface:manage:destinations [2026-01-12 20:23] (current) – johpar
Line 1: Line 1:
 ====== Destinations & Destination Lists ====== ====== Destinations & Destination Lists ======
 {{indexmenu_n>740}} {{indexmenu_n>740}}
 +
 +The purpose of these two resources is to allow efficient management of message templates and where they are sent. Once created, a Destination List can be selected for an unlimited number of "Send message" alarm actions. If changes are required, such as on-boarding a new employee, simply edit the Destination List and the effect is account wide. 
 +
 +Although visible from the groups under an account, Destinations and Destination List tabs are an account resource. If the users of a group need to create and manage their own Destinations and Destination Lists, their group must be upgraded to an account.
 +
 +<WRAP center round info 60%>
 +To access Destinations and Destination List a user must be invited to an account and have the privilege "Can add/change destinations". 
 +</WRAP>
 +
  
 === Destinations === === Destinations ===
  
-Destinations are the endpoints for messages sent via "Alarm Actions". These endpoints are typically various methods of connecting with human recipients, but API calls to other software programs is also an option. The "Destination" tab for each "Group" is like a address book, but since each destination is a single endpoint an individual human recipient may have multiple entries to list; email, cell phone, and text.  +Destinations are the endpoints for messages sent via "Alarm Actions". These endpoints are typically various methods of connecting with human recipients, but API calls to other software programs is also an option. The "Destination" tab for each "Account" is like a address book, but since each destination is a single endpoint an individual human recipient may have multiple entries to list; email, cell phone, and text.  
  
 ^ Endpoint Type ^ Action ^ Example ^  ^ Endpoint Type ^ Action ^ Example ^ 
Line 13: Line 22:
 | Send to Pushover | Directs a text message to an individual through the Pushover app, using their Pushover key | :abc123def456abc123def456abc123xy | | Send to Pushover | Directs a text message to an individual through the Pushover app, using their Pushover key | :abc123def456abc123def456abc123xy |
 | Send to Nagios | Nagios is a open source monitoring system. See https://www.nagios.org | https://my.nagiosserver.com/nrdp + access token | | Send to Nagios | Nagios is a open source monitoring system. See https://www.nagios.org | https://my.nagiosserver.com/nrdp + access token |
 +| Send command | Send a command to a different ezeio. See [[..:..:apiref:control|control API]] for possible commands. | Serial number of ezeio to send command to |
  
  
Line 37: Line 47:
 === Message Templates === === Message Templates ===
  
-The Message Template allows a user with adequate privileges, to customize the message assigned to each List Step (Destination) using plain text and [[ezeio2:userinterface:manage:meggagetemplates|Message Template tags]]. The Default message templates are tailored to the Destination Type, making the default SMS messages shorter than email. You can also choose to give more or different information to some Destinations (recipients). Message Template Tags  allow the message to contain current field values, device status, system info, meta data, even a Google maps link with the units location. +The Message Template allows a user with adequate privileges, to customize the message assigned to each List Step (Destination) using plain text and [[ezeio2:userinterface:manage:messagetemplates|Message Template tags]]. The Default message templates are tailored to the Destination Type, making the default SMS messages shorter than email. You can also choose to give more or different information to some Destinations (recipients). Message Template Tags  allow the message to contain current field values, device status, system info, meta data, even a Google maps link with the units location. 
  
 **__Default SMS Message Template__**  **__Default SMS Message Template__** 
Line 50: Line 60:
  
 ^ Message structure ^ Message item ^ tags ^ ^ Message structure ^ Message item ^ tags ^
-| Sender | ezeio S/N, Name  | Not customizable |+| Sender | ezeio S/N, Name  | Default to ''{serial}@eze.io'', see below |
 | Subject | Message Type, Action Name | [SOURCENAME] [ACTIONAME] | | Subject | Message Type, Action Name | [SOURCENAME] [ACTIONAME] |
 | Body | Alarm Action Message, Date, Time  | [ACTIONMESSAGE] [ISODATE] [ISOTIME] | | Body | Alarm Action Message, Date, Time  | [ACTIONMESSAGE] [ISODATE] [ISOTIME] |
-| Footer (Fixed) | https://ezeio & ezeio serial # | Not customizable |+| Footer (Fixed) | https://ezeio & ezeio serial # | See below |
 |  |  |  | |  |  |  |
  
  • ezeio2/userinterface/manage/destinations.1727972395.txt.gz
  • Last modified: 2024-10-03 16:19
  • by andreh