I'm not totally clear on your scenario. Do you know in advance what files get produced and who they need to go to? If so you could add a separate notification task for each file.

In terms of setting the recipient list at runtime, you can do this by configuring the Task with a Job Variable:

1. On the Recipients page of the Notification Task Properties, there's an "Additional Recipients" section. Add a new recipient here and set the e-mail address to a variable token, such as "%RecipientList%".

2. Add a script somewhere before the task runs to set the RecipientList variable to the recipient(s) you want to send to. Separate multiple recipients with a vertical bar ("|"). Example code:

adTempus.JobVariables.Add("RecipientList","some person <[email protected]>|[email protected]|third person <[email protected]>")

Note that you can optionally include a display name.

You can also send notification messages programmatically from a script, using the adTempus.SendNotificationMessage method. Sample code (in VB):

        Dim message As New Notification.NotificationMessage()
        message.Subject="Here is your file"
        message.Message="File is attached"
        message.AddAttachment("c:\test\myfile.txt",Nothing)
        message.AddMailRecipient("someone","[email protected]",MessageRecipientType.To)
        adTempus.SendNotificationMessage(message)

Please clarify your needs if you need more assistance.

Bill:

Thanks very good ideas.  What I would ideally like to do is create a Notification Recipients Group for each of the various files we will be delivering, use a Notification Task and plug in the Recipients Group to send to at run time.  I've gotten the %RecipientList% variable to work, but only with a single email destination . . . the pipe delimited list doesn't seem to work for me.

Is there perhaps a sample to access the Notification step in the current job and plug in by name a chosen group?  What I have done so far is add multiple Notification Tasks, one per delivered item with a static Notification Group.  I added a Job Variable Condition to each Notification to decide whether this is the correct delivery step or not for this execution, this cuts way down on the amount of programming, but, makes the job itself harder to maintain.

Thanks again,