|
The prior answer is correct, a workflow or trigger would be the usual way to do this. Unfortunately Content does not support workflow yet, but did recently add support for triggers on a couple of the content objects. The Content data model is a little funky at first. It'll help to review the Content ERD in the Webservices API Docs. If you're only looking for just brand new documents, look at creating a trigger on the ContentDocument object. If you're looking to handle uploads of updates to existing documents you can put a trigger on the ContentVersion object. Before you go down that road you really should check out the standard subscription features of content. They support getting notifications when new content is added to a library or content pack. Would save you from having to do custom development and keep the user's themselves in control of their notifications. | |||
|
|
|
Triggers can be activated when based on a database object's status: before insert, after insert, before update, after update, before delete and after delete. Provided your uploaded files are going to be added to your database, they can be used to activate a trigger. So the question becomes, how do you manage your uploaded files? Do you have workflow rules you use to manage them before they're accepted into your database? If so, then I'd recommend you add a workflow rule to initiate the desired emails rather than coding a trigger. That would likely be the simplest solution for you since the files presumably need to be added to your database via some method. | |||||
|
