spencerm/PacketStation
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Same-rev drawing re-release on an in-shop packet: change order or silent swap #9

New Issue
Closed
opened 2026-10-19 02:50:14 +00:00 by spencerm · 4 comments
spencerm commented 2026-10-19 02:50:14 +00:00
Owner
Copy Link
Copy Source

M-Files sometimes re-releases a drawing at the same rev with a new file.

Built as the default: a drawing-origin change order, never a silent swap.

To answer: keep, or swap silently with an audit entry.

Plan reference: Q10 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.

M-Files sometimes re-releases a drawing at the same rev with a new file. **Built as the default:** a drawing-origin change order, never a silent swap. **To answer:** keep, or swap silently with an audit entry. --- Plan reference: Q10 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.
spencerm added the phase 3decision: Seth labels 2026-10-19 02:50:14 +00:00
SethD commented 2026-10-26 15:35:37 +00:00
Collaborator
Copy Link
Copy Source

swap silently as long as it is the same drawing with no changes

swap silently as long as it is the same drawing with no changes
spencerm commented 2026-10-27 21:48:42 +00:00
Author
Owner
Copy Link
Copy Source

Thanks. One question about "same drawing with no changes".

When M-Files re-releases a drawing at the same rev, it always comes with a new file. If the file is byte-for-byte identical, Packet Station already ignores it. When the bytes differ, Packet Station cannot tell a real content change (a dimension moved) from a cosmetic one (title block re-plotted, new PDF export).

Which should happen on an in-shop packet when the new same-rev file differs?

  1. Swap it silently, with a log entry and an audit row. Trust that a real change always gets a new rev.
  2. Keep the change order (as built), so the shop confirms the new pages.
  3. Swap silently only when the page count is unchanged; otherwise a change order.
Thanks. One question about "same drawing with no changes". When M-Files re-releases a drawing at the same rev, it always comes with a new file. If the file is byte-for-byte identical, Packet Station already ignores it. When the bytes differ, Packet Station cannot tell a real content change (a dimension moved) from a cosmetic one (title block re-plotted, new PDF export). Which should happen on an in-shop packet when the new same-rev file differs? 1. Swap it silently, with a log entry and an audit row. Trust that a real change always gets a new rev. 2. Keep the change order (as built), so the shop confirms the new pages. 3. Swap silently only when the page count is unchanged; otherwise a change order.
SethD commented 2026-10-29 14:39:35 +00:00
Collaborator
Copy Link
Copy Source

Keep the change order (as built), so the shop confirms the new pages.

Keep the change order (as built), so the shop confirms the new pages.
spencerm commented 2026-10-30 19:34:17 +00:00
Author
Owner
Copy Link
Copy Source

Noted: the change order on a same-rev re-release stays as built, so the shop confirms the new pages. Recorded in docs/PLAN.md question 10 (PR 54).

Noted: the change order on a same-rev re-release stays as built, so the shop confirms the new pages. Recorded in docs/PLAN.md question 10 (PR 54).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
decision: Clerical
decision: IT
decision: Q.C.
decision: Seth
phase 10
phase 3
phase 4
phase 5
phase 6
phase 7
phase 8
phase 9
production
No labels decision: Seth phase 3
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
SethD (Seth Dostaler) spencerm (Spencer McGuire)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spencerm/PacketStation#9