Barcode Range Validation - Revision history

Jgreco: Proofread - greco

2021-11-12T17:49:54Z

Proofread - greco

Jwolbert: /* How it works */

2016-06-21T15:40:15Z

How it works

Jwolbert: /* How it works */

2016-06-21T15:38:19Z

How it works

Jwolbert: /* How it works */

2016-06-21T15:35:52Z

How it works

Jwolbert at 15:35, 21 June 2016

2016-06-21T15:35:21Z

Jwolbert: Created page with "{{TrackAbout Feature |Parent Module=Core Tracking |Feature Description=TrackAbout provides support for validating numeric barcode/tag ranges for barcodes in relation to the ki..."

2016-06-21T15:34:29Z

Created page with "{{TrackAbout Feature |Parent Module=Core Tracking |Feature Description=TrackAbout provides support for validating numeric barcode/tag ranges for barcodes in relation to the ki..."

New page

{{TrackAbout Feature
|Parent Module=Core Tracking
|Feature Description=TrackAbout provides support for validating numeric barcode/tag ranges for barcodes in relation to the kind of assets they're associated with (i.e. individual assets, bundles, containers).
|Supported In=TAMobile 6 Desktop, TAMobile 6 Rugged
}}
==Overview==
Some companies use complex meaningful barcodes/tags to track their assets. TrackAbout provides support for validating numeric barcode/tag ranges for barcodes in relation to the kind of assets they're associated with (i.e. individual assets, bundles, containers).

==How it works==
Ranged Barcode Rules define the numbers can be used for barcodes for each country code, issuer code, and asset class (cylinder, container, or pack/bundle) combination.

For example, given country code 100, issuer code 301, a start of 00002000, and an end of 00005000 that apply to containers, valid barcodes would include 10030100002000 - 10030100005000.

Cylinder rules may include an optional asset family restriction, which helps users recognize the type of cylinder by barcode alone. This restriction is only enforced when adding a new cylinder or replacing a barcode.

← Older revision		Revision as of 15:40, 21 June 2016
Line 12:		Line 12:

	[[File:Ranged Barcode Rules.png\|400px]]		[[File:Ranged Barcode Rules.png\|400px]]
		+
		+	Barcodes must conform to the format [CCC][III][NNNNNNNN] where CCC is a three-digit country code, III is a three-digit issuer code, and NNNNNNNN is an eight-digit number. All values are padded with leading zeros. Different asset classes (e.g., cylinders, bundles, containers) are allotted number ranges per country / issuer combination.

	For example, given country code 100, issuer code 301, a start of 00002000, and an end of 00005000 that apply to containers, valid barcodes would include 10030100002000 - 10030100005000.		For example, given country code 100, issuer code 301, a start of 00002000, and an end of 00005000 that apply to containers, valid barcodes would include 10030100002000 - 10030100005000.

← Older revision		Revision as of 15:38, 21 June 2016
Line 18:		Line 18:

	Cylinder rules may include an optional asset family restriction, which helps users recognize the type of cylinder by barcode alone. This restriction is only enforced when adding a new cylinder or replacing a barcode.		Cylinder rules may include an optional asset family restriction, which helps users recognize the type of cylinder by barcode alone. This restriction is only enforced when adding a new cylinder or replacing a barcode.
		+
		+	==Supported Actions==
		+
		+	As of June 2016, Barcode Range Validation is available on TAMobile 6 and the rules apply to the following actions:
		+
		+	* Add New / Edit
		+	* Add Container
		+	* Make Bundle
		+	* Make Pack
		+	* Replace Barcode
		+	* Proof of Delivery
		+	* Locate
		+	* Truck Load
		+	* Sort Trip
		+	* Customer Audit

@@ Line 5: / Line 5: @@
 }}
 ==Overview==
-Some companies use complex meaningful barcodes/tags to track their assets.  TrackAbout provides support for validating numeric barcode/tag ranges for barcodes in relation to the kind of assets they're associated with (i.e. individual assets, bundles, containers).
+Some companies use complex meaningful barcodes/tags to track their assets. TrackAbout provides support for validating numeric barcode/tag ranges for barcodes in relation to the kind of assets they're associated with (i.e. individual assets, bundles, containers).
 ==How it works==
-Ranged Barcode Rules define the numbers can be used for barcodes for each country code, issuer code, and asset class (cylinder, container, or pack/bundle) combination.
+Ranged Barcode Rules define the numbers that can be used for barcodes for each country code, issuer code, and asset class (cylinder, container, or pack/bundle) combination.
 [[File:Ranged Barcode Rules.png|400px]]

@@ Line 14: / Line 14: @@
 For example, given country code 100, issuer code 301, a start of 00002000, and an end of 00005000 that apply to containers, valid barcodes would include 10030100002000 - 10030100005000.
-[[File:Creating a Barcode Range Rule.png|400px]]
 Cylinder rules may include an optional asset family restriction, which helps users recognize the type of cylinder by barcode alone. This restriction is only enforced when adding a new cylinder or replacing a barcode.