TANSS
TANSS IT Service Management Integration
The TANSS integration connects ELONIQ with the TANSS IT service management system. It synchronizes company and device data, enables ticket management and automatically creates DMS folders for customers.
Overview
The TANSS integration provides a comprehensive connection to the TANSS IT service management system. The integration synchronizes business data and enables automatic linking of documents with customers, devices and tickets.
Core Functions
- Data synchronization — Companies, employees, tickets, ticket statuses and devices are regularly synchronized and available as database tables.
- Folder synchronization — A folder is automatically created in the DMS for each TANSS customer. Template-based naming with variables.
- Device mapping — Link TANSS devices with DMS folders for automatic document assignment.
- Ticket integration — Create, update and comment on tickets directly from ELONIQ.
Features
- Company management — Synchronize companies, employees and contact data from TANSS.
- Ticket management — Create, update and comment on tickets. Internal and external comments supported.
- Device management — Retrieve devices from TANSS and link with DMS documents (device mapping).
- Folder synchronization — Automatically create DMS folders for each TANSS customer with template-based folder names.
- Database adapter — Provide TANSS data as tables (companies, employees, tickets, devices) for other modules.
- 2FA support (TOTP) — Automatic TOTP generation for TANSS instances with two-factor authentication.
- Intelligent caching — Companies, employees, ticket statuses and devices are cached with configurable TTL.
- Exponential backoff — Automatic retries on network errors with exponential delay.
- Time tracking — Retrieve time entries from TANSS for documentation and billing.
- Template variables — Dynamically generate folder names with variables like
{CustomerName},{CustomerNumber},{City}.
Usage
- Open integration — Navigate to Integrations > TANSS in AdminUI.
- Configure connection — Enter base URL, username and password. For 2FA: provide TOTP secret.
- Test connection — Test the API connection and check the connection status.
- Activate functions — Select the desired functions: Database Sync, ticket creation, Auto Cache.
- Set up folder synchronization — Define a folder template, the base folder in DMS and the sync interval.
- First synchronization — Start the first synchronization manually and review the results.
- Configure device mapping — Optional: link TANSS devices with DMS folders.
- Monitor status — Regularly check sync statistics and cache status.
Best Practices
- Set up TOTP — If your TANSS system requires 2FA, configure the TOTP secret for uninterrupted authentication.
- Adjust cache TTL — Shorten the TTL if company data changes frequently. The default is sufficient for most scenarios.
- Test folder templates — Test folder templates with a small customer group before enabling full synchronization.
- Keep retry policy — The default retry settings (3 attempts, exponential backoff) are optimal for most TANSS instances.
- Maintain device mappings — Regularly review device mappings to ensure DMS folders are correctly linked.
- Activate functions selectively — Only enable the functions (DB sync, tickets, cache) that are actually needed.
Examples
1. Basic TANSS Connection
Base URL: https://customer.tanss.de Username: api_user Password: *** Functions: Database Sync, Auto Cache
2. TANSS with 2FA and Ticket Management
Base URL: https://customer.tanss.de Username: api_user Password: *** TOTP Secret: JBSWY3DPEHPK3PXP Functions: Database Sync, Create Tickets, Update Tickets, Auto Cache
3. Folder Synchronization to ELO
Folder Template: {CustomerName} ({CustomerNumber})
Base Folder: ¶Customers¶
Sync Interval: 60 minutesA folder is automatically created in ELO for each TANSS customer, e.g. ¶Customers¶/Company ABC (K-001).
4. Template with Variables
Available Variables:
{CustomerName} → Company ABC Ltd
{CustomerNumber} → K-001
{CompanyID} → 42
{City} → Berlin
{Year} → 2026
{Month} → 03
{Day} → 02