Customer Context
Oracle manages large, long-lived Q&A libraries that evolve over time. As formatting standards change, legacy or out-of-scope styles (e.g., older NAA examples) need to be removed to maintain clarity, consistency, and usability for global teams.
Problem / Opportunity
Currently, there is no efficient way to remove deprecated styles at scale:
- Styles that are no longer relevant remain applied across Q&A content, creating clutter and confusion.
- Removing styles requires manual, record-by-record updates.
- There is limited visibility into how widely a style is used or where formatting inconsistencies exist.
As a result, Oracle’s style lists grow unnecessarily large, making it harder for users to apply the correct formatting and maintain governance.
Proposed Enhancement
Enable bulk removal and governance of styles by:
- Allowing users to bulk remove one or more selected styles across Q&A records.
- Defining a clear system behavior for removed styles (e.g., map to a default style, convert to plain text, or allow admin-defined replacements).
- Supporting a streamlined, single-style or standardized-style model where appropriate.
- Providing visibility into style usage to identify gaps, inconsistencies, or outliers across the library.
Success Criteria
- Reduced number of unused or deprecated styles in active libraries
- Faster cleanup of legacy formatting during standard changes
- Improved consistency of formatting across Q&A content
- Positive feedback from Oracle on ease of style governance
Open Questions (for Product Consideration)
- What is the default formatting behavior when a style is removed?
- How can Responsive support customers transitioning to a single-style model while preserving consistency?
- What reporting or visual indicators can help identify formatting gaps or outliers?
