Webhook error

Hi Bob Bundy

This ticket is currently going through our QA process and will be released ASAP. Thanks for your patience on this one!

Hannah @ SugarCRM

"The fixed in release has been updated to ‘11.1.0’, which is tentatively scheduled for release in Q3 of this year."

When will On-Site instances get the fix? Which release? 12.0.0 or 11.0.x?

What I cannot understand, is the choice of waiting for months, while the task might be solved within an hour with logic hook configuring ...
It looks like issue severity is not very high for both - subscribers and the vendor.

Sorry, I don't understand what do you mean.
You can configure WebLogicHooks. You have to program to use logic hooks. Big difference imho.

When I create a bug report, I normally not expect to wait 1.5 years until the issue is fixed.
After a while you live with it, and you (at least me) still expect "they"/Sugar will fix it with the next minor release.

Besides that you don't want to invent the wheel again. It's not just throwing some json to a web server using curl. You would also have to program error handling, in case the web server is not available, retries(job scheduler?) ... and so on.

Btw, at the moment WebLogicHooks are always successful, no retries and no errors will be reported. Jobs are always done successful:
portal.sugarondemand.com/

As I see from your question, companies got used to think that creating logic hooks in Sugar demands developer's efforts

It looks like subscribers don't know that for the last 4 years logic hooks may be configured by skilled Sugar admins with a no-code Logic Builder tool as I mentioned in the example above (including configuring of authorization and processing of errors if the case demands this)

I'm trying to say that the business task this forum starts from, could be solved with no development and very fast- with no suffering for months from the issue articulated here

Thanks for mention this tool. I was not aware of it and I will look at it.

Regarding this bug, unfortunately it doesn't make sense to me to install a new, not tested, pricy tool, because a Sugar feature has a bug. I mean how many tools will I have in 2 or 3 years when I try to replace the not working SugarCRM code with 3rd party code? 

I always try to solve the root cause of a problem.
With each additional tool I get additional complexity, dependencies, higher testing and maintenance effort and probably extra costs too.

Thanks for mention this tool. I was not aware of it and I will look at it.

Regarding this bug, unfortunately it doesn't make sense to me to install a new, not tested, pricy tool, because a Sugar feature has a bug. I mean how many tools will I have in 2 or 3 years when I try to replace the not working SugarCRM code with 3rd party code? 

I always try to solve the root cause of a problem.
With each additional tool I get additional complexity, dependencies, higher testing and maintenance effort and probably extra costs too.

Sometimes solving others bugs is not in our power, however we are in power to choose the way to deliver  the priority business task for reasonable efforts.

Luckily, Logic Builder is cloud-based, so need  to install anything to benefit from configuring - just sign in to logicbuilder.integroscrm.com,  upload custom metadata, design logic hook and then deploy a solution designed via Module Loader. 

Since the tool is not a part of Sugar, it is not included into subscription - that does mean extra cost.

However, the annual access to the environment cost for the compaly less then 3 mandays of Professional Services in regular the US/UK/EU rates, while the Logic hooks designed with the tool are never charged in any way. 

You will be surprised that custom solution for Sugar may not need regular development cycle even if designed from the scratch