From c69c08b3dfb5ed86f919f7cc9c1a36d498d147f7 Mon Sep 17 00:00:00 2001 From: TNB Date: Wed, 17 Jun 2026 09:01:46 -0400 Subject: [PATCH] Add Wednesday TallyFlow Print clarifying question to daily research cycle --- TallyFlow/Product/TallyFlow Clarifying Questions.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/TallyFlow/Product/TallyFlow Clarifying Questions.md b/TallyFlow/Product/TallyFlow Clarifying Questions.md index 09373bf..767a96b 100644 --- a/TallyFlow/Product/TallyFlow Clarifying Questions.md +++ b/TallyFlow/Product/TallyFlow Clarifying Questions.md @@ -13,8 +13,14 @@ **Date Asked:** Tuesday, June 16, 2026 +## Wednesday - TallyFlow Print +**Question Asked:** What Zebra printer models and RFID tag encoding options (e.g., specific memory banks like EPC, TID, user memory; password protection; serialization/prefix logic) are supported or tested in TallyFlow Print, and how does the print job orchestration handle multi-printer environments, queuing, error recovery (printer offline, encoding failures), and safeguards against duplicate asset registrations when using the optional Core auto-registration feature? + +**Context/Notes:** Builds on the known Zebra printer support, parent/child structures, multi-printer management, and optional registration in the User's Guide and code reviews. Targets gaps in hardware compatibility details, reliability for industrial/rail use cases, and integration robustness to improve docs, website feature descriptions, and marketing for on-site labeling workflows. Addresses potential AEI/rail-adjacent tag encoding questions indirectly through custom RFID support. + +**Date Asked:** Wednesday, June 17, 2026 + ## Other Days - Monday (Core): [To be added next cycle] -- Wednesday (Print): [To be added] - Thursday (Capture): [To be added] - Friday (IoT): [To be added]