{"id":12395,"date":"2018-10-30T12:29:35","date_gmt":"2018-10-30T16:29:35","guid":{"rendered":"https:\/\/avtech.com\/articles\/?p=12395"},"modified":"2025-01-06T12:56:41","modified_gmt":"2025-01-06T17:56:41","slug":"how-to-simplify-your-device-manager-alert-configuration","status":"publish","type":"post","link":"https:\/\/avtech.com\/articles\/12395\/how-to-simplify-your-device-manager-alert-configuration\/","title":{"rendered":"How to Simplify Your Device ManageR Alert Configuration"},"content":{"rendered":"

Contacts, Actions and Action\/Notification Lists are the building blocks for your Alerts.<\/p>\n

\"\"<\/a><\/p>\n

If your alert configuration has duplicates of any of these components\u20142 or more Actions, for example, that do exactly the same thing but have different names\u2014you have a more complicated structure than you need.<\/p>\n

The models in this FAQ show you what to avoid and how to streamline your set up.<\/p>\n

<\/span>If your Alert configuration looks like this . . .<\/div>
\n

How Not to Set Up Alerts in Device ManageR<\/h3>\n

Don’t work from the top (Alerts) down to the bottom (Contacts) when setting up your Alerts.<\/p>\n

You’ll end up with a complicated configuration cluttered with unnecessary duplicates.<\/p>\n

\n
\n

\"\"<\/a><\/p>\n

Notice the unnecessary duplicates in the flowchart to the right.<\/p>\n

– Contacts 2 & 3 are the same as Contact 1.<\/p>\n

– Likewise for Actions 2 & 3 and Action\/Notification Lists 2 & 3.<\/p>\n

Contacts, Actions and Action\/Notification Lists are meant to be unique and to be re-used.<\/p>\n

If your set up is like this, simplify it based on the model below<\/a>.<\/p>\n<\/div><\/div>\n

\n

\"\"<\/a><\/p>\n<\/div><\/div>\n<\/div>\n<\/div><\/div>\n

<\/span>Change it to this.<\/div>
\n

How to Set Up Alerts in Device ManageR<\/h3>\n

Work from the bottom (Contacts) up to the top (Alerts) when setting up your Alerts.<\/p>\n

\n
\n

\"\"<\/a><\/p>\n

Notice that each Contact, Action and Action\/Notification List is unique in the flowchart to the right.<\/p>\n

– Each unique Contact has 1 unique corresponding Action.<\/p>\n

– The 2 unique Actions are grouped into a unique Action\/Notification List.<\/p>\n

– That Action\/Notification List is re-used in all 3 Alerts.<\/p>\n<\/div><\/div>\n

\n

\"\"<\/a><\/p>\n<\/div><\/div>\n<\/div>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"

Contacts, Actions and Action\/Notification Lists are the building blocks for your Alerts. If your alert configuration has duplicates of any of these components\u20142 or more Actions, for example, that do exactly the same thing but have different names\u2014you have a more complicated structure than you need. The models in this FAQ show you what to […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0},"categories":[3],"tags":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n