Built as the default: a second confirmation and a warning on both routes; the open work orders are kept on the seal and in the log.
To answer: keep, or block until VISUAL shows closed.
Plan reference: Q36 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
**Built as the default:** a second confirmation and a warning on both routes; the open work orders are kept on the seal and in the log.
**To answer:** keep, or block until VISUAL shows closed.
---
Plan reference: Q36 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.
Noted: filing waits until VISUAL shows the work orders closed. The packet sits in a Clerical "Ready to close" column until the feed sees VISUAL closed, then moves to "Ready for data book". Recorded in docs/PLAN.md as change C5, to build in phase 10. I applied it to packets routed to Shipping too; say so here if Shipping should be different. Closing.
Noted: filing waits until VISUAL shows the work orders closed. The packet sits in a Clerical "Ready to close" column until the feed sees VISUAL closed, then moves to "Ready for data book". Recorded in docs/PLAN.md as change C5, to build in phase 10. I applied it to packets routed to Shipping too; say so here if Shipping should be different. Closing.
Building this now (filing waits until VISUAL shows every work order closed, on both routes). One case needs your call:
If a work order is deleted from VISUAL while it still showed open, Packet Station never sees it close, so the packet could never be filed. Which should happen?
Treat a work order that has been gone from VISUAL for 2 feed runs as closed, so the packet can move on.
Keep it blocked and let an Admin mark it closed by hand, with a reason that is logged.
Something else.
Until you answer, it stays blocked. The question above about Shipping still stands: as built, Shipping packets wait for the VISUAL close too.
Building this now (filing waits until VISUAL shows every work order closed, on both routes). One case needs your call:
If a work order is deleted from VISUAL while it still showed open, Packet Station never sees it close, so the packet could never be filed. Which should happen?
1. Treat a work order that has been gone from VISUAL for 2 feed runs as closed, so the packet can move on.
2. Keep it blocked and let an Admin mark it closed by hand, with a reason that is logged.
3. Something else.
Until you answer, it stays blocked. The question above about Shipping still stands: as built, Shipping packets wait for the VISUAL close too.
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.
Built as the default: a second confirmation and a warning on both routes; the open work orders are kept on the seal and in the log.
To answer: keep, or block until VISUAL shows closed.
Plan reference: Q36 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
Packets need to go into the ready to close clerical column until visual shows them closed. they then need to go to the ready for data book column
Noted: filing waits until VISUAL shows the work orders closed. The packet sits in a Clerical "Ready to close" column until the feed sees VISUAL closed, then moves to "Ready for data book". Recorded in docs/PLAN.md as change C5, to build in phase 10. I applied it to packets routed to Shipping too; say so here if Shipping should be different. Closing.
Building this now (filing waits until VISUAL shows every work order closed, on both routes). One case needs your call:
If a work order is deleted from VISUAL while it still showed open, Packet Station never sees it close, so the packet could never be filed. Which should happen?
Until you answer, it stays blocked. The question above about Shipping still stands: as built, Shipping packets wait for the VISUAL close too.