Difference between revisions of "ITrack/Barcodes"

From ISoft Wiki
Jump to navigationJump to search
Line 55: Line 55:
| ITrack User
| ITrack User
| *U[userid]*
| *U[userid]*
|-
| OEM Number
| *[any non-empty sequence]*
| Catchall for anything that didn't match
|}
|}
* Encoded location names are currently accepted as alternate location barcode formatting even though it is not standard.
* Encoded location names are currently accepted as alternate location barcode formatting even though it is not standard.

Revision as of 12:03, 19 November 2014

Several elements of ITrack and ITrack software utilize barcodes. All ITrack products should utilize a similar barcoding scheme.

Encoding

All barcodes are done via standard 3-of-9.

Preamble and postamble

Virtually every barcode scanner can be programmed to simulate a keypress combination before entering the barcode contents (the preamble) and after (postamble).

ITrack Pro

ITrack Pro document screens (Sales, Quotes, Purchase Orders) expect a preamble of Ctrl+b and a postamble of \n.

The document screens will take whatever value is between those characters and do a lookup by partnum (the value encoded in barcodes on ITrack Pro tags), and if no values are found by partnum, by UPC (the value encoded into the barcodes printed on most products).

Workclock

The workclock system expects the barcode scanner to provide a preamble and postamble of ':$:'.

LXW

LXW defaults to preamble '~' and postamble '\r', but can be changed via Settings: 'ITrack LX'-'Preamble Character Codes' and 'Postabmle Character Codes'

Barcode Formatting

Depending on the context, the barcode will encode different types of values.

LXW

Objects Barcode Contents Additional Rules
Inventory *[inventoryid]* inventoryid must be less than 12 characters
UPC *[raw_UPC]* raw_UPC must be numeric only, exactly 12 characters
Serialized Inventory *[inventoryid]-[inventoryserialid]*
Location *%[locationid]*
Sales Order *S[storeid]-[salesorderid]*
Purchase Order *P[storeid]-[purchaseorderid]*
Transfer Order *T[transferorderid]*
Work Order Job *J[jobid]*
ITrack User *U[userid]*
OEM Number *[any non-empty sequence]* Catchall for anything that didn't match
  • Encoded location names are currently accepted as alternate location barcode formatting even though it is not standard.

Caveats

Technically, non-conforming barcode scans that contain letters and numbers are treated as locations as a work-around for an existing setup. However, this behavior is NOT supported in the long-term and will be deprecated and removed without notice. Don't rely on it!

LXPro

Objects Barcode Contents
Inventory *[partnum]*
Vehicle *$[stocknum]*
Location *%[locationid]*


Presage

Object Barcode contents Notes
Sample *S[sampleid]* Used in barcodes where the users will not be changing the sample's tag number
Work order *W[workorderid]*
Physical sample (bag) *T[tagnumber]* Identifies a sample to be submitted to multiple analyses. Is not globally unique, must be paired with a Work Order.
Location *L[locationid]* Identifies a specific location. This represents a specific place at only one plant, and does not care about the location name.
Analysis *A[analysisid]* Identifies a specific analysis.
Location+Analysis *LA[locationid]-[analysisid]* Allows the specification of an analysis and a location at the same time. Used to create product-tracking analyses.

Work Clock

Actions Barcode Contents
Clock the selected user into a selected job *+CLOCKIN*
Clock the selected user out of an active job *+CLOCKOUT*

Weaknesses

List of things to fix in the current scheme that will cause trouble down the road:

  • Inventory ID and InventoryID-SerialID are not prefixed, (potentially) overlapping with number-only string location names
  • Inventory ID, InventoryID-SerialID, LocationID do not include storeid, requiring it to be guessed at and limiting its effectiveness if not outright causing bugs