vivekmchawla / simple-trigger-pattern

Official repository of the Simple Trigger Pattern for Salesforce (STP).

##Introduction

This is the official public repository of the Simple Trigger Pattern for Salesforce (STP). This pattern was developed by Salesforce MVP Vivek M. Chawla (@VivekMChawla), a Salesforce Certified Platform Developer (Levels I and II), App Builder, and Advanced Administrator.

The Simple Trigger Pattern can be used to quick-start development of new triggers. It encapsulates several best-practices, including "One Trigger per Object", "No Business Logic in Triggers", and "Recursion Prevention Using Static Variables". The STP also facilitates adoption of the architectural best practice of Separation of Concerns.

NOTE: If you are looking for the Gist "snippet collection" of Simple Trigger Pattern files, you can find it here: bit.ly/SimpleTriggerPatternGist

##Contents

The following files are contained in this repository:

• LICENSE.txt
  • Copyright and license information
  • All code and documentation are distributed under MIT License
  • If you find this pattern useful, let me know @VivekMChawla
• README.md
  • The file you're reading right now
• TriggerHandler.cls
  • Apex virtual class
  • Core component of the Simple Trigger Pattern
  • Must be deployed to your org before implementing STP
  • Does not require customization before deployment
  • All trigger handlers implementing STP must extend this class
• TriggerHandlerTest.cls
  • Apex test class
  • Must be deployed to your org before implementing STP
  • Does not require customization before deployment
  • Provides 97% code coverage of the TriggerHandler virtual class
• SampleObjectTrigger.cls
  • Apex trigger template
  • Requires customization before deploying to your org
• SampleObjectTriggerHandler.cls
  • Apex class template
  • Requires customization before deploying to your org
• SampleObjectTriggerHandlerTest.cls
  • Apex test class template
  • Requires customization before deploying to your org

simple-trigger-pattern's Issues

Does pattern support Bulk DML retries when allOrNothing=false?

I think this is true after inspecting your trigger pattern. Looking for verification and suggesting you add to your documentation.

If doing a bulk DML operation such as Database.insert(sobjList,false), per the Apex documentation, if some records fail, Apex will attempt a second and possibly third retry on the failing sobjects.

You would not want the trigger recursion static variables to be remembered for the second or third retry as otherwise the retry logic will not execute one's trigger handler business logic.

I believe your pattern addresses this because on a retry, per the doc, the trigger refires which means the xxxObjectTriggerHandler will be reinstantiated for the retry set and thus reset the isXXXXFirstRun booleans.