Customer Integrations

Integrating ActiveControl with other 3rd Party tools has grown significantly in popularity at Basis Technologies over the last couple of years, as SAP customers strive to use best of breed tools as part of their end-to-end toolchain.

Since ActiveControl 8.50 – several customers have chosen to setup ActiveControl integrations with various 3rd Party tools themselves. These Integrations has been developed by the Customer – and are not part of ActiveControl out-of-the-box product. These integrations are mentioned in these Release Notes so that if any other customer is interested in such an Integration, you can contact Basis Technologies and we can facilitate some discussion/collaboration between you and the other Customer that did the work.

4ME

During 2021, a new Basis Technologies’ customer requested an integration between ActiveControl and the 4ME (https://www.4me.com/) ticketing tool they were using. This was not a tool Basis Technologies had previously created an integration with. Since the customer wanted a particularly custom solution, they ended up doing the Development themselves – and so there is no new out-of-the-box Integration capability available as part of ActiveControl 9.00. The integration was solely to automatically create the Business Tasks. It was not a bi-directional integration to update 4ME ticket statuses as the Business Task deployment status changed as Transport Forms move through the ActiveControl workflow.

Microsoft Azure DevOps

During early 2022, a new Basis Technologies customer requested an integration between ActiveControl and Microsoft Azure DevOps (ADO). This was not a tool Basis Technologies had previously created an integration with. Since the customer did not want to use Node-RED – they instead chose to use Mulesoft to provide the middleware between ADO and the ActiveControl APIs. This integration was used to create Business Tasks at the appropriate point of the ADO ticket – and then send status updates back to ADO as the Business Task deployment status changed as the associated Transport Forms moved through the ActiveControl workflow.