We live in a highly competitive world where, in order to become a leader, organizations need a differentiator that sets them apart. That could mean presenting new services, better user experience, different approaches for different audiences, finding new channels to convey their message, keeping their audience engaged in a consistent manner, and more.
An effective “digital presence” is one of the most important pillars of any differentiation strategy. This means providing delightful, friction-free experiences that engage customers and establish a long-term relationship. And what is the key technology that enables this? Integrations.
Importance of Integrations
In the modern enterprise landscape, companies maintain a large set of digital platforms. Usually, each one addresses a particular use case, with most companies having at least five main platforms:
- Financial information - SAP, Netsuite, Dynamics, etc.
- Customer information - Salesforce, Dynamics, etc.
- HR information - PeopleSoft, Workday, etc.
- Service Desk - ServiceNow, Zendesk, Jira, etc.
- Industry-specific systems of records, such as in insurance, healthcare, banking, etc.
- Analytics - usually non-relational databases like Snowflake, MongoDB, etc.
Each of these platforms function as the master source of truth for their respective area. Connecting them so that they function well together is a must for every modern company that wants a competitive edge, but it is also one of IT’s greatest challenges. Gartner estimated that integration work would account for 50% of the time and cost of building a digital platform through 2020.
During 2020, the urgency to connect these systems has increased dramatically as a result of the COVID-19 pandemic. Organizations have been challenged to reinvent themselves, seeking different channels to get to their customers, and developing online stores because the way they operated didn’t comply with the new social-distancing and lockdown reality. This, in turn, has required extensive integration to be put in place.
An online store, for example, needs data from the product database (product details, stocks, etc.), online payment gateways, and connectivity to order management systems. But what if some of these are in-house systems, built long ago, that didn’t previously need to integrate with other applications? Being able to respond quickly to changing business conditions can become difficult.
Integrations also play an important role in optimizing costs and increasing efficiency. Data silos are all too common in the enterprise, leading to decisions being made based on incomplete data, or causing delays as data is tracked down in other systems. Having a Data & Integration Strategy in place to manage multiple systems of record allows businesses to break down the silos and look at the big picture, instead of looking at each system individually. Having a consolidated view of all company data, figures, and processes means better decisions can be made, at the speed the business requires.
A Pain for Developers
Enterprise systems of record (ERPs, CRMs, IT, HR, etc.) got the integration memo many years ago, with most now providing APIs, usually web services, that allow communication with the “outside” world.
However, actually using APIs from different systems spread across an organization is no easy task. According to the 2020 OutSystems survey “The Speed of Change: How Fast Are You?”, in which 2,200 respondents (not OutSystems customers) ranked their top four reasons for application delays, ”integration with legacy systems/lack of APIs” was ranked highest by the respondents experiencing the greatest delays.
It’s difficult because vendor APIs vary significantly, which means there are many considerations for the developers tasked with using them:
- What is the API protocol? REST, SOAP, GraphQL, or something older and proprietary?
- What is the authorization mechanism? End-User OAuth, Server-to-Server (JWT), APIKey, or simple basic authentication?
- What configurations are needed? Many systems have to be configured to accept requests from “outside”. For example, in Salesforce, in order to get data using REST APIs, the connected app must be created with the right permissions.
- Are there encoding considerations? Does communication require special encoding? For example, SAP OData services require that each parameter is preceded by a “$” (dollar sign).
- Is the API performance acceptable? Can the legacy system API cope with B2C-scale mobile application requirements? Most likely not, so developers must consider other options like having a local replica.
- Is the API externally available? Is there any particular infrastructure/network configuration that needs to be considered, a whitelist URL or IP address in the firewall?
Integration with OutSystems
Here at OutSystems, thanks to our almost 20-year track record, we know a thing or two about complex integration scenarios. We have focused on making it easy to integrate with any external system of record, regardless of the communication protocol. Here are some of the ways our platform helps:
- Connect to any REST or SOAP by simply entering the endpoint URL. OutSystems introspects the specification (WSDL or Swagger) and automatically generates OutSystems code.
- Connect to any external database right out of the box, even if it’s an old DB2 database running on AS400.
- Create your own .NET code connector to integrate with any homegrown system.
- Expose your own REST or SOAP web services with a couple of clicks.
- OutSystems provides a complete governance model that can be connected to your own identity management systems to secure all API use.
- OutSystems handles instrumentation of all your inbound/outbound web services so troubleshooting APIs is simple.
- Built-in dashboards and monitoring allow proactive identification of any API-related issues.
You can learn more about OutSystems integration capabilities here.