I've been configuring a full install for a while now and am unclear on the notification possibilities. Below is an example of the process I would like. Is it possible?

1. UPLOADER uploads a new file in a directory with permissions for CLIENT
2. APPROVER is notified, logs in, approves the file
3. CLIENT is notified that a file is approved.

CLIENT gets notified of the file before it is approved. They cannot view it yet but they also don't know that it is waiting approval. It's just not there even though an email told them it was uploaded.

APPROVER gets notified of the file, but they aren't told that this is a new file that requires their action.

Maybe I don't understand all the possibilites of the notifications settings. Please let me know if you can help me understand.

Thanks, Ken

Hi Ken,

DMX does not (yet) have a full workflow engine in it. In fact I'd love to work on this but I'm also waiting to see what DNN does to avoid problems down the road. The design of the notification engine is therefore not that it permits something like you describe very easily. Instead it is designed around 'actions' or 'events' if you like. Most things that happen in DMX have an action 'name' like 'add', 'edit' or 'download'. Whenever the action happens in code a call to log & notify is made. The notification recipient list is determined as follows: all those that are subscribed to the entry, all those that are subscribed to the containing folder, and all the 'approvers' for that entry. The email to send is determined by looking up the action in Logging.ascx.resx. There the module will find an email 'key'. It's these keys that you maintain in the interface through 'notifications'. If no key is found, then no notification is sent (like for download).

Peter