ERP and other integrations

This chapter summarises what TAS 5.19.12 offers for connecting to accounting/ERP systems and databases: what is a ready-made part of the product (core or plugin) and what is only a pattern that a template builds itself from general-purpose tools.

IntegrationStatus in 5.19.12How it works
Pohoda (Stormware)Not built inThe template calls the Pohoda mServer through the general-purpose calculation module curl (HTTP) and the helper functions lib.xmlToJson, lib.jsonToCsv, lib.updateDTFromCsv for working with XML and CSV. The mServer address is a variable or constant in the template. Store the login credentials in the Vault and read them from there in the calculation, not as plain text in the template.
Money S5Not built inA similar pattern to Pohoda – GraphQL queries through the same curl module.
ISDOCIsDoc pluginReads ISDOC invoices from an .isdoc file, an .isdocx container or a PDF with embedded ISDOC and stores them in a variable. In the template, use the ISDOC Reader Smart Event (see Smart Events for integrations) or the corresponding function in a calculation. Reading is purely local; the plugin makes no network calls.
TAS2TAS (calling another TAS instance)Core + apiExtensions pluginOne TAS installation controls cases in another through its REST API: POST /plugins/api-extensions/start-process creates a case from a header and sets variables in a single database transaction (either all of it succeeds or nothing does), and POST /dms/upload adds a document to it. The calling side authenticates with an API token or an OAuth client – see API tokens and OAuth clients in practice.
DB ViewCore (overviews)An overview can be connected to a custom database view (SQL VIEW) instead of the standard case and variable tables – you set the source table and column mapping when creating or editing the overview. The view itself is prepared in the database by the DBA; TAS only reads from it.

ISDOC – plugin settings

The only configurable parameter of the IsDoc plugin is the maximum size of an unpacked .isdocx container (default 64 MB), as protection against overly large files. You set it in Administration › Plugins › IsDoc › Configuration.

TAS2TAS – things to keep in mind

  • The start-process call runs in a single transaction: if anything fails (invalid variable, missing header), not even a partially created case is created.
  • Authentication is the same as for any other REST API integration – either an API token of a system user or an OAuth client. There is no special “TAS2TAS” authentication mechanism.
  • To transfer documents between instances, use /dms/upload, not file copying outside the API.

The opposite direction: exposing TAS data externally

The expose DB plugin (integration category) does the opposite of DB View – it exposes a selected database table or view as a read-only REST endpoint for an external system. It is configured with named connections in Administration › Plugins › Configuration (table name, columns, filterable columns, and optionally a custom database connection). It is not the same as DB View in overviews – the two features handle opposite data flows.

Pohoda and Money S5 require a custom design
Because neither Pohoda nor Money S5 has a ready-made connector in TAS, each such connection must be designed in a specific template together with a consultant – it varies depending on the ERP system version and on which data is to be transferred.

Related: Smart Events for integrations, Plugins, Overviews, REST API: login and basic calls.

DocuSign and electronic signatures

Smart Events for Integrations
Syca (opens in a new tab)

Powered by HelpDocs (opens in a new tab)