SRC Read Event Settings

SRC Read Event Settings ** this to be reworked into another grouping to support mining for logical Read events (non-triggered) for TEC and AHI. There will be a new job similiar to ProcessSRCEvents that will be used for AHI.

This function enables changing/updating values specific to SRC behavior as described below. These parameters control event management in a non-triggered environment whereas the duration of a read event needs to be determined based on start/end time of tags being seen/not seen. As a result emails are sent out to customer email groups notifying of what tags were seen coming or going out of a choke point (e.g. yard gate or similar).

	Query Time Buffer (ms)
	The duration in milliseconds in which RFDPHLOG records in the database must be logged before they will become available for an event. Why? ** to account for transactional latency. eg. 30 seconds where logical reader has [EMAIL]. Job is running and only looks for PHLOG + Buffer time. read all tags with timestamp. at this point create an 'SRC Event (SRC_Read_Events + tag events)' Situation is compouned when you have multiple physical readers all reporting at different times.

	Transaction Time Delta (ms)
	The duration in milliseconds allowed for an inventory transaction to be linked with a RFDPHLOG logging record. ** 10:00:00 to account for the delta between phlog and LOCIH timestamps. logic allows to singulate the correct transactions for the physical log event.

	Event Wait Time (sec)
	The duration in seconds in which the system will wait for more tags after a scan. This timer gets reset whenever a tag is scanned during the event. If this timer expires, an alert is sent out. ** (10) tags logged, going to wait this time period to see if more tags come in.

	Event Limit (sec)
	The duration in seconds in which the system will end a read event if tags are still being scanned. If this timer expires, an alert will be sent out even if tags are still being actively scanned at the read point. ** exception if rogue tags being read, or poles being dumped within read zone.

	Employee Tag Alias
	Employee tags will reference this alias when displayed in email alerts ** Crew tags that are linked to trucks logged within the same timestamp constraints.

	Companion Tag Alias
	Tags associated with the Inventory Type 'COMPANION' will reference this alias in email alerts ** This is the label on email outboundWO tags that relate to Inventory type of 'COMPANION' WO is container is Container, not a UDA?

	Enforce Event Limit?
	Determines if the Event Limit time above is enforced ** turn off #4

	Clear Events with no Transactions?
	Determines if read events that generate no transactions are cleared from local storage ** Time period to clear working files if no LOCIH generated. Tag is already in location or truck goes through portal but no 'inventory trans' took place, or unmapped tags.

	Save to File?
	Determines if email alerts are saved in HTML format to the local server after they are sent. These will be saved to the EF application directory. ** Audit trail backup, no auto recover on send at this time. Phlog table is flagged so would have to unflag to resend if neccesary.