Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Integration via webhooks

This article discusses things to consider if you plan to use webhooks in Hornbill for integration.

Before you begin

Custom fields in Service Manager

If you plan to use webhook services in your Hornbill implementation, then it is important to consider how you use your custom fields.

If you want to use custom field values in the webhooks, you should reserve the first 30 custom fields for those values that need to be expressed for webhook triggers. While in Service Manager there are 80 custom fields, the webhook options in the trigger expression only go up to Custom 30.

Triggering webhooks in Hornbill

In Hornbill, webhooks function on entities. Because webhooks are entity-bound, you cannot trigger a webhook for one entity on an event in another entity. Consider this when making use of the custom fields available for webhooks, and when creating your trigger expressions.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document