Binding Function

RFDDTAG

Binding ID

MAP_TO_DEFAULT

Binding Description

Map Tag to Default Item & Location

Purpose

This binding will enable an unmapped tag that is seen at a read zone to be mapped and put into inventory. This is typically used when TagNet is not part of the initial tag commissioning workflow and thus has no knowledge of the object being read. This mapping is done using a*DEFAULT TagID and put into a location that represents the default Item and location to be used.

This binding leverages the variable RFDDTAG binding to send an event payload to an EF endpoint that performs the business logic using a number of custom supplied XSL style sheets to format the data into XML. This can be used whether the reader is server managed or via the SRC.

Logic

Collects whatever tags are seen during a read event cycle from a given portal and performs the following logic:

üResolves each tag to its mapped object attributes (Product, Asset, or Person) and pushes them in real time to the PEV display Client.

üProcesses IMOVE rules is so specified in Binding properties and automatically transfers inventory from location A to Location B. Sends out email if IMOVE has [EMAIL] keyword anywhere in description.

üSupports full GPIO script as a result of standard MATCH / NOMATCH/ NOTAG variables.

üTriggers Camera support if so configured in the Physical Reader profile

üSupports all Filter keywords (including *RSSI, *PRODTYPE, *ANTENNA)

üSupports Binding Email Exceptions. Email notification is sent when an error is encountered.

üSends out Tag Event data as listed below via an HTTP post to the user defined endpoint

❖Read Point attributes (Logical/Physical reader, antenna, timestamp, etc.)

üThe chart below shows what attributes are sent in the XML payload

üCan be used in RSSI zone configurations and supports system logging.

üCombines features from RFDPEVG and RFDPOST

Restrictions

Comments

 A video tutorial of setting up this binding is accessible from this link

This binding can be tested with the EF Dynamic Tag Event test utility

Files Updated

RFDTAGVS

Program Name

URI set to RFDDTAG

Binding Setup

Binding Properties

Email Notification

The email address to send binding specific alerts. Note: This overrides the default SMTP Recipient value under System Settings

UDA Grouping

UDA's at both the Asset instance level and Tag Inventory level instance can be included in the Dynamic XML by grouping them in a UDA Group Name

Dwell Time

Dwell time prevents the tag from being included in the web service request when seen again at the same gate when vehicle dwells there.  Refer to the the Binding Change for detailed explanations of this directive.

IMOVE Rules

Refer to the the Binding Change for detailed explanations of each directive.

Data Layout & Style Sheets

This section specifies the content type (XML today with JSON in future), the Data layout, and the style sheet names that have been edited to included your specific attributes. Note that these style sheets are for the individual tag transaction payloads as denoted by the *TAGLIST Data Layout selection.

The Style Sheets should be copied out of TagNet/Integrator/JSMInstance/RFID/ folder into a user defined folder (e.g. Custom-xsl) within the as they will be overwritten upon subsequent updates to TagNet. The folder path for the modified style sheets would then be TagNet/Integrator/JSMInstance/Custom-xsl