Difference between revisions of "System Settings"
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
==Introduction== | ==Introduction== | ||
The System Settings focuses on two areas, the Advanced Settings and the Web Hooks. | The System Settings focuses on two areas, the Advanced Settings and the Web Hooks. | ||
| − | + | <br><br> | |
| − | == [[Advanced Settings]] == | + | |
| + | == [[File:advancedsettingsicon.png|text-bottom|link=Advanced Settings]] [[Advanced Settings]] == | ||
[[File:AdvancedSettingsCard.png|right|link=Advanced Settings]] | [[File:AdvancedSettingsCard.png|right|link=Advanced Settings]] | ||
The Advanced Settings provides access to all of the available settings within your instance. These offer a number of detailed configuration options to configure your instance just the way that you want it. | The Advanced Settings provides access to all of the available settings within your instance. These offer a number of detailed configuration options to configure your instance just the way that you want it. | ||
| Line 11: | Line 12: | ||
<br><br> | <br><br> | ||
| − | ==[[File:webhooksicon.png|link=Webhooks]] [[Webhooks]] == | + | ==[[File:webhooksicon.png|text-bottom|link=Webhooks]] [[Webhooks]] == |
[[File:WebhooksCard.png|right|link=Webhooks]] | [[File:WebhooksCard.png|right|link=Webhooks]] | ||
Web Hooks are a great way to integrate Hornbill with other applications that are accessible over the internet. Web Hooks can send information from Hornbill to another application as soon as a record is updated, rather than relying on scheduled imports or the continually polling for data. | Web Hooks are a great way to integrate Hornbill with other applications that are accessible over the internet. Web Hooks can send information from Hornbill to another application as soon as a record is updated, rather than relying on scheduled imports or the continually polling for data. | ||
A web hook is the opposite to an API call, a web hook is a call over HTTP from your Hornbill instance to a web endpoint of your choosing. Most application actions on a Hornbill instance can trigger an action-specific event when an action is performed. Hornbill can be configured to call to a web end point passing the action-specific data to the web service being invoked. This is a very powerful mechanism that enables true, near real-time integration with other business systems. | A web hook is the opposite to an API call, a web hook is a call over HTTP from your Hornbill instance to a web endpoint of your choosing. Most application actions on a Hornbill instance can trigger an action-specific event when an action is performed. Hornbill can be configured to call to a web end point passing the action-specific data to the web service being invoked. This is a very powerful mechanism that enables true, near real-time integration with other business systems. | ||
| − | |||
:* Event driven integration from Hornbill to an external source | :* Event driven integration from Hornbill to an external source | ||
Revision as of 04:05, 31 August 2016
Home > Administration > System > Settings
Introduction
The System Settings focuses on two areas, the Advanced Settings and the Web Hooks.
Advanced Settings
The Advanced Settings provides access to all of the available settings within your instance. These offer a number of detailed configuration options to configure your instance just the way that you want it.
- Search for Settings
- Restore settings to their default
Webhooks
Web Hooks are a great way to integrate Hornbill with other applications that are accessible over the internet. Web Hooks can send information from Hornbill to another application as soon as a record is updated, rather than relying on scheduled imports or the continually polling for data. A web hook is the opposite to an API call, a web hook is a call over HTTP from your Hornbill instance to a web endpoint of your choosing. Most application actions on a Hornbill instance can trigger an action-specific event when an action is performed. Hornbill can be configured to call to a web end point passing the action-specific data to the web service being invoked. This is a very powerful mechanism that enables true, near real-time integration with other business systems.
- Event driven integration from Hornbill to an external source
- Send data over HTTP to a specified web endpoint