Hello everyone! I came across a blog post at gokubi.com ( http://gokubi.com/archives/two-interesting-ways-to-architect-apex-triggers ) about some interesting ways of architecting Apex Triggers. We have developed a lot of logic in Apex Triggers and ended with some really nasty code in some scenarios; this post got me thinking about new ways to architect triggers using a more object-oriented approach. So just to follow the thoughts in this post I'll show you what I did to organize our triggers and it has been working pretty good so far. NOTE: Please refer to the code section below //Step 1 I started by creating an Apex Class to replicate some of the triggers functionality... //Step 2 The next step will be to start coding our Apex Class that will perform all of the logic in our triggers, so let's say the we are building a trigger for My_Object__c custom object. //Step 3 And finally, we just need to create the Apex Triggers that will just initialize our Trigger class and initialize

Salesforce's Spring '10 is packed with some really nice enhancements, new interface, code scheduler, no limits in collections, and more! For more information go to: http://developer.force.com/releases/release/Spring10 Here's a small demo of how code scheduler works: