The Salesforce receiver and configuration names are sfsoap and SalesforceSoap, respectively. This leads to Salesforce URIs of the form https://{host}/api/webhooks/incoming/sfsoap/{id} with an MS_WebHookReceiverSecret_SalesforceSoap application setting or WebHooks:SalesforceSoap:SecretKey:{id} configuration values (for Core).
The Salesforce receiver is inconsistent in two ways:
It is the only receiver with different receiver and configuration names.
It is the only receiver that includes anything beyond the sender name in its names e.g. the GitHub receiver is just named github.
Suggest we use salesforce everywhere. Another option (that I like less) would be salesforceSoap everywhere.
Once we pick a new name (if any), should we update the ASP.NET WebHooks receiver? Next release will be a full release…
The Salesforce receiver and configuration names are
sfsoap
andSalesforceSoap
, respectively. This leads to Salesforce URIs of the formhttps://{host}/api/webhooks/incoming/sfsoap/{id}
with anMS_WebHookReceiverSecret_SalesforceSoap
application setting orWebHooks:SalesforceSoap:SecretKey:{id}
configuration values (for Core).The Salesforce receiver is inconsistent in two ways:
github
.Suggest we use
salesforce
everywhere. Another option (that I like less) would besalesforceSoap
everywhere.Once we pick a new name (if any), should we update the ASP.NET WebHooks receiver? Next release will be a full release…