New features released September 29, 2016

If you like these improvements, or you want to suggest more, please use the Feedback page.

Customize the display of product and location identifiers

You can now customize the way identifiers are displayed when viewing decoded EPCIS data. For example, instead of displaying just a GTIN and serial number, the product name associated with that GTIN can be displayed as well.

Here is an example, showing product and location names:

See the FAQ for instructions on how to use this feature

Updates to support EPCIS 1.2 and CBV 1.2

The EPCIS Workbench fully support EPCIS 1.2 and CBV 1.2, both of which were published by GS1 on September 29, 2016. New features in the EPCIS Workbench include:

New features released November 4, 2015

If you like these improvements, or you want to suggest more, please use the Feedback page.

Errors are now highlighted in the XML listing

The EPCIS Workbench performs over 100 validation checks on EPCIS data. Previously, errors were reported by red highlighting in the decoded EPCIS data, and in the error listing below the decoded data. Now, errors are also highlighted in the XML listing that follows the error listing.

Here is an example:

If you roll your mouse over one of the highlighted areas in the XML, the error message is displayed:

Other improvements to XML listing

Previously, the XML listing relied upon your web browser's XML display feature, and so the display of XML varied from browser to browser. Now, the XML listing is generated in a browser-independent way, so that the experience is consistent no matter what browser you use.

If you roll your mouse over an XML namespace prefix, the corresponding XML namespace URI is displayed. Here is an example, where the mouse is rolled over the prefix "example":

Other improvements to generated XML

The EPCIS Workbench generates XML when you create EPCIS events using the event editor and when you create EPCIS queries using the query editor. Previously, the generated XML contained an excessive number of XML namespace declarations (attributes beginning with "xmlns") and did not always generate meaningful prefixes. Now, the generated XML uses as few namespace declarations as possible, and chooses more intuitive namespace prefixes. These changes improve readability, and reduce the total size of the generated XML.

Here is an example of generated XML before the recent change:

And here is the same EPCIS event as it is now generated. Note the reduced number of namespace declarations and the more meaningful prefixes.