The data book carries internal history and the controlled-copy stamp.
To answer: whether a customer copy with some sections left out is wanted, and which sections.
Plan reference: Q9b in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
The data book carries internal history and the controlled-copy stamp.
**To answer:** whether a customer copy with some sections left out is wanted, and which sections.
---
Plan reference: Q9b 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.
I think for now we can leave the history off. This is something we can look at later implementing or that we can look up the history on our side if there are questions
I think for now we can leave the history off. This is something we can look at later implementing or that we can look up the history on our side if there are questions
Thanks. One detail so this is built the way you mean:
Today there is one data book per filed packet. It includes the packet history pages and the controlled-copy stamp, and that same file is what goes to the customer.
Which do you want?
One data book, with the history pages taken out. History stays visible in Packet Station only.
Two copies: the internal data book with history, and a customer copy without it, both built at filing.
Thanks. One detail so this is built the way you mean:
Today there is one data book per filed packet. It includes the packet history pages and the controlled-copy stamp, and that same file is what goes to the customer.
Which do you want?
1. One data book, with the history pages taken out. History stays visible in Packet Station only.
2. Two copies: the internal data book with history, and a customer copy without it, both built at filing.
Noted: one data book, the customer copy, without the packet history pages. History stays readable in Packet Station. Recorded in docs/PLAN.md as change C6, to build in phase 10 (PR 53). Closing.
Noted: one data book, the customer copy, without the packet history pages. History stays readable in Packet Station. Recorded in docs/PLAN.md as change C6, to build in phase 10 (PR 53). Closing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The data book carries internal history and the controlled-copy stamp.
To answer: whether a customer copy with some sections left out is wanted, and which sections.
Plan reference: Q9b in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
I think for now we can leave the history off. This is something we can look at later implementing or that we can look up the history on our side if there are questions
Thanks. One detail so this is built the way you mean:
Today there is one data book per filed packet. It includes the packet history pages and the controlled-copy stamp, and that same file is what goes to the customer.
Which do you want?
lets just do the customer copy for now. do not worry about including the full history in the databook
Noted: one data book, the customer copy, without the packet history pages. History stays readable in Packet Station. Recorded in docs/PLAN.md as change C6, to build in phase 10 (PR 53). Closing.