Warning Older Docs! - You are viewing documentation for a previous released version of RhoMobile Suite.

UpcEanSecurityLevel Decoder Setting

The UpcEanSecurityLevel Decoder Setting is used to set the upcEanSecurityLevel which describes the UPC/EAN security level.

Syntax

upcEanSecurityLevel (Decoder Setting) <META> Syntax

<META HTTP-Equiv="scanner" content="upcEanSecurityLevel:[parameter]">

upcEanSecurityLevel JavaScript Object Syntax:
By default the JavaScript Object 'scanner' will exist on the current page and can be used to interact directly with the upcEanSecurityLevel.
To Set upcEanSecurityLevel parameters via JavaScript use the following syntax: scanner.Parameter = Value;

e.g. scanner.upcEanSecurityLevel = Value;
UpcEanSecurityLevel Ruby Object Syntax:
By default the Ruby Object 'Scanner' will exist on the current page and can be used to interact directly with the UpcEanSecurityLevel.
To Set UpcEanSecurityLevel parameters via Ruby use the following syntax: Scanner.Parameter = Value

e.g. Scanner.upcEanSecurityLevel = Value

Parameters

Items listed in this section indicate parameters, or attributes which can be set.

Name Possible Values Description Default Value
upcEanSecurityLevel:[Value] 0 - 3 inclusive 0: This setting allows the scanner to operate in its most aggressive state, while providing sufficient security in decoding most 'in-spec' barcodes. 1: This setting eliminates most mis-decodes. 2: Select this option if security level 1 fails to eliminate mis-decodes. 3: Select this option if security level 1 and 2 fail to eliminate mis-decodes. Be advised that selecting level 3 is an extreme measure against mis-decoding and will significantly impair the decoding ability of the scanner. Device specific

Requirements

RhoElements Version 1.0.0 or above
Supported Devices All supported devices.
Minimum Requirements Scanner or Imager module and device that supports upcEanSecurityLevel.
Persistence Transient - Decoder settings are only guaranteed to persist until the Scanner is disabled

HTML/JavaScript Examples

The following example sets the upcEanSecurityLevel to check ambiguous characters:

<META HTTP-Equiv="scanner" Content="allDecoders:enabled">
<META HTTP-Equiv="scanner" Content="upcEanSecurityLevel:ambiguous">
<META HTTP-Equiv="scanner" Content="enabled">

Above example can also be written as shown below:

<META HTTP-Equiv="scanner" Content="allDecoders:enabled;upcEanSecurityLevel:ambiguous;enabled">

or

<META HTTP-Equiv="scanner-allDecoders" Content="enabled">
<META HTTP-Equiv="scanner-upcEanSecurityLevel" Content="ambiguous">
<META HTTP-Equiv="scanner-enabled" Content="SCN1">
Back to Top