Thread Details
  • State Not Answered
  • Replies 6 replies
  • Subscribers 369 subscribers
  • Views 2149 views
  • Users 0 members are here
Forum Actions

Web Logic Hook on custom module not called

Paul Blasl

We are using the Web Logic Hooks functionality in case of two modules of ours.
During the development of an internal tool which is using the SugarCRM REST API as well, we decided to use the same Web Logic Hooks functionality, but instead of an already defined module we wanted to use it for a custom module made by the Sugar Studio/ Module builder feature.
We had some experiments and we've realised that the configured endpoint is not called.
I've looked over the documentation and I've found this page:
https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_10.2/Architecture/Module_Builder/#Adding_Custom_Logic_Using_Code
Which says that a custom module might need some additional coding and configuration if we would like to enable Web Logic Hooks feature, but it's not 100% clear to me what needs to be done from our side.

My question is, what should we do in order to work with a module made by Sugar Studio/ Module builder feature and Web Logic Hooks functionality together? How could we reach a point where we can listen to an after_save event with a module made by Sugar Studio/ Module builder feature?

Has someone experiments with defining WEb Logic Hooks for a customer module?

BR

Parents
  • 0 Sugar Employee Badge

    Hello Paul, 

    When using Web Logic Hooks the data is not sent instantaneously but rather queued and processed later by the Dispatch Web Logic Hook scheduled job.

    This means that the Cron needs to be enabled for the instance. 
    Can you confirm that the Cron is enabled on your tests? 

    Adding on that there are some documented defects that might explain this behavior, can you provide details on the exact Web Logic Hook that's not working so we can check if you are hitting any defect? 


Reply
  • 0 Sugar Employee Badge

    Hello Paul, 

    When using Web Logic Hooks the data is not sent instantaneously but rather queued and processed later by the Dispatch Web Logic Hook scheduled job.

    This means that the Cron needs to be enabled for the instance. 
    Can you confirm that the Cron is enabled on your tests? 

    Adding on that there are some documented defects that might explain this behavior, can you provide details on the exact Web Logic Hook that's not working so we can check if you are hitting any defect? 


Children
  • 0 in reply to Andre Serrazina

    I tried to create a Web Logic Hook on an instance which does have the scheduler activated.

    This is an example of a Web Logic Hook we have in place on an already defined module:

    (note: I changed the URL in this example for the screenshot - in our production system we have a valid URL in place)

    For testing we first tried to copy this web logic hook and set the custom module on the copied logic hook. However no action was caused when new data was created or edited on the custom module.
    Which made us thinking if web logic hooks in custom modules need additional coding/configuration.