Binding Function

RFDDTAG

Binding ID

EF_LOGICAL_EVENT

Binding Description

Posts Read Events to EF Endpoint for Logical Grouping

Purpose

This is a universal binding that enables enhanced functionality within the TagNet Extension Framework (as listed below in Post EF logic). This leverages the variable RFDDTAG URI to send an event payload to an endpoint that performs the business logic using a number of custom supplied XSL style sheets to format the data into XML.

Note that this Binding 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:

Prior to sending to EF

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

ü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. Note: SRC read events use their actual read event time as the Inventory transaction time and not when the transaction is processed (server time). This is to account for different time zones of where the SRC may be relative to TagNet Server time zone as well as transmit latency between SRC location and server.

ü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 EF defined endpoint. The box below shows the generated XML.

❖Tag Event attributes (Binding ID, Location ID, Schedule timestamp, Event Cycle, etc.)

❖Tag attributes (TagID, Object Type, Physical reader, Seq, timestamp, Antenna, RSSI)

Logic within EF after receiving payload

üProcesses IMOVE rules (if configured here) and pushes to the EF browser based Event Viewer

üProcesses Zone based directionality logic if Zone passed in payload (as opposed to antenna ID) or Reader/Antenna makes a match in the Zone file. See further logic details below

üProcesses Departmental substitution logic when *ANY  (from location) and *SOURCE (to Location) specified in the IMOVE Rule. This if for customers that introduce a level in the inventory location matrix that implies asset ownership regardless of what physical location the asset is moved to. For example: if a matrix is setup as Facility.Building.Dept.Room.Location and the tag is moved, the Dept value (Level3) will be moved to the same (level3) of the target location. Refer to Inventory Movement Rules for further examples.

üEnables an unmapped tag that is seen at a read point to be mapped and put into inventory. Configure in Imove API Settings

üEnables certain object fields to be updated during an IMOVE rule. Configure in Imove API Settings

üEnables Event Group logging to occur for directional zone based logic. Configure in Imove API Settings

üEnables specialized 'Hold State' logic evoked after a successful IMOVE transaction. Configure in Imove API Settings

Restrictions

Comments

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

Files Updated

RFDLOCIN, RFDLOCIH (Insert), RFDTAGVS (tag last seen by Location/Reader/Ant), RFDTAGPR (tag last seen globally),  TagHoldState (if feature enabled)

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 when seen again at the same read point until dwell time expires.  Refer to the the Binding Change for detailed explanations of this directive. NOTE: If using Zone based logic - Dwell time at binding level should not be used here if as this is controlled at the Zone level

IMOVE Rules

Refer to the the Binding Change for detailed explanations of each directive. NOTE: These directives are ignored here as the EF manages IMOVE rules as well as event visualization via its Browser based event viewer.

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 to support this binding need to be copied out of \TagNet Extension Framework\EF Web\custom-xsl folder into a user defined folder (e.g. Custom-xsl) 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