AutoTask Notifications

For an overview of AutoTasks and their syntax, see AutoTasks

An Autotask can be configured to send a notification email once its match criteria are met. This is achieved by the use of the notifications component. In the example below, when an asset is uploaded into NetX, a notification email using the email template assetImportReport.tpl will be sent to the email address associated with all of the users included in the group named Import admins.

<task name="Notification on import">
	<matchCriteria type="and">
    	<criteria type="action" value="import"/>
 	</matchCriteria>
 	<notifications>
    	<notify emailTemplate="assetImportReport.tpl" groupName="Import admins" type="email"/>
	</notifications>
</task>

email

Only one recipient parameter can be used per AutoTask when adding a notification component, e.g. you may use address or groupName or user, but cannot combine any of these parameters with the other two. 

The notification type is always email. The following parameters specify both the email's recipient(s) as well as the email template sent to any recipients. Both a recipient and an email template parameter are required.

Parameter Description

emailTemplate

This parameter determines which email template is sent once the AutoTask's match criteria are met. The file type suffix is required

Value options: Name of an existing email template

address

The value of this parameter must correspond to a valid email address. Events that trigger the task's match criteria will send a notifying email to the specified address. This parameter cannot be used in conjunction with either groupName or user parameters.

Value options: email address

groupName

This parameter defines which NetX users will receive a notification once the task's match criteria have been met, by using an existing group name as its value. This parameter cannot be used in conjunction with either address or user parameters. 

Value options: NetX group name

user

This parameter defines the user who will receive a notification once the task's match criteria have been met. This parameter cannot be used in conjunction with either address or groupName parameters.

Value options: 

  • self: A value of self will send a notification to the email address associated with the user whose actions triggered the task. 
  • mod: If the AutoTask's match criteria rely on asset-based triggers (such as uploading or resyncing an asset), a user value of mod will send a notification to the email address associated with the user who last modified the asset.  
  • categoryManager: A value of categoryManager will send a notification to the email address of the user who created the folder identified in the AutoTask. This value requires a category context in the AutoTask's match criteria
Was this article helpful?
0 out of 0 found this helpful