Public Access
31 lines
2.2 KiB
Markdown
31 lines
2.2 KiB
Markdown
## MODIFIED Requirements
|
|
|
|
### Requirement: Windows Outlook enrichment is optional
|
|
Meeting Assistant SHALL gate Outlook Classic COM enrichment behind the Windows compilation target.
|
|
|
|
When the Windows build starts a meeting and Outlook Classic has exactly one current Teams appointment, Meeting Assistant SHALL copy the appointment title to the meeting note and copy the appointment agenda and scheduled end time to the assistant-context frontmatter.
|
|
|
|
Meeting Assistant SHALL copy the appointment attendees to the meeting note only when the raw appointment attendee count is less than or equal to the configured `Recording:MaxMetadataAttendeeImportCount`. The default maximum SHALL be 30 attendees.
|
|
|
|
The agenda SHALL be extracted from the appointment body content before the Teams join separator or Teams join text.
|
|
|
|
#### Scenario: Current Teams appointment enriches meeting artifacts
|
|
- **WHEN** a Windows build starts a meeting while Outlook Classic exposes exactly one current Teams appointment
|
|
- **THEN** Meeting Assistant uses the appointment subject as the meeting title
|
|
- **AND** writes the appointment attendees into meeting note frontmatter when the raw attendee count is within the configured import limit
|
|
- **AND** writes the appointment agenda into assistant-context frontmatter
|
|
- **AND** writes the appointment end time as `scheduled_end` into assistant-context frontmatter
|
|
|
|
#### Scenario: Oversized attendee list is not imported
|
|
- **GIVEN** the configured metadata attendee import limit is 30
|
|
- **WHEN** a Windows build starts a meeting while Outlook Classic exposes exactly one current Teams appointment with 31 attendees
|
|
- **THEN** Meeting Assistant uses the appointment subject as the meeting title
|
|
- **AND** does not write the appointment attendees into meeting note frontmatter
|
|
- **AND** writes the appointment agenda into assistant-context frontmatter
|
|
- **AND** writes the appointment end time as `scheduled_end` into assistant-context frontmatter
|
|
|
|
#### Scenario: Outlook is unavailable or ambiguous
|
|
- **WHEN** Outlook Classic is unavailable or more than one current Teams appointment is found
|
|
- **THEN** Meeting Assistant starts the recording with the default generated meeting title and empty agenda
|
|
- **AND** omits `scheduled_end` from assistant-context frontmatter
|