When a packet is routed to another department, welds, heat tags and the heat table stay on the packet and show as carried.
Built as the default: computed, nothing copied.
To answer: keep.
Plan reference: Q24 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
When a packet is routed to another department, welds, heat tags and the heat table stay on the packet and show as carried.
**Built as the default:** computed, nothing copied.
**To answer:** keep.
---
Plan reference: Q24 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.
yes always keep the data on further progression. some drawings call parts weld and weld assembly welds on the same drawing. in this case weld assembly would need to be able to add welds to the previous weld map so we can limit the amount of data in the databook. This will only come into effect if the packet transfers to that department.
yes always keep the data on further progression. some drawings call parts weld and weld assembly welds on the same drawing. in this case weld assembly would need to be able to add welds to the previous weld map so we can limit the amount of data in the databook. This will only come into effect if the packet transfers to that department.
Noted: the welds, heat tags and heat table stay with the packet as it moves on, and a department that receives the packet (for example weld assembly after parts weld) adds its welds to the same weld map, so the data book carries one map. That is how the build works today. Recorded in docs/PLAN.md Q24. Closing.
Noted: the welds, heat tags and heat table stay with the packet as it moves on, and a department that receives the packet (for example weld assembly after parts weld) adds its welds to the same weld map, so the data book carries one map. That is how the build works today. Recorded in docs/PLAN.md Q24. 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.
When a packet is routed to another department, welds, heat tags and the heat table stay on the packet and show as carried.
Built as the default: computed, nothing copied.
To answer: keep.
Plan reference: Q24 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
yes always keep the data on further progression. some drawings call parts weld and weld assembly welds on the same drawing. in this case weld assembly would need to be able to add welds to the previous weld map so we can limit the amount of data in the databook. This will only come into effect if the packet transfers to that department.
Noted: the welds, heat tags and heat table stay with the packet as it moves on, and a department that receives the packet (for example weld assembly after parts weld) adds its welds to the same weld map, so the data book carries one map. That is how the build works today. Recorded in docs/PLAN.md Q24. Closing.