Multiple (and Concurrent) Custom Status Indicators
under review
W
Wisteria Prawn
We are requesting a significant upgrade to the "Status" indicator system. Instead of a single, "Custom" status, we need the ability to create multiple custom indicators that can be displayed simultaneously on the public-facing Knowledge Base articles. (These should function as high-visibility UI badges, managed and displayed separately from the existing "Article Tags" system used for SEO and search boosting.)
Currently, Document360 limits an article to one status indicator at a time. This is restrictive because statuses often need to convey different types of information to the reader.
- Example: An article might be "Updated" (Status) AND require an "Enterprise License" (Functional Metadata).
- Right now, we have to choose one or the other, or manually type this into the article body, which lacks visual consistency and searchability.
Proposed Solution: "Visual Badges" System
A dedicated system for Concurrent Status Indicators that provides:
- Distinct UI Layer: Indicators should remain at the top of the article (near the title) to give immediate context to the reader, separate from the Tag cloud.
- Multiple Active Indicators: The ability to toggle multiple statuses for one article (e.g., a "Beta" badge AND an "Enterprise" badge).
- Independent Logic: These indicators should not affect search weight in the same way tags do; their primary purpose is visual communication.
- Custom Styling: A dedicated settings page to define the Label and HEX color for each unique status.
Log In
D
D360 Product Management
marked this post as
under review
Mohamed Shakheen
Hi Wisteria Prawn
Thank you for sharing the detailed context and use case around multiple status indicators. We understand the need for displaying concurrent visual signals on articles and how the current single-status limitation creates friction for your workflow.
We’ve taken note of your proposal for a dedicated “Visual Badges” system and will analyze this from both a product and technical feasibility standpoint, including UI/UX implications and alignment with existing tagging and metadata systems.
We will review this internally and share an update with you on next steps once we have more clarity on the approach and potential timelines.