DekEn

อัปเดต 2026-09-07

Case-study datasheet revision history

Shared, database-backed revisions

Every EGAT equipment datasheet keeps a shared, database-backed revision history (one global row per slug) so gb/admin users see how a spec sheet changed across design iterations instead of a single overwritten file.

เมื่อไรจึงใช้
  • Tracking how a datasheet's spec evolved from an earlier revision to a later one as the design matured
  • Recovering an earlier revision's content after a later edit
  • Auditing who changed what on a shared, multi-editor datasheet
คำนวณอย่างไร

A dedicated case-study-datasheets endpoint persists an opaque {revisions[], activeRevId} payload per slug; each datasheet page wires its auto-save into that shared revision store rather than a page-local draft.

ข้อควรระวัง
noteIt's last-write-wins on the whole payload — two people editing the same datasheet at once can have one's save overwrite the other's
noteBecause it's a SHARED global row per slug (not per-user), a saved revision is visible to every gb/admin viewer, not private to the editor
ที่เกี่ยวข้อง