Middleware is software that lies between an operating system and the applications running on it. Essentially functioning as a hidden translation layer, middleware enables communication and data management for distributed applications.
As organizations move their digital infrastructure to the cloud, many are discovering that integration poses a significant challenge – possibly finding themselves in the middle of an ecosystem with applications and services siloed off and disconnected from each other.
Introduction to the role an Integration Platform plays in managing workflows of data between ITAS and 3rd party applications and services using APIs
A common scenario for our Liquid Products customers, is one where goods are moved from and to Stock Tanks at locations (Terminals) that use Weighbridges to measure the weight of the trucks on entry and exit.
The overall purpose of the ITAS API is to provide external access to the ITAS system, both in terms of data and functionality. The API endpoints provide that point of contact and allow us to create a layer between ITAS and external usage.
Focusing on components and methodologies that support integration projects between ITAS and other accounting systems. Applied to a scenario in which ITAS is used to generate the invoicing and the accounting activity is performed in an alternate system.
Technical exploration of the Publish-Subscribe (PubSub) model implemented as part of the events notification framework. Covers the use of Topics and the Events API; a series of endpoints used to publish, subscribe and manage notifications.
This video reviews the ITAS API (REST Application Programming Interface) and provides working examples using the POSTMAN API Testing tool.
Each Government e-Invoice mandate will likely have its own specific requirements regarding data, formatting, messaging, security and workflow. Traditional approaches that involved tightly integrating ITAS processes to each mandate are not only costly to develop and support, but are also vulnerable to subsequent changes at the Local Tax Authority end.
Enterprise clients have their own IT (development) capability allowing them to fully utilise the open architecture provided by the ITAS API.
Exploration of the role of the API for enabling integration of ITAS with cloud-hosted and on-premise applications and services
For the purposes of this Use Case, the focus is on Cash Management where Invoicing is generated within ITAS but the Invoice Authorisation (pre-payments for example) is managed in a 3rd party Financial Management system.
This article highlights the issues faced by organisations who receive data feeds from their brokers and/or trading terminals.
For the purposes of this Use Case, the focus is on Cash Management where Invoicing is generated within ITAS but Accounts Payable/Receivable facilities are managed in a 3rd party Financial Management system.
Data Modify Service (DMS) is a powerful REST compliant API interface enabling you to create, amend or remove ITAS data using a simple query language (GraphQL). This technology is designed around the relationships between the Entities to enable a more sophisticated data search capability.
API-enabled access was once the sole preserve of Enterprise operations, i.e. those with in-house development capability. In order to bridge the gap and allow citizen-driven API integrations we have introduced the OData (Open Data Protocol) Service.
A common requirement for customers working with physical stock within a warehouse location, is the ability to identify and track items through ITAS. Although the software does not directly communicate with scanning devices, by providing an API it does allow scanning devices and any proprietary software to request and update information held against stock items.