Settings

The settings screen for the IndyGo interface allows the user to manage local settings at the device level. Settings are broken into several categories: Hardware and Devices, Configuration Options, Login Options, and General.

Manage Device Connectio n -- The user can troubleshoot a connected device, connect to alternate devices, or forget the current device. Refresh current connection might be used if you cannot connect to your desired device. Ensure your device is powered on and in range, and try refreshing your connection. Pairing with a new device allows users to select the supported device they want to connect to. It automatically forgets any current device you might be connected to. Forget Deviceremoves any connected device from the local cache and allows the app to run without any native barcode or RFID reading options.

Hardware and Devices

RFID Options -- Only appears if the supported device has RFID (UHF) scanning capabilities. From here, the user can test High vs. Low power settings on tags without associating them with the main system.

The low power setting is adjustable in the IndyGo application. Low-powered scanning is used by default when pairing equipment and is an option in the equipment selection screen for IndyGo-style events. Much like the high-powered scan, the scan will take place as long as the trigger is pulled. It is recommended when you want to be certain of the tag you are directly scanning. The higher the power used, the greater the likelihood that you could scan a tag that is not right in front of the reader. 27 is the maximum power for the scanner in low-power mode. Every three units subtracted from 30 cuts the power in half. For example, 27 is half of the power of 30 (30 is full power). The low power setting is set to 15 by default, 1/32nd of the full power setting.
The high power setting is set to maximum (30) and cannot be adjusted. This setting is used in the "Search" screen and the "Locate" option by default and can be employed in the equipment selection screen in IndyGo events. In this mode, holding down the trigger will continue scanning the area for assets at the maximum power of the reader.

BLE Tag Options, if enabled, will allow the user to: pair assets with BLE tags, search for those related assets from the search screen, and search for related tags in actions.

**Enable Camera Options,**if disabled, will hide camera-based options and not allow the end user to take pictures of assets (also a security setting in the main system), nor will they be able to use the camera to scan any QR codes.

Kiosk Modewill be disabled by default, providing the user with a specific mode where the workstation is generally stationary. Therefore, the application allows certain options to be enabled and disabled, different from a "Mobile" or "Kiosk-style" setup. If enabled, Kiosk mode allows for screen rotation for the application, specific kiosk style events to be shown (Workflow Configuration Option in main client), "Locate" type features are not visible, and camera options are hidden. After every "Action" or "Event" is performed, the user will be prompted to decide whether to commit another transaction or log out. If the user walks away and does not respond to the prompt, they will be automatically logged out after 30 seconds. If the screen is inactive for 45 seconds, the workstation will present a message asking if the user is still there. If no response is given in 15 seconds, an auto-logout will occur. Kiosk mode can only be enabled by system administrators who log in at that workstation. If a workstation is in "Kiosk Mode," then the visibility of options in the settings screen is limited to options in the "General" section.

Configuration Options

Auto Sort by Due Date will be disabled by default. If enabled, all assets added to your Actions or Events will automatically be sorted by the due date with the earliest due dates first. If disabled, then the assets will appear as they are added. Enabling this is generally recommended for use with RFID inventory-type events for updating locations if the job is also to collect past due or coming due assets.

Vary Sounds by Due Date will play different sounds when adding equipment to actions based upon the Schedule Alert Days setting. If the item is coming due or is past due, a distinct chime sound will play. This would be particularly useful for adding assets to an action with the RFID scan.

Show Company Name will be enabled by default. This allows the user to see the Company name for the equipment in the search screen and when adding/searching for equipment in "Actions."

Hide Search Screen will simply only show the actions and settings screen.

Device Location is recommended for use in Kiosk-Style situations but can be used otherwise if desired. This allows the user to assign a specific location to the scanner or workstation. Only system-wide locations with a " Kiosk " type can be accessed in this list. If an IndyGo event has a default value for the Location (From) or Location (To) field, which is exactly "KIOSK_LOCATION," then the IndyGo event in the mobile app will know the default location specified at the device. That default location will only populate in the event once the first piece of equipment is added.

Login Options

Hide Username and Password Login hides the option to enter the username and password from plain sight on the login screen.

Enable Camera Scan-In allows the user to scan a QR code with your mobile device's native camera in order to log in. The value which is scanned in is not the password, but rather Passive RFID ID for the employee record.

Enable Connection Edit If disabled, the user cannot edit the connection setting from the login screen.

Common User Login allows an administrator to save an encrypted username and password locally. This can provide additional login options for employee with records which have a passive RFID ID stored but do not have their own dedicated username and password. This requires that a scan-in functionality take place which pushes that related employee's Passive RFID ID to the log in screen for authentication. Users who authenticate in this manner will have access to actions and equipment based upon the common user's settings.

Enable Guest Mode Login can be used in conjunction with the Common User Login and will show the option on that station's log in screen to "Log In as Guest." This would authenticate using the common user credentials, but put the user in a mode where they can only access equipment based upon that common user's settings. Guests can look up equipment information from the search screen, but will not be able to perform any actions which write to the database; Pairing/unpairing assets, taking pictures of equipment, and performing actions would all be disabled for guest users.

General

Send Feedback will allow the end user to email IndySoft support as long as the device is set up to allow the user to email.

Privacy Policy

App Version

Deregister Devices can be used by System Administrators to remove registration from a device.