Difference between revisions of "ITrack/Barcodes"

From ISoft Wiki
Jump to navigationJump to search
(→‎Serialized parts: Turns out we're not going to preface them with an S)
(→‎Barcode contents: Turning into a table)
Line 15: Line 15:
Depending on the context, the barcode will encode different types of values.
Depending on the context, the barcode will encode different types of values.


=== Inventory ===
{| class="wikitable"
Identified by a raw number (no character preface, starts with a digit).
! Object
Numbers with less than 10 digits are assumed to be the primary key of an inventory record (inventoryid in Enterprise, partnum in Pro).
! Barcode contents
Numbers with greater than 10 digits are assumed to be UPC codes.
! Notes
 
|-
=== Location ===
| Inventory
Location barcodes are prefaced with % - the rest of the text is a string with the location name/identifier.
| '''[inventoryid]''' OR '''[UPC code]'''
 
| If the number is less than 10 digits, it is assumed to be the primary key of an inventory record (inventoryid in Enterprise, partnum in Pro). Numbers with greater than 10 digits are assumed to be UPC codes.
=== ITrack User ===
|-
Prefaced with U - Signifies that the rest of the barcode contains a user id, referencing an ITrack user account
| Location
 
| '''%[locationid]''' OR '''[full location name]'''
=== Work Order Job ===
| Ideally, location barcodes should be the locationid, prefaced by a % sign.  In some cases, sadly, they may be an unqualified string.
Prefaced with J - Signifies that the rest of the barcode contains a job id, referencing a work order job.
|-
 
| ITrack user
=== Serialized parts ===
| '''U[userid]'''
[inventoryid]-[inventoryserialid]
|-
| Work Order Job
| '''J[job id]'''
|-
| Sales Order
| '''S[salesorderid]'''
|-
| Purchase Order
| '''P[purchaseorderid]'''
|-
| Serialized part
| '''[inventoryid]-[inventoryserialid]'''
|}


=== Other, context-sensitive ===
=== Other, context-sensitive ===

Revision as of 16:09, 5 June 2012

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

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 and LX

Both the workclock system and LX expect the barcode scanner to provide a preamble and postamble of ':$:'.

Barcode contents

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

Object Barcode contents Notes
Inventory [inventoryid] OR [UPC code] If the number is less than 10 digits, it is assumed to be the primary key of an inventory record (inventoryid in Enterprise, partnum in Pro). Numbers with greater than 10 digits are assumed to be UPC codes.
Location %[locationid] OR [full location name] Ideally, location barcodes should be the locationid, prefaced by a % sign. In some cases, sadly, they may be an unqualified string.
ITrack user U[userid]
Work Order Job J[job id]
Sales Order S[salesorderid]
Purchase Order P[purchaseorderid]
Serialized part [inventoryid]-[inventoryserialid]

Other, context-sensitive

Prefaced with + - Signifies that the rest of the barcode contains a context-sensitive command, which will probably not have meaning outside of magical bar-code applications.

  • CLOCKIN - Clocks the selected user into a selected job
  • CLOCKOUT - Clocks the selected user out of an active job
Retrieved from "https://wikido.isoftdata.com//index.php?title=ITrack/Barcodes&oldid=5889"