Trying to implement the popular Financialforce enterprise design patterns library, and not clear on if it provides baked in capability to prevent a trigger recursion. I've looked through the core classes for clues, re-read the docs and no clues so far. Given I dont have control over how the unit of work is initiated i.e. could be a batch job, and I know I need to make an update to records AFTER they hit the database, how would I prevent the recursion ? Should I just add a static var as per 'old' approach
Any suggestions would be most appreciated.