Refactors and adds shared formatting utilities for initials, values, and humanizing keys with unit tests.
Improve object form logic to handle ETag conflicts gracefully, enabling retry after fresh data fetch.
Implement API configuration, hooks, and components for fetching and rendering audit log entries.
Implements the audit log panel in Author View, toggled from the Activity section, including UI components and toolbar actions.
Enhances create/edit flows with ETag concurrency control, triggering refetches and fresh data retrieval.
Adds optimized audit log API configuration, fetch hook, and conditional query invalidation for real-time updates.
Introduce shared formatting utilities to enhance display of changelog data and user avatars.
Ensure audit log data stays up-to-date after user mutations via targeted query invalidation.
Provides state management for audit panel visibility and integrates dynamic grid layout transformations to share space with the object list.
Build and integrate a toggleable audit log panel in the Author View, including UI components, state management, and layout adjustments.
Related requirement tasks from other projects
Description Please provide system capabilities and/or a demo. Platform Status: partially implemented PPT Status: Yes MVP: Yes Must Have: Priority 1 (A) Use Case This will assist in setting and monitoring our KPI's. For example, in WC our workflow and data processing was less efficient than previous CMS. We would like ability to track our progress in the new CCMS (how long it takes to author a topic, how long it is in translation, how long does publishing take, how many iteration reviews took place, from start to finish did we meet 48 hours) to look for areas of efficiency gain or focus areas for improvement as well. Current Challenges Internal reports in current tool are cumbersome and configured for engineering/mfg/parts data reports. Lacks good reports for Technical Information. One specific KPI we have been unable to achieve in current tool and would want to measure is 48 hr update - are we meeting the target, how far off are we. Notes but supported (data available Save a lot of the information in the backend PowerBI does currently work with platform Don't have access yet (Simple to rollout) Custom visualisations need to be implemented (dashboards) Not yet exportable or sent to a dashboard. Description: Allows internal/external reporting, PowerBI integration, and custom visualisations; export/dashboard functions not yet available. Status: Not implemented but supported Notes: Data stored in backend; PowerBI works but no access yet; custom dashboards need implementation; currently not exportable.
View in Azure DevOps →