Field Settings

IndyGo is primarily focused on simple transactions and updating where a piece of equipment is located. That being said, IndyGo-style events offer nine fields to display within an action. The three non-editable fields that can be displayed for reference are Employee, Date, and Time. The remaining six fields, Department, Location, Sub-Location, Comments, Location (From), and Location (To), can be edited in the mobile application. If these fields are exposed in the mobile action, then the user must select a value before completing the transaction (except for comments).

Fields/Columns

Information Column

This column displays the field name of all information specified during an event.

Visible Column

Check the visible column next to the appropriate field name to make a field appear on an event. If you check a field as visible, set the order of the field (see further below).

Prompt Column

Is not used in IndyGo Events

Order Column

The order column determines the order in which the event fields are displayed. You will be warned when saving the equipment if you accidentally duplicate an order number.

Label Column

The Label Column is used whenever you want a custom field label different from the label in the Information Column.

Store With Equip Column

This column has three different choices, Always/Never/Only If Data Exists. These options refer to if and when the specified event data should be copied to the gage as Status Information. Choosing 'Always' will copy the event data into the appropriate equipment field, even if the field has been left blank. Choosing 'Never' will leave the equipment's status information as-is. A 'Only If Data Exists' option will copy information to the equipment's status fields only if the event information field contains data.

Store In Column

Each gage can have two types of current status fields stored with it. Almost all event information can be stored with the equipment after an event is complete, making it easy to filter equipment by its current and in-transit statuses. There are two different types of statuses: Current Status info and Transit Status info.

When a piece of equipment is involved in a 1-step transaction (a transaction that involves only one event), you will want to rely on the Current Status info to store the current information about the gage. An example of a 1-step transaction is a 'Check-Out' of a piece of equipment to the shop floor. The equipment's status is now 'Checked-Out,' the event will record who checked it out.

If the piece of equipment is involved in a 2-step transaction (a transaction that involves two events), then you will want to rely on the In Transit info for the first event and then the Current Status info for the second event. An example of a 2-step transaction is a 'Transfer To Lab' / 'Receive At Lab.' During the initial 'Transfer to Lab' event, you would move relevant event info data to the equipment's 'In Transit' status because the equipment is going to the lab, but until the lab receives it, then its actual status is unknown. Only when the lab gets the equipment can you assume that the event data is now the 'Current Status' info.

Additionally, there may be some information that you want to store in Both statuses. In that case, select Both for where to store the information.

Defaults Column

The Defaults column can be used to specify default values for event fields. For example, if you wanted to move the equipment's default department field into the event's department field, you could enter !DEPARTMENT in the Defaults column. IF using defaults in IndyGo, it is highly recommended that the user sets the choose equipment option as the first step in the action/event, as defaults will only appear AFTER equipment is added.

KIOSK_LOCATION can be entered into either the Location (From) or Location (To) columns to automatically populate the mobile device or kiosk "Device Location" by default. This may be particularly useful at a Kiosk for a Check-In event using the Location (To) field OR a Check Out event using the Location (From) field. The fields need not be shown in the interface to have that value defaulted and updated. Only Location Tree Locations that are flagged as "Is Storage" at the location level will successfully be defaulted to. If you plan on using a "Kiosk" type default location that is not marked as storage, then the Location (To) field will need to be exposed in the app. Although it will not default a value in the application, it will allow only "Is Storage" locations underneath that "Kiosk" type location to be selected.

Update Gage Field Column

This column can be used to specify equipment fields to populate with Event information once the event has been completed. For example, to move the event's department field to the equipment department field, you would enter !DEPARTMENT into the Update Gage Field column. Location (To) and Location (From) fields can only truly work with their designated Storage ID, Current Location ID, and Transit Location ID fields. These can be set in the Update column or the "Store In" column for current and transit-style fields.