Difference between revisions of "Integrations"
From Charitylog Manual
| Line 3: | Line 3: | ||
* To streamline multiple processes | * To streamline multiple processes | ||
* To negate the need to enter the same information twice in 2 systems | * To negate the need to enter the same information twice in 2 systems | ||
| − | === | + | ===Streamlining multiple processes=== |
An example of this is the [http://www.Loqate.com Loqate] integration. This adds a button next to each postcode, and shows a list of matching addresses to save time when creating client records. | An example of this is the [http://www.Loqate.com Loqate] integration. This adds a button next to each postcode, and shows a list of matching addresses to save time when creating client records. | ||
| + | ===Avoiding double entry=== | ||
| + | We're systems overlap, e.g. a mailing system and a CRM, an accounts system and a CRM, or a care management system and a CRM, identical data will often need to exist in both systems. | ||
Revision as of 16:09, 21 April 2020
Integrating Charitylog or Crossdata with other systems
Integrations are where 2 systems "talk" to each other, for 2 main reasons:
- To streamline multiple processes
- To negate the need to enter the same information twice in 2 systems
Streamlining multiple processes
An example of this is the Loqate integration. This adds a button next to each postcode, and shows a list of matching addresses to save time when creating client records.
Avoiding double entry
We're systems overlap, e.g. a mailing system and a CRM, an accounts system and a CRM, or a care management system and a CRM, identical data will often need to exist in both systems.
