RecordPoint is a global records management solution provider that gives businesses the ability to manage records from multiple services and platforms reducing the cost and complexity of records management.
In 2018, RecordPoint approached CoSource to build an Exchange Online Connector for their Records365 platform.
At a high level the connector had to perform the following functions:
Manage records from multiple services and platforms reducing the cost and complexity of records management
Build an Exchange Online Connector
Allows submission of records, aggregations, audit information and
binaries into Records365
In developing the connector, CoSource had to meet a number of key requirements:
A Records365 Connector is a software component that interacts with a content source in order to locate and submit records to the Records365 records management platform, and which the platform can use to manage the content back in its source.
For this purpose, the Records365 platform hosts a Connector Framework, which each connector must integrate with in order to perform their function.
This framework is comprised of HTTP API endpoints that both internal and third-party developers can use to create connectors to any accessible content source, while imposing as few restrictions on how those connectors are designed and implemented as possible.
The Connector Framework is made up of the following components:
The framework also includes the Records365 Azure AD application, which is used to authenticate our product to all configured Connectors using an OAuth 2.0 consent flow.
All connectors at a minimum must implement the following:
The Connector Framework processes submissions of content from a connector, and at present requires one operation that modifies content in the content source – deletion of disposed content.
The Connector was implemented as a set of microservices which ran on top of Azure Service Fabric to take advantage of its scalability and reliability.
The Configuration microservice maintained the tenant’s configuration and auth information in conjunction with Records365 which included a user interface component.
The Monitoring microservice monitored the Exchange online content source for new messages and changes, then submitted them to the messaging API for processing.
The Submission microservice digested and transmitted the data from Exchange online source to Records365
The Destruction microservice was in charge of executing the destruction orders from Records365 to Exchange online.
The Messaging API provided a central point through which all content flowed so it was maintained until it was safely stored in Record365 thus providing dead lettering functionality.
Lastly, the connector was accompanied by a bulk load script which allowed for the rapid onboarding of new customers.
The connector was pivotal in maintaining Record Point’s position of a global custodian of record management. The feedback from both Record Point and their customers was extremely positive, with the CEO personally thanking the CoSource team for the excellent work.
To find out more about the connector or Records365, please visit –