Differences

This shows you the differences between two versions of the page.

Link to this comparison view

bar_code_scanning [2019/01/30 09:22]
127.0.0.1 external edit
bar_code_scanning [2019/01/30 16:08]
kcifreo
Line 1: Line 1:
-Bar Code Scanning in Job Monitor +===== Bar Code Scanning in Job Monitor =====
  
 **This feature is only available with Production Terminal version 05.00.1104.2001 and later.** **This feature is only available with Production Terminal version 05.00.1104.2001 and later.**
- 
- 
  
 The barcode feature not only allows the user to enter text with a keyboard or select a value with a mouse as usual, but to also accept input from a barcode scanner. USB Barcode Scanners simulate keystrokes of the keyboard. However, the information coming from the barcode is a numeric ID of the data and not the data itself, so Production Terminal has to manually handle barcode where applicable. The barcode feature not only allows the user to enter text with a keyboard or select a value with a mouse as usual, but to also accept input from a barcode scanner. USB Barcode Scanners simulate keystrokes of the keyboard. However, the information coming from the barcode is a numeric ID of the data and not the data itself, so Production Terminal has to manually handle barcode where applicable.
  
 +The following fields in the Job Monitor Screen can be filled in using a bar code scanner:
  
- 
-The following fields in the Job Monitor Screen can be filled in using a bar code scanner: 
   * Employee   * Employee
   * Line Item #   * Line Item #
Line 15: Line 12:
   * Assigned To   * Assigned To
   * Part (when clocking in)   * Part (when clocking in)
- 
- 
  
 To use the barcode, the user will need to click in the desired field and then scan the desired bar code for that field. The field will populate with the corresponding value and the focus will advance to the next field (like a Tab would). If the bar code does not have a match, a message will display indicating there was no match found. Users can also type into these fields. To use the barcode, the user will need to click in the desired field and then scan the desired bar code for that field. The field will populate with the corresponding value and the focus will advance to the next field (like a Tab would). If the bar code does not have a match, a message will display indicating there was no match found. Users can also type into these fields.
- 
- 
  
 Note: Cyrious uses DBR28 Code 128 barcode fonts. Note: Cyrious uses DBR28 Code 128 barcode fonts.
  
- +The //decoded//  format of a barcode in Cyrious is as follows:
- +
-The //decoded// format of a barcode in Cyrious is as follows: +
- +
  
 ~cccccc.iiiiii ~cccccc.iiiiii
  
 +Where
  
- 
-Where 
   * ~ (tilde) indicates that what follows is a bar code.   * ~ (tilde) indicates that what follows is a bar code.
   * cccccc is the ClassTypeID of the particular data item.   * cccccc is the ClassTypeID of the particular data item.
   * iiiii is the database ID of the particular data item.   * iiiii is the database ID of the particular data item.
- 
- 
  
 The ClassTypeIDs of all objects in Cyrious can be found on this WIKI: The ClassTypeIDs of all objects in Cyrious can be found on this WIKI:
  
- +[[:database_table_by_object_type_and_classtypeid|]].
- +
-[[database_table_by_object_type_and_classtypeid]]. +
- +
  
 For Production Terminal, the following ClassTypeIDs are used: For Production Terminal, the following ClassTypeIDs are used:
  
 +|**Object** ||**ClassTypeID** ||
 +|Employee||3500||
 +|Line Item||10100||
 +|Part (Definition)||12014||
 +|Station||26100||
 +|Part (in a Transaction)||10300||
  
- 
-|| **Object** || **ClassTypeID** || 
-|| Employee || 3500 || 
-|| Line Item || 10100 || 
-|| Part (Definition) || 12014 || 
-|| Station || 26100 || 
-|| Part (in a Transaction) || 10300 || 
 The scanner should be set up to send a CR/LF after each scan. This may be the default, but many scanners are configurable. The scanner should be set up to send a CR/LF after each scan. This may be the default, but many scanners are configurable.
  
 +[[:include_componentbacklinks_pagebar_code_scanning_limit5|include component"backlinks" page"Bar Code Scanning" limit"5"]]
  
 +\\
  
-[[include_componentbacklinks_pagebar_code_scanning_limit5|include component"backlinks" page"Bar Code Scanning" limit"5"]]