Skip to content

Style History

The History tab in the Style module provides a chronological log of actions performed on files within a style record. This feature is essential for tracking document activity and ensuring audit-readiness throughout the style lifecycle. Alongside other style views that capture field-level changes—such as description, composition, category, specifications, and approvals—it helps teams reconstruct how the style's supporting artefacts evolved over time. Use it when you need evidence of who downloaded or replaced a tech pack during a sign-off window.

Style History

The log captures every file-related interaction, such as uploads, downloads, and edits, along with timestamps and user attribution. This enhances transparency and accountability in the development and approval process.

Columns Available

The history log displays the following columns for each recorded action:

Field Description
Date Timestamp when the action occurred.
Changed By The user who performed the action.
Action Type of interaction (e.g., Update, Create, Delete).
Items File or folder involved in the action.
Value From Source or previous value, such as the workflow stage or file category.
Value To Destination or new value after the action was completed.

Style History

Key Features

Feature Description
Search and Filter Use the search bar to narrow results by file name, user, or date.
Download History Identify users who accessed key files, including when.
Audit Ready Ensures all file activity is logged and reviewable for compliance and historical analysis.
Important Tips
  • Use the log to verify who uploaded final versions or downloaded production-ready files.
  • History logs are retained for a maximum of 180 days.
  • Helpful during vendor coordination and internal approvals.
  • This log is permanent and cannot be modified by users.
Best Practices

Regular Review: Check the history log regularly when coordinating with vendors or during approval workflows.

Search Efficiently: Use the search function to quickly find specific file activity or user actions.

Audit Verification: Reference the log during approvals to verify who has accessed key documents and when.