FieldLogs Integrations
FieldLogs is compatible with most integration ecosystems.
There are many scenarios where data from FieldLogs need to be passed on to third-party systems and vice-versa. Some examples are cited below:
FieldLogs collects digital signatures on Tasks. These records may need to be exported and sent to the relevant systems.
Disaster Recovery Strategies require FieldLogs to systematically export data to customer servers on the cloud or on-premises.
Data from customer ERP solutions need to be passed onto FieldLogs and vice-versa.
When the status of a FieldLogs Task undergoes a change, it is required to update the customer ERP solution.
When a Flag is raised on a Task, details of the Task and the issue need to be communicated to the relevant systems.
When a Flag is marked as resolved, details of the resolved Flag information need to be communicated to the relevant systems.
FieldLogs master database tables are synced with data from the master database tables in the customer servers. In some cases, FieldLogs master database tables pass data to the customer master database tables.
FieldLogs Integration with Boomi
FieldLogs currently uses Boomi as the integration platform.
The Boomi Atom is a light-weight, dynamic runtime engine that contains all the end to end components to run the integration processes. Boomi Atom can be installed in the Customer Premises or on FieldLogs' servers. Boomi Atom interacts with the Customer ERP systems using the appropriate Enterprise connectors. It interacts with FieldLogs using FieldLogs APIs.
The below illustration shows an example where the customer uses SAP as the ERP system.
 |
FieldLogs Light Integration Solution
With some legacy systems, FieldLogs also employs a light integration approach, where email alerts are sent to a dedicated support group when defined events of interest occur. It is up to the recipients to take appropriate action.