Can UnitsInitalized be apart of a transaction prior to unit identifier generation #238
Description
We are investigating the unit initialization process using CFX but have run into an ambiguity regarding UnitsInitialized and how it relates to WorkStarted, that — within the spec, documentation, or source code — does not appear to have a direct answer.
UnitsInitialized contains the TransactionID parameter (added in version 1.1 per appendix entry A.1) which, per section 4.4.2, comes from the WorkStarted message. Table 5-2 then allows WorkStarted for unmarked boards with UnitIdentifier being optional. However, it is unclear what happens if UnitsInitialized is called afterwards — adding barcodes to the units mid-transaction. Per the online documentation, UnitsInitialized's TransactionID is required if it is part of a work transaction, which appears to allow this case. However, it does not specify whether the WorkStarted message should have used the barcodes for the units that will be initialized or not. So finally, our question: can UnitsInitialized be called in the midst of a transaction where the UnitIdentifiers were not known a priori?
(all spec references are in regard to the most recent 2.0 version)