Is it possible to create a global after_save logic hook?

Question

I need to create an after_save logic hook that will run on all or a list of modules (array of module names to check) when a record in any of them is saved. Instead of copying and pasting logic hook definitions to each and every module, is there a way to create such a hook globally? What kind of files should I put where? I understand that global logic hooks are placed in ./custom/modules/logic_hooks.php , but is there any way to trigger a global logic hook on the save actions of any module? I can see that an after_save logic hook in that logic_hooks.php file does work, but it does not seem right for my situation since in my log I can see that it triggers several times on a simple page load. Is this because SugarCRM is based on modules and making a global after_save logic hook makes it trigger on many underlying system modules that are not even touched by the user directly? I wonder if it would cause performance implications if I simply had a condition that allows the hook to only continue if the module that triggers it is in a list of allowed modules. Edit: Actually the problem I have now is that I am unable to log function arguments and whenever I try to Sugar tells me "there was an error while connecting to the server". According to the documentation the after_save logic hook should have arugments $bean, $event and $arguments, but like I said - none of them can be logged and when it tries to log it the saving is actually completely prevented.

Artis Plocins · Accepted Answer

I've managed to put this all together after numerous tests and experiments using any information I could find around. Also, the developer documentation does not list the actual way that team sets and team manipulation for beans works. So, to create a global module hook: Create a logic hook definition in custom/modules/logic_hooks.php as per the global hooks described in documentation, but use one of the module hook types like after_save or before_save Create a logic hook file as usual (normally placed in custom/modules/logic_hook_name_example.php) NOTE: Within the logic hook method take care not to log large variables or the system will be impaired You can both get and set the primary team and team set IDs using $bean->team_id and $bean->team_set_id properties respectively Since the purpose of this logic hook for me was to manipulate teams and team sets, I wrote that as a full example.

Artis Plocins · Answer

If you have a child-parent relationship then perhaps you want an after relationship add logic hook rather than a before or after save. Generally each of the records has to be saved (so they each have an ID) and then related to each other. In the arguments of an after_relationship_add logic hook you have a $bean (the bean of the record you are on) and in the arguments 
 $ arguments [ ' related_module ' ] and $ arguments [ ' related_id ' ] 
 will give you the module name and id of the related record so you can get the bean of the record you just related to your $bean. 
 $relatedBean = BeanFactory::retrieveBean($arguments['related_module'], $arguments['related_id']) 
 Manipulating Teams on the $relatedBean to match the $bean should then be relatively simple if you follow some guidelines you can find here: 
 https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_11.0/Architecture/Teams/Manipulating_Teams_Programmatically/index.html 
 FrancescaS