Difference between revisions of "Interfaces Dolibarr toward foreign systems"
Jump to navigation
Jump to search
PolyglotBot (talk | contribs) m (Import interlang links (links to translated versions of this page in other languages) from Multi Language Manager table.) |
|||
Line 1: | Line 1: | ||
+ | <!-- BEGIN origin interlang links --> | ||
+ | <!-- You can edit this section but do NOT remove these comments | ||
+ | Links below will be automatically replicated on translated pages by PolyglotBot --> | ||
+ | [[fr:Interfaces_Dolibarr_vers_exterieur]] | ||
+ | [[es:Interfaces_Dolibarr_hacia_el_exterior]] | ||
+ | <!-- END interlang links --> | ||
+ | |||
{{TemplateDocDevEn}} | {{TemplateDocDevEn}} | ||
Dolibarr provides two simple mechanisms to interface Dolibarr with an external system on the behave of a Dolibarr event : | Dolibarr provides two simple mechanisms to interface Dolibarr with an external system on the behave of a Dolibarr event : |
Revision as of 13:20, 23 July 2019
Dolibarr provides two simple mechanisms to interface Dolibarr with an external system on the behave of a Dolibarr event :
- Triggers - a mechanism to activate your own code when Dolibarr executes an action (for example, creation of invoice, edit of a user, delete of an order, ...)
- Hooks system - an interface to integrate your own code in an entry point of Dolibarr
For more information on the opposite mechanism (allow an external system to interface with the Dolibarr system and use the Dolibarr's datas), see Interfaces from foreign systems toward Dolibarr).