Event Information

Besides adding equipment, actions can be designed to allow user-specific inputs to update related equipment dynamically. In an action, the event information screen can either appear as the 1st step, 2nd step, or not at all. IndyGo events are designed to be simple transactions that generally do not require much or any employee training. Event Fields that can be accessed and manipulated in an event are Employee, Department, Location, SubLocation, and Location To. Fields that can be exposed but are not editable are Event Date, Event Time, and Location From. Fields can be used similarly to IndySoft Client events in that values can be defaulted once the equipment is added, and those fields can update specific equipment characteristics.

Selecting Event Field Values

Selecting event field values can be done in up to 3 ways.

Tapping to search will pull up a related list for that user to select from. Result sets will lazy load into the application and not pull the entire result set to avoid time lags for large data sets. Lists for related fields will be looked up based on field type, and company-related information will be used with the following priority.

Scanning a related QR code from the device's native camera

Scanning a related barcode from the external device's native barcode camera **** is probably the most efficient way to select a value. When landing on the Event Information screen, the user can always scan the top value without tapping that field. Other fields below (if any) must be tapped to enable scanning the code.

Scanning or selecting a value for these event fields must always be validated against a list. Free form entry is prohibited for any field outside the "Notes" field. Therefore, the logged-in user's lists for corresponding fields will be based on a.) the field type...Department, Employee, Location, and b.) a company under which the list is stored. The company values per list will follow the following logic.

1. Default company valuesfor that related field. Only default companies saved for the related logged-in user's "DEFAULT" location will be used. Example User/Location Settings

2. If no default company value exists, the last company the user accessed in the main system (after official logout) will be used.

3. If no default company exists and no last company was ever accessed in the system, the related logged-in employee's company for the list will be used.

Finally, regardless of whether the Event Information screen is first or second in your IndyGo "Action," no fields may be left blank to finish or proceed to add equipment. (The exception is the "Notes" field.)