bja

added email (salesforce)

Thanks John ... that does not appear to be tied to different profile or user. The isactive can be come very cumbersome for a large Org ( given the granularity...

It would appear to be cleaner to modify the ctor (ApplicationSObjectDomain) ... and enable/disable trigger via the Hier. Custom Setting ... something like ....: // disable configuration based on hier....

Hmmm ... if you are referring to the _alternate suggestion_: _'You could also program the functionality to pivot by custom setting into the Domain Process actions.'_ that would appear to...

I think I can still perform the following (interfaces, di and base classes in a sub-dir); _**deferring**_ at this time the handling of custom settings ( whether via the _ApplicationSObjectDomain_...

Without getting to fancy ( include or exclude sobjects or support of regex). For example, in custom setting field , create a field **disableTriggerByDomain**. This is would be a (comma,...

OK ... the disableAll in fflib (_fflib_SObjectDomain.getTriggerEvent(_domainClass_).disableAll(_); did not disable invocation for all when coming thru the ctor. As a result, after reading the custom setting, I set a flag...