tag:blogger.com,1999:blog-6140199022860280334.post5643089866539919767..comments2024-03-29T06:37:56.706+00:00Comments on Bob Buzzard Blog: One Trigger to Rule Them All? It Depends.Bob Buzzardhttp://www.blogger.com/profile/07815472992351343395noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6140199022860280334.post-29078096200097196952017-05-14T03:48:46.022+01:002017-05-14T03:48:46.022+01:00If we are writing code in favor of Admin Guy then ...If we are writing code in favor of Admin Guy then your approach is the good one. But let them ding into code and feel the pain of code reading ;) Anonymoushttps://www.blogger.com/profile/12001411893793810340noreply@blogger.comtag:blogger.com,1999:blog-6140199022860280334.post-27030012745920805712017-03-21T18:03:22.471+00:002017-03-21T18:03:22.471+00:00Nice one, I was thinkg abt the same... :PNice one, I was thinkg abt the same... :PRajendra Singh Nagarhttps://www.blogger.com/profile/10352445423126298511noreply@blogger.comtag:blogger.com,1999:blog-6140199022860280334.post-84140243309799630522017-03-12T16:52:03.888+00:002017-03-12T16:52:03.888+00:00Hi Bob, largely I agree with your points. However,...Hi Bob, largely I agree with your points. However, my thought process is, why do we even need an administrator to look at the trigger code? Most commonly, an event handler in an object trigger is doing more than one job. So, simply by switching it off, we just stop all the functions. Rather, I believe, in such scenarios we can come up with a configuration based approach to enable/ disable the functionalities. By no means, I am suggesting it to be the best approach, but the intention is to avoid admin to look under the hood.Anshul Vermahttps://www.blogger.com/profile/08108189820154378688noreply@blogger.com