1. Background & ContextIn Freshservice, we utilize the approval workflow for knowledge base solution articles. New articles or updates to existing ones must be approved by designated individuals or groups before they go live. This feature works very well and ensures the quality and compliance of our internal and external documentation.2. Problem StatementCurrently, the Version History of a solution article does not provide visibility into the historical approval data of older versions. Within the version history view, it is not possible to see:Who approved a specific, older version of the article.Who actually published that specific version.The system typically only displays the current status or the last editor, missing the detailed audit trail of the approval process for each individual historical version.3. Business Impact & ComplianceThis lack of visibility poses a significant challenge during IT Audits (e.g., ISO 27001, ITIL audits, or SOX compliance).Auditors strictly require seamless proof that published knowledge—especially standard operating procedures (SOPs) for critical infrastructure—has passed the correct approval channels.Currently, reconstructing this data requires tedious manual searching through email notifications, global system logs, or historical ticket workflows.4. Proposed SolutionWe propose enhancing the Solution Article Version History view to include audit-relevant metadata for every version iteration.Suggested UI Improvements:Expanded Table/Detail View: Each listed version in the history should feature additional columns or an expandable details panel."Approved By" Field: Displays the name and timestamp of the agent who granted the approval for that specific version."Published By" Field: Displays the name and timestamp of the agent who published that specific version.Target Visual Structure Example:VersionModified ByModification DateApproved ByApproval DatePublished ByStatusv3 (Current)John Doe2026-06-10Jane Smith2026-06-11John DoePublishedv2 (Archived)Julia Admin2026-04-01IT Manager2026-04-02Julia AdminArchivedv1 (Archived)John Doe2026-01-15Change Advisory2026-01-16John DoeArchived5. Benefits of ImplementationAudit-Readiness: Instant, transparent proof for compliance officers and auditors directly within the article interface.Time Savings: Eliminates hours spent manually reconstructing workflows from global activity logs.Quality Management: Enhances internal accountability and traceability if errors are discovered in older documentation baselines.
1. Background & Context!--tgqphd|[]-->
In Freshservice, we utilize the approval workflow for knowledge base solution articles. New articles or updates to existing ones must be approved by designated individuals or groups before they go live. This feature works very well and ensures the quality and compliance of our internal and external documentation.!--tgqphd|[]-->
!--tgqphd|[]-->
2. Problem Statement!--tgqphd|[]-->
Currently, the Version History!--tgqphd|[]--> of a solution article does not provide visibility into the historical approval data of older versions. Within the version history view, it is not possible to see:!--tgqphd|[]-->
- Who!--tgqphd|[]--> approved a specific, older version of the article.!--tgqphd|[]-->!--tgqphd|[]-->
- Who!--tgqphd|[]--> actually published that specific version.!--tgqphd|[]-->!--tgqphd|[]-->!--tgqphd|[]-->
The system typically only displays the current status or the last editor, missing the detailed audit trail of the approval process for each individual historical version.!--tgqphd|[]-->
!--tgqphd|[]-->
3. Business Impact & Compliance!--tgqphd|[]-->
This lack of visibility poses a significant challenge during IT Audits (e.g., ISO 27001, ITIL audits, or SOX compliance)!--tgqphd|[]-->.!--tgqphd|[]-->
- Auditors strictly require seamless proof that published knowledge—especially standard operating procedures (SOPs) for critical infrastructure—has passed the correct approval channels.!--tgqphd|[]-->!--tgqphd|[]-->
- Currently, reconstructing this data requires tedious manual searching through email notifications, global system logs, or historical ticket workflows.!--tgqphd|[]-->!--tgqphd|[]-->!--tgqphd|[]-->
!--tgqphd|[]-->
4. Proposed Solution!--tgqphd|[]-->
We propose enhancing the Solution Article Version History!--tgqphd|[]--> view to include audit-relevant metadata for every version iteration.!--tgqphd|[]-->
!--tgqphd|[]-->
Suggested UI Improvements:!--tgqphd|[]-->
- Expanded Table/Detail View:!--tgqphd|[]--> Each listed version in the history should feature additional columns or an expandable details panel.!--tgqphd|[]-->!--tgqphd|[]-->
- "Approved By" Field:!--tgqphd|[]--> Displays the name and timestamp of the agent who granted the approval for that specific version.!--tgqphd|[]-->!--tgqphd|[]-->
- "Published By" Field:!--tgqphd|[]--> Displays the name and timestamp of the agent who published that specific version.!--tgqphd|[]-->!--tgqphd|[]-->!--tgqphd|[]-->
!--tgqphd|[]-->
Target Visual Structure Example:!--tgqphd|[]-->
!--tgqphd|[]-->
| Version!--tgqphd|[]--> | Modified By!--tgqphd|[]--> | Modification Date!--tgqphd|[]--> | Approved By!--tgqphd|[]--> | Approval Date!--tgqphd|[]--> | Published By!--tgqphd|[]--> | Status!--tgqphd|[]--> |
|---|---|---|---|---|---|---|
| v3 (Current)!--tgqphd|[]--> | John Doe!--tgqphd|[]--> | 2026-06-10!--tgqphd|[]--> | Jane Smith!--tgqphd|[]--> | 2026-06-11!--tgqphd|[]--> | John Doe!--tgqphd|[]--> | Published!--tgqphd|[]--> |
| v2 (Archived)!--tgqphd|[]--> | Julia Admin!--tgqphd|[]--> | 2026-04-01!--tgqphd|[]--> | IT Manager!--tgqphd|[]--> | 2026-04-02!--tgqphd|[]--> | Julia Admin!--tgqphd|[]--> | Archived!--tgqphd|[]--> |
| v1 (Archived)!--tgqphd|[]--> | John Doe!--tgqphd|[]--> | 2026-01-15!--tgqphd|[]--> | Change Advisory!--tgqphd|[]--> | 2026-01-16!--tgqphd|[]--> | John Doe!--tgqphd|[]--> | Archived!--tgqphd|[]--> |
!--tgqphd|[[1,0,0,7,null,""]]-->
!--tgqphd|[]-->
5. Benefits of Implementation!--tgqphd|[]-->
- Audit-Readiness:!--tgqphd|[]--> Instant, transparent proof for compliance officers and auditors directly within the article interface.!--tgqphd|[]-->!--tgqphd|[]-->
- Time Savings:!--tgqphd|[]--> Eliminates hours spent manually reconstructing workflows from global activity logs.!--tgqphd|[]-->!--tgqphd|[]-->
- Quality Management:!--tgqphd|[]--> Enhances internal accountability and traceability if errors are discovered in older documentation baselines.!--tgqphd|[]-->!--tgqphd|[]-->!--tgqphd|[]-->
!--tgqphd|[]-->
