• Norman Bechler

Connecting Microsoft Teams and SharePoint with Records Management Systems like ELO ECM

With the cloud-based frameworks like the "b.Hub", companies can link ELO Enterprise Content Management solutions with Microsoft Teams and SharePoint. This simplifies business processes. The "b.Hub" interface works on the basis of Microsoft Azure.

Document processing systems can be linked with "b.Hub". Project or process managers can define where documents are stored, processed and archived at what time and with what information. It is also possible to transfer documents from the Microsoft Teams collaboration tool and Microsoft SharePoint to the ELO system.

Digitizing business processes in practice

The following "b.Hub" templates for practical use of the interface are currently available:

- Archiving SharePoint documents in ELO ECM

- Transfer of documents from Microsoft Teams into ELO ECM

- Storage of Microsoft Dynamics 365 documents in ELO ECM

- Publishing of ELO documents in SharePoint

"b.Hub" as a technological "bridge builder"

Modern work in the sense of a digital workplace only succeeds when processes run smoothly and efficiently. This requires that a work process is considered as a whole across several systems. Interfaces such as "b.Hub" are the technological "bridge builder" for this. The technology enables data and documents to be transferred from one document-processing system to another in an automated or rule-based manner.

Application scenarios for the b.Hub SDK include:

Archiving SharePoint documents into the ELO ECM archive.

Define which documents (e.g. by document type) should be transferred from your SharePoint libraries to your ELO archive. This process can be triggered by different triggers, e.g. after the completion of a project, with the assignment of a certain value, after a certain period of time or at regular intervals.

Archiving Microsoft Teams documents into the ELO ECM archive.

With the introduction of Microsoft Teams, many document sources can quickly emerge, most of which are not centrally reviewed for retention requirements. Define with a policy that closed teams should be checked first and decide which content incl. metadata is subject to retention and thus automatically transferred to your ELO archive.

Archiving Microsoft Dynamics 365 documents to the ELO ECM archive.

You have documents created in MS Dynamics 365 Apps that you want to archive? Via b.Hub, these invoices, orders or quotations can be automatically stored in your ELO archive with keywords.

Publish ELO documents to SharePoint.

Publish documents stored in ELO on the intranet either as a copy or as a link to the ELO document. Search options and permissions are then defined via SharePoint.