At the heart of this second goal is our insistence that we should further not assume exactly what our customers want to actually do with the data. We want that data to be available for them to do whatever they need it for, and to be able to fully leverage any and all existing systems at the location.

Visio Logger integration happens through software interfaces that are exercised by the system at 6 distinct times within the visitor data collection activity. Source code for some of the integration tools Visio Logger ships with is installed when the system installs. That source contains full information on the structure and nature of these interfaces.

These external tools can be activated when:

1. Before visitor data collection starts. During this event, external software might make changes to the sign in process. For example, the available "selections" in a field menu could be automatically changed based on the current day and time. An external system, for example, a scheduling system, could provide the available values, perhaps, which companies are expected to arrive in the building on this day. Then, the visitor would be selecting one of these values from the menu.
2. As each "page" is submitted. Visio Logger organizes fields into pages - which can be thought of as a set of fields provided by the visitor in one step. When a signature pad is in use, and either the pad keyboard or a menu is presented to the user, a page has 1 field on it. However, in Kiosk mode, you can ask for any number of data points. In any case, as each "grouping" of these field has been submitted by the visitor - the components registered to handle this event get called by Visio Logger. It is within this processing that you can inspect all of the currently supplied data and do anything at all with it. You could consult an external system and with any returned results - actually set the values of other fields. Note that Visio Logger presents pages in series to the visitor. When a page has fields whose values are already supplied, Visio Logger skips showing that page to the visitor. Essentially changing the "flow" of the sign in process based on information the visitor has provided. In fact, Visio Logger ships with the InnoVisioNate Page Submitted processor that lets you configure this flow, so you can essentially capture multiple different "sets" of fields based on your visitor type.
3. Whenever a record is changed. This action does not strictly occur during visitor sign in time but when data for that visitor changes for any reason. One example is when an Action is taken, that row for that visitor will receive a timestamp for that action. And another is when a field is editable, and staff clicks on the cell and changes the value, this will cause this integration tool to activate.
4. When an action is taken. Again, this does not happen during visitor sign in time, but when staff actually clicks on the button that represents the action in that visitor's data. One of the integration tools shipped with Visio Logger includes the ability to snap a picture of the visitor. Therefore, you can set up an Action field(s) to take this picture anytime from any computer.
5. When the record is complete. At this point in time, Visio Logger has collected all of the information required of the user and the system is ready to cycle to the next visitor. This is an excellent opportunity to print a badge (such a tools ships with Visio Logger) or to provide information to an another system, as just 2 examples.
6. As each key is taped out by the user on the signature pad keyboard. This event is implemented to assist in developing value recognition technology, such as auto lookup, when a visitor is entering data. At this point, you can see the "thus far" entered data and perhaps consult an external database to see if that uniquely matches some data record, and if it does, provide data from that system, including, not just the completed value, but any other value as well.