email user based on container items

Reply to email user based on container items on Fri, 11 Sep 2015 17:39:51 GMT

Jmp_3f8h — Fri, 11 Sep 2015 17:39:51 GMT

@victor said in email user based on container items:

rcpt = GetRecipients($node);
return (rcpt != null) ? rcpt : "default@email";  // fallback email if nothing was set in containers

sub GetRecipients(obj)
{
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetCustomAttribute(p, "recipients");
	if (rcpt != null)
		return rcpt;
    }
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetRecipients(p);
	if (rcpt != null)
		return rcpt;
    }
    return null;
}

I've used this one (the second) and it rocks! Thank you very much for your help.

Best remarks,
Marco

Reply to email user based on container items on Fri, 11 Sep 2015 12:37:36 GMT

victor — Fri, 11 Sep 2015 12:37:36 GMT

Only direct parents are examined. Recursive script could looks like this:

rcpt = GetRecipients($node);
return (rcpt != null) ? rcpt : "default@email";  // fallback email if nothing was set in containers

sub GetRecipients(obj)
{
    rcpt = GetCustomAttribute(obj, "recipients");
    if (rcpt != null)
	 return rcpt;
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetRecipients(p);
  	if (rcpt != null)
 		return rcpt;
    }
    return null;
}

and if you want that any closest parent had higher priority:

rcpt = GetRecipients($node);
return (rcpt != null) ? rcpt : "default@email";  // fallback email if nothing was set in containers

sub GetRecipients(obj)
{
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetCustomAttribute(p, "recipients");
	if (rcpt != null)
		return rcpt;
    }
    foreach(p : GetObjectParents(obj))
    {
        rcpt = GetRecipients(p);
	if (rcpt != null)
		return rcpt;
    }
    return null;
}

Best regards,
Victor

Reply to email user based on container items on Fri, 11 Sep 2015 12:27:00 GMT

Jmp_3f8h — Fri, 11 Sep 2015 12:27:00 GMT

@victor said in email user based on container items:

Hi,

how script to extract recipients looks like?

Best regards,
Victor

Exactly like te one you posted in your example, I assumed (wrongly at this point) that all the parents were explored in the "foreach" statement.

Marco

Reply to email user based on container items on Fri, 11 Sep 2015 12:24:32 GMT

victor — Fri, 11 Sep 2015 12:24:32 GMT

Hi,

how script to extract recipients looks like?

Best regards,
Victor

Reply to email user based on container items on Thu, 10 Sep 2015 21:55:46 GMT

Jmp_3f8h — Thu, 10 Sep 2015 21:55:46 GMT

@victor said in email user based on container items:

It will return emails configured in parent container for node in custom attribute "recipients", or default email if nothing is configured. Script can be made more complicated to collect all recipients on all upper layers and combine them into single recipient list.

Hi Victor,

Have a look to the attached image. Is it possible to find the custom attribute in a "top level" parent container? I've created the custom attribute "recipients" into the container "Thinksoft" but when the alarm is generated from an inner node (e.g. VM-REDQUEEN three levels down or SKYNET two levels down) that custom attribute seems ignored.

Best regards,
Marco

Reply to email user based on container items on Tue, 18 Aug 2015 14:50:44 GMT

curruscanis — Tue, 18 Aug 2015 14:50:44 GMT

Thank you Victor, I will give that a try. It is easier than setting up different alerts and actions for each email address.

Reply to email user based on container items on Tue, 04 Aug 2015 15:06:57 GMT

victor — Tue, 04 Aug 2015 15:06:57 GMT

You can set responsible person's in container's custom attribute, and create universal action that will use script to extract recipient. For example, you can definie recipients in email action like this:

%[GetRecipients]

Then, create script in script library caled "GetRecipients" like this:

foreach(p : GetNodeParents($node))
{
	rcpt = GetCustomAttribute(p, "recipients");
	if (rcpt != null)
		return rcpt;
}
return "default@email";  // fallback email if nothing was set in containers

It will return emails configured in parent container for node in custom attribute "recipients", or default email if nothing is configured. Script can be made more complicated to collect all recipients on all upper layers and combine them into single recipient list.

Best regards,
Victor

Reply to email user based on container items on Tue, 28 Jul 2015 20:16:04 GMT

curruscanis — Tue, 28 Jul 2015 20:16:04 GMT

Thank you Alex, that is what I came up with too. I was hoping there was a way to alter a given rule in the event processing that would do both. If I have to create a new rule for each container that has a different person responsible it will eventually be a lot of redundant rules with the only difference being the email destination.

Reply to email user based on container items on Mon, 27 Jul 2015 22:24:52 GMT

alk — Mon, 27 Jul 2015 22:24:52 GMT

Just add additional rule into EPP. Set events=(list), source=container, action=email-to-additional-user