1. Introduction

The Tahiti Outlook Add-in (TOA) lets an Outlook user pick a message together with its attachments and store it into a digital archive (Damis). The user picks a document template and fills the template-defined attributes; that combination identifies the document in the archive and establishes the relation to the target entity it belongs to.

TOA replaces the original Tahiti desktop client’s Outlook integration, which was implemented as a COM add-in. The new component drops the COM dependency in favour of a web-hosted task pane built on the modern Office JavaScript API, which works in both new and classic Outlook, on desktop and on the web.

1.1. Components

There are two deployable parts; both are produced by the same root Maven build and shipped as separate release ZIPs.

TOA server (TOAServer)

Spring Boot 3 / Java 21 backend. Receives uploaded messages and attachments, stores them on disk under a per-domain data root, and forwards the assembled document batch to the Damis storage server. See Installing TOA server for installation and Configuration for configuration.

Outlook add-in (TOAClient)

Web-hosted task pane (TypeScript, packaged with webpack). Runs inside Outlook through the Office JavaScript API. Customer deployment is per Hosting the task pane (reverse proxy in front of the static bundle) and Centralized deployment (Microsoft 365) (rollout via the Microsoft 365 admin center).

The two parts share a single OpenAPI contract generated from the TypeSpec specification in the apispec module; operators do not need to think about the spec, but it is the reason a server upgrade without a matching client upgrade is generally safe.

1.2. System requirements

1.2.1. Server side

  • Operating system - Linux. No Windows server build is provided.

  • Java runtime - JDK 21. The fat jar in the release bundle is built against Java 21 and will not start on an older JRE.

  • Storage - any local filesystem writable by the service account. Sizing is dominated by the retention window times the daily upload volume; see Server settings (dataRetention) and On-disk layout.

  • Network - the server needs:

    • outbound access to the Damis storage server URL configured per domain (and, optionally, to a remote cmserver template URL), and

    • a publicly reachable HTTPS endpoint in front of it so the Outlook add-in running on user workstations can call the API. TLS is terminated by a reverse proxy, not by the server itself - see Hosting the task pane.

1.2.2. Client side

  • Outlook - new Outlook for Windows, classic Outlook for Windows, Outlook for Mac, or Outlook on the web. No specific Exchange or Microsoft 365 plan is required; the add-in does not call Exchange or Graph directly.

  • Office JavaScript API - Mailbox requirement set 1.15. Older hosts without this API level refuse to install the add-in (a clean failure mode rather than a silent degradation).

  • Mobile - Outlook on iOS and Android is not supported.

1.3. Audience

This documentation is written for administrators deploying and operating TOA at a customer site. It assumes shell access to the server host and Microsoft 365 admin rights for centralized add-in deployment.