Feature Suggestion

Description: Phase 2 completes thedata deletion programme and delivers the user-facing experience. Building on the engine and ITGS deletion support from Phase 1, Phase 2 adds deletion coverage for Warehouse (Power BI reporting data) and Marketplace (third-party connector data), and delivers the Excel-driven UI that authorised users will actually use to trigger deletions — with a full two-person approval flow and permanent audit trail. Phase 2 cannot begin until Phase 1 is fully complete. The deletion engine built in Phase 1 is the backbone every feature here depends on. What is being built in Phase 2: Feature 3 — Warehouse Deletion and Refresh When a packet is deleted from Core, its data must also be removed from the Warehouse — otherwise it continues to appear in Power BI dashboards, which is a GDPR violation. This feature deletes the matching Warehouse records and triggers a forced Power BI dataset refresh so the data disappears from reporting immediately. Feature 4 — Marketplace Deletion Packets that pass through Marketplace connectors may hold associated data in third-party systems. This feature identifies that data, calls the appropriate Marketplace connector to remove it, and confirms deletion before Core removes its own records. Feature 5 — Excel-Based Deletion UI The front-end that authorised users interact with. A user with the Purge Packets permission uploads an Excel file containing the packet references to be deleted. The system validates the list, resolves the full consequential deletion group, and shows the user exactly what will be deleted before anything happens. A second authorised user must approve. On approval, deletion runs asynchronously across all 5 systems — Core, ITGS, Warehouse, Marketplace, and Blob storage — and a permanent audit record is created. Warehouse Deletion and Refresh-[ https://feedback.enate.net/feature-request/p/warehouse-deletion-and-refresh-belongs-to-data-deletion-packet-purge-framework ] Marketplace Deletion - [ https://feedback.enate.net/feature-request/p/marketplace-deletion-belongs-to-data-deletion-packet-purge-framework ] Excel-Based Deletion UI- [ https://feedback.enate.net/feature-request/p/excel-based-deletion-ui-belongs-to-data-deletion-packet-purge-framework ] ⚠️ Important — nothing in this feature is available until all 5 features are complete: Even when Phase 2 features are individually built, the end-to-end deletion flow requires all 5 features across both phases to be live. The Excel UI (Feature 5) is the trigger point — it will only be enabled once Features 1 through 4 are confirmed complete and tested. This feature will only be available to use after all 5 features across Phase 1 and Phase 2 are complete. This is Phase 2 of 2. Phase 2 depends entirely on GDPR Data Deletion — Phase 1: Core Engine & Intelligent Search [ https://feedback.enate.net/feature-request/p/data-deletion-packet-purge-framework-phase-1 ]

We are building a proper deletion feature inside Enate — one that is safe, controlled, and leaves a clear A safe, auditable, and compliant way to permanently delete packet data from every system Enate holds data in. Today this is done via manual SQL scripts — which is slow, risky, and leaves no audit trail. This epic replaces that entirely with a structured, two-person approved, multi-system deletion framework. The is split into 5 features that are built and delivered in sequence. Each feature is independent enough to be built by a separate team but they all connect together into one end-to-end flow. Phase 1 lays the foundation. It builds the backend deletion engine that every other part of this capability depends on, and adds deletion support to Intelligent Search (ITGS) — which ships in the July Alpha and cannot go live without deletion parity. Without Phase 1 complete, nothing in Phase 2 can be built or tested. These two features are the critical path for the entire deletion programme. What is being built in Phase 1: Feature 1 — Packet Group Deletion Engine The core backend engine. When given a list of packet references, it resolves the full group of related packets (parent + all children), validates eligibility, and orchestrates deletion across every system Enate holds data in — in the correct order. This engine is the foundation every other feature in both Phase 1 and Phase 2 calls into. Nothing works without it. Feature 2 — Intelligent Search (ITGS) Deletion Today, ITGS receives create and update events from Core but has no deletion support. If a packet is deleted from Core, it stays indexed and searchable in ITGS — a direct data violation. This feature adds a deletion event listener to ITGS, removes the corresponding index entry, and sends a positive confirmation back to Core before Core removes its own records. ITGS ships in the July Alpha. Deletion support must be ready at the same time. ⚠️ Important — this is infrastructure, not a user-facing feature: Phase 1 delivers no UI. Customers and agents will not see any change in the product when Phase 1 ships. The deletion engine and ITGS integration run entirely in the background. The user-facing deletion experience — the Excel upload, the approval flow, the audit trail — is delivered in Phase 2. This feature will only be available to use after all 5 features across Phase 1 and Phase 2 are complete. Packet Group Deletion Engine- [ https://feedback.enate.net/feature-request/p/packet-group-deletion-engine ] Intelligent Search (ITGS) Deletion- [ https://feedback.enate.net/feature-request/p/intelligent-search-itgs-deletion ] This is Phase 1 of 2. See the full picture in Data Deletion Purge packet— Phase 2: Warehouse, Marketplace & Excel UI [ https://feedback.enate.net/feature-request/p/data-deletion-packet-purge-framework-phase-2 ]

We are refreshing the Work Manager user experience to improve the look and feel while keeping existing capabilities intact. This new user experience will be released in stages through an alpha/beta program. A select few of you are invited to participate in this program to help shape the new version of Work Manager. In Alpha 1 we are going to release a refreshed design of the homepage, Ticket screen, Case screen, Action screen and Quickfind. Along with this, we are including the following new features: AI Assistant in Email Editor Add Format Painter Tool in Email Editor Aptos Font in Email Editor Search and Replace in Email Editor Calibri Font Available in Email Editor Quick Access Toolbar in Email Editor Spellcheck and Grammar Check in Email Editor Email Translation Searchable Context Fields Advanced Table Editing Options Advanced Image Editing Tools CC Field Open by Default Rename “Submit” Button to “Save” Copy Button for File Names Ability to Summarise Email Threads Group Time Tracker Entries by User Improved Table Formatting Options in Email Body Improve Display Font to Distinguish Similar Characters Add “Clear Formatting” Option in Email Editor Display User Role in User Settings (Read‑Only) Allow Editing of Ticket Description After Submission Confirmation Pop‑Up When Cancelling an Email Draft Relocate Message Pop‑Up in Work Manager UI Show Customer, Contract, and Service Context in Quickfind Results Show Individual Counts as Separate Bars in Bar Charts Improve Email Separator Line – Use Solid Line Instead of Dashes Option to sort My Team in alphabetical order Notes support rich text editing (undo/redo, fonts, size, bold/italic/underline/strikethrough, text & background colour, lists, indentation, alignment, line height, superscript/subscript, capitalisation, tables, special characters, find & replace, format painter, clear formatting) Superscripts work automatically upon hitting space in email composer and notes Option to attach multiple files at once to an email Drag and drop email addresses from 'To' to 'CC', 'BCC' etc. Sort the Unassigned Work Queues – by Workload, Due Status or Alphabetically Edit a Cancelled Email – Recover Its Content Into the Composer

We are refreshing the Work Manager user experience to improve the look and feel while keeping existing capabilities intact. This new user experience will be released in stages through an alpha/beta program. A select few of you are invited to participate in this program to help shape the new version of Work Manager. In Alpha 2 we are going to release a refreshed design of the Case and Action screens.

Please improve Quickfind so that it shows results that are more relevant to me. Currently, it returns a large number of items, many of which belong to customers or areas I don’t work with.