Architecture

This page describes the technical architecture of the Q-Team Solutions Edit in Outlook app for Microsoft Dynamics 365 Business Central.

Architecture Overview

graph TB
    BC[Business Central] --> EIO[Edit in Outlook App]
    EIO --> AUTH[Q-Team Authenticator]
    EIO --> CA[Control Add-in]
    CA --> BROWSER[Browser]
    BROWSER --> OUTLOOK[Microsoft Outlook]
    OUTLOOK --> O365[Office 365]
    
    BC --> EMAIL[Email Engine]
    EMAIL --> TEMPLATE[Email Templates]
    EMAIL --> EML[EML File Generation]

Main Components

1. Business Central App

Location: src/ directory - App ID: 0e9ac084-9f49-46d3-b3d1-224b4e7dba0a - Publisher: Q-Team Solutions - Version: 27.0.46066.0 - Platform: Business Central 27.0+

Codeunits

Control Add-ins

2. Dependencies

Q-Team App Authenticator

• Required Dependency: Q-Team App Authenticator (version 27.0.46044.0)
• Function: Secure authentication and authorization
• Integration: Token-based authentication for API calls

3. Client-Side Architecture

JavaScript Components

Location: js/ directory

CSS Styling

Location: css/ directory - DropArea.css: Styling for drag-and-drop interface

4. Email Workflow Architecture

Process Flow

1. Initiation: User activates "Edit in Outlook" from Business Central document
2. Template Retrieval: System retrieves relevant email template
3. EML Generation: Creation of .eml file with document and template
4. Browser Download: File is downloaded to user's system
5. Outlook Integration: User opens .eml file in Outlook
6. Editing: User edits email in Outlook interface
7. Sending: Email is sent via Outlook/Office 365

EML File Structure

EML File
├── Headers (To, From, Subject, etc.)
├── Body (HTML/Plain text)
├── Attachments
│   ├── PDF Document
│   └── Additional files
└── Metadata

5. Integration Events

The app provides various Integration Events for extensibility:

OnBeforeGenerateEML

• Trigger: Before EML generation
• Use case: Custom validation or preprocessing

OnAfterGenerateEML

• Trigger: After EML generation
• Use case: Logging, archiving, postprocessing

Warehouse Shipment Events

• Specific events for warehouse shipment documents
• Support for complex document flows

6. Security Architecture

Authentication Flow

sequenceDiagram
    participant User
    participant BC as Business Central
    participant EIO as Edit in Outlook
    participant AUTH as Q-Team Authenticator
    participant O365 as Office 365
    
    User->>BC: Select document
    BC->>EIO: Trigger Edit in Outlook
    EIO->>AUTH: Request authentication
    AUTH->>EIO: Return access token
    EIO->>BC: Generate EML with token
    BC->>User: Download EML file
    User->>O365: Open in Outlook
    O365->>User: Send email

Permissions & Access Rights

• Permission Sets: Defined in src/permissionset/
• Entitlements: Controlled via QTEAMEntitlementManagement
• User Rights: Respects Business Central user permissions

7. Deployment Architecture

Multi-Platform Support

• SaaS: Via AppSource deployment
• On-Premise: Via .app file installation
• Hybrid: Supports both scenarios

Versioning

• App versioning: Semantic versioning (Major.Minor.Build.Revision)
• Compatibility: Backward compatibility with Business Central updates
• Update mechanism: Automatic updates for SaaS

8. Performance & Scalability

Optimizations

• Lazy Loading: Control add-ins loaded only when needed
• Caching: Templates and configuration are cached
• Batch Processing: Support for bulk operations

Resource Management

• Memory: Efficient use of browser memory
• Network: Minimal API calls to Business Central
• Storage: Local storage of temporary files

9. Error Handling

Client-Side

• JavaScript error handling in control add-ins
• Fallback mechanisms for browser compatibility
• User-friendly error messages

Server-Side

• AL error handling in codeunits
• Integration event error management
• Logging to Application Insights

Monitoring

• Application Insights: Telemetry and error tracking
• Performance counters: Response time monitoring
• Usage analytics: Usage statistics

Next steps: - Installation - Setup instructions - API Documentation - Developer information