Version 2.3.6 Draft

Summary

This draft records Document Manager, chat, and Windows 11 readiness work completed after the 2.3.5 release. The current readiness direction is to keep planning inside the chat experience rather than moving it to a separate dashboard workspace.

Draft changes

Document Manager

• Added bulk delete support in File Manager so users can select multiple uploaded documents and remove them in one action.
• Kept deletion scoped to the signed-in user's own documents and cleaned up managed Azure Blob copies when those files were stored through the Document Manager integration.

Chat reliability

• Hid memory controls when memory capture is disabled so users are not shown a memory icon or toggle for an unavailable feature.
• Fixed light-mode Code View rendering so highlighted Markdown/code output does not display raw highlighting markup.
• Refined release-notification auto-open behaviour so a dismissed or closed notification drawer is not shown again for the same unread release notice when users change chat mode.

Windows 11 readiness chat flow

• Kept the Windows 11 readiness wizard as a conversation-first experience.
• Reverted the proposed standalone readiness workspace route before release.
• Preserved the existing chat wizard entry points so users can continue starting readiness work from chat.
• Confirmed the preferred next design direction: an inline guided readiness card inside chat, not a separate page.

Intune and readiness data handling

• Improved Windows 11 readiness tool routing so feature update readiness, hardware readiness scripts, application inventory, and cost modelling requests are matched more reliably.
• Added safeguards for large Intune readiness and feature update report results by limiting visible chat attachment rows and marking truncated output.
• Clarified that future readiness flows must classify operating system data explicitly instead of assuming all returned devices are Windows 10.
• Kept Intune as the preferred connected-data source, with CSV upload and generated collection scripts as fallback paths.

Cost modelling and interruption flow

• Corrected upgrade-cost totals so replacement costs are not counted in the wrong part of the estimate.
• Added dashboard-style KPI and Chart.js output for Windows 11 upgrade cost analysis so chat answers and the full report can show visual cost and refresh trends.
• Refined the generated cost-analysis report dialog so dashboard charts stay in the correct section and light-theme buttons, cards, and chart colours follow EtherAssist branding.
• Fixed PDF export for generated Windows 11 cost-analysis reports, including embedded banner image handling and clearer export failure feedback.
• Fixed the report PDF download path for browser pdfmake builds that return generated blobs through callbacks.
• Added defensive PDF export fallbacks so banner/chart rendering failures do not block report downloads.
• Fixed expanded chart readability by applying explicit light/dark fullscreen surfaces and overriding stale generated Chart.js label colours.
• Refined cost-analysis wording around unsupported-device CSV input and replacement assumptions.
• Fixed readiness tool interruption rendering so Microsoft sign-in or consent prompts do not render alongside a generic continue action.

Follow-up plan

• Build an inline Windows 11 readiness card inside chat with source selection, assessment goal selection, and run actions.
• Surface Intune connection and permission status inside the chat flow before running readiness checks.
• Add an explicit OS classification step before cost or replacement modelling.
• Render readiness summaries, unsupported-device reasons, affected device tables, and export actions as structured chat attachments.
• Keep any future persisted readiness project/history work separate from the chat-first flow until the conversation design is validated.