Tracker Application

Overview

The BOS Enterprise Tracker application is a lightweight executable that runs as follows: 

• Dual Mode (Connected and Offline) - The application runs on a Local database which is populated from and then replicated to the Live database when an internet connection exists. The Local database is a metadata backup of the Live database.

• Connected Mode - Connects directly to the Live database without an offline option.

Note: Only the Field Service and Deliveries modules support Dual Mode.

Setting up

Tracker.exe can be downloaded from Tools or the Shared Drive\Downloads\... folder.  For Dual Mode, a Data folder needs to be created and contain a metadata backup of the BOS Enterprise DB which must be made from the Live DB after it has been upgraded.

Click the Setting icon in the Login window to open a utility that will create the INI file for you based on your selections/inputs.the selected mode - Connected or Dual.

The Database Connection strings need to be added to the TRACKER.INI file. Following is an example of how the INI file must be formatted:

• [SERVERDB] path = server:localDBpath

• [LOCALDB] path = server:localDBpath 

Note: For Connect Mode, the [LOCALDB] path = Live DB and the [SERVERDB] item is not required.

How Dual Mode works

The Client App can run in Offline (Red icon) or in Online (Green icon) mode. The local database is always updated and if you are in Online mode, the Server will also be updated in real time. If the application is Offline, the updated records are flagged and as soon as you go into Online mode, the Server will be updated with all the changes that have been made.

The Local database starts out as a metadata-only copy of the Server database which does not contain any data. The first time you log into the Client, therefore, you need to be Online in order for your User and Transaction detail to be downloaded to the local database.

The Local database is a temporary database that only contains a subset of data you have been working on and should frequently be replicated to the Server. When you exit the Client app, you will be warned if there are records in the local database that have not been uploaded.

How to enable Modules

The following Modules can be enabled in the Transaction Settings > Tracker Module group.

The following Modules are enabled with a Yes/No setting:

• Deliveries - Obtain digital signatures to confirm the Delivery of Items.

• Field Service - Take pictures to confirm the work that has been completed and obtain digital signatures to confirm Timekeeping 

• Job Tracker - Use a touch interface or barcode scanner to track the progress and duration of jobs on a factory floor. 

The following modules are enabled by selecting the Transaction that will be used to Issue or Receive - These modules are only supported in Connected Mode

• Issue Inventory (Select the Issue Transaction) - Applicable to Inventory Items only

• Issue Goods  (Select the Issue Transaction)  - Used as proof of Issue/Delivery for any Items or Services. For example, it could be used to control the flow of Items that are sent to outwork suppliers.

• Receive Inventory  (Select the Issue Transaction) - Applicable to Inventory Items only

• Receive Goods  (Select the Issue Transaction) - Used as proof of Receipt/Delivery for any Items or Services - for example, it could be used to control the flow of Items that are received from outwork suppliers.

Login

Enter your Password or PIN using the number pad provided and click the Login button.  When in Dual Mode, the green Login button will connect to the Local as well as to the Remote databases. The red Login button will connect to the Local database only.  The first time you login in, you need to use the green Login button to fetch user information and settings from the server. When the same User logs in again, the Settings are not updated from the Server. The Refresh button in the Menu page header can be used to refetch Settings from the Server

When in Connected mode, you only have the option to use the green Login button.

Logout

Click the Logout button to close the connection and navigate to the Login screen. When you log back in, the application will open to the module you were working in when you logged out. 

Exit Application

When you exit the application, you will be prompted about the following:

• One or more records have not been uploaded to the Server

• There are one or more open Timekeeping records