Integration
The recommended way to communicate with Tempus Serva is through the webservice interface (REST).
Regardless of you are using the scheduled import services or the webservice interface, all restrictions from the solution models apply.
Scheduled data imports
The services runs in the context of a user (static), that can have restricted access just as any other user.
Database connection / SQL
PLACEHOLDER ARTICLE
Parsing XML data files
XML integration also handles task splitting and handling. Each file is split into multiple smaller requests, that are logged and handled individually. In that way an error in a single line, will not prevent the complete batch from executing.
Files are split in the following folder structure
- Tasks that are awaiting processing
- Tasks that have been processed
- Tasks processed with succes
- Tasks processed with errors
This allows for easy resubmission of problem data ("Tasks processed with errors"), by copying the file back to the preocessing folder ("Tasks awaiting processing").
Converting emails to data
The email import converts new emails sent to a certain account.
A few special email "values" can be mapped to solution fields
- Email: Senders address
- Subject: Email subject title line (text)
- Content: Text payload in email (rich text)
- Attatchments: Files attached to the email
After processing the emails they are marked as read at the server - regardless of succes/error status. Reprocessing can be invoked by changing the read status of the email in question.
Event driven data exports
PLACEHOLDER ARTICLE
Tempus Serva REST interface
The REST interface runs in the context of a user (dynamic), that can have restricted access just as any other user.
Credentials are provided with each system interaction, and its even possible to use your own credentials for testing.
Service operations
- Finding data
- Reading data
- Creating data
- Updating data