Terminal Profile Setting Types are assigned to Terminal Profiles on the Terminal Profile Setting form. Each setting represents a specific function, such as such as Offline Charge Element Validation and Biometric Enforce.
If a Terminal Profile setting is modified, the application server and terminal must both be restarted in order for the new setting to take effect.
Note that a Terminal Setting will override a Terminal Profile setting. For example, if a terminal is configured to enforce biometric authentication (BIOMETRIC_ENFORCE), but its Terminal Profile is not, employees will still be required to use a finger scan.
If you are running the Mobile Client and your mobile device has GPS enabled, your location will be recorded (Latitude, Longitude, and Accuracy). These location values can be viewed in the Sign Audit form, Action form, and the daily and punch time tabs of the timecard.
A location’s Accuracy level depends on how the location was recorded. For example, a location recorded using GPS or a Wi-Fi connection will be more accurate than a location recorded using cell phone tower triangulation (e.g., 10 meters vs. 1000 meters).
You can use the ACCURACY_TOLERANCE_LEVEL setting in a Terminal Profile to restrict signing and event posting based on a location’s accuracy level.
If a recorded location’s Accuracy is greater than the ACCURACY_TOLERANCE_LEVEL, the user will not be able to sign the timecard or add/modify/delete the event.
In the Setting Value field, enter the Accuracy level in meters that you want to enforce.
If you do not add this setting to your Terminal Profile, the Mobile Client will not restrict users from signing or modifying timecards based on the Accuracy of their locations.
Identifies the badge group that is allowed access to terminals using this Terminal Profile.
Note: Login Event Name has to be LOGIN_XML_BADGE_GROUP
This setting is used to designate an InTouch terminal as a biometric verification terminal. If the terminal has a fingerprint scanner and this setting is enabled, employees can log into the terminal using a fingerprint instead of a badge number.
Set BIOMETRIC_ENFORCE to Enabled if you want employees to log into the terminal using the fingerprint scanner.
Set BIOMETRIC_ENFORCE to Disabled if you do not want employees to log into the terminal using the fingerprint scanner.
If the terminal has BIOMETRIC_ENROLL (see below) enabled, then typically the BIOMETRIC_ENFORCE setting will not be used or will be disabled.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
See Also: Biometric Configuration
Character Set. If you want to use a character set other than default value ISO-8859-1 (Latin 1), enter it in this field.
Determines the date format used in date fields for elapsed events on a terminal (9540, 9300/9500,or 9520 terminal types). The default value is yyyyMMdd. For example, January 2, 2011 would display as 20110102.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
Indicates whether events posted on this terminal will activate a terminal’s relay. Select Enabled or Disabled.
When the event activates a relay, the terminal gives an output signal such as a light going off or a door opening. For example, when an employee scans their badge, the terminal may cause a door to open.
In addition to this Terminal Profile Setting, you must also define the events that will activate the terminal’s relay. To do so, use the Event Relay tab in the Events form.
Note: Event Relay is only supported on 9540 and 9520 terminals. You will need to know how many relays are on the terminal and which relays are already in use. Consult your terminal’s operation manual for information.
When a terminal is offline, this setting is the length of time the relay (specified by EVENT_RELAY_NUM_OFFLINE – see below) will be activated when the user posts an offline transaction.
In offline mode, terminal relays are not activated by specific events. Instead, you can use the EVENT_RELAY_INTERVAL_OFFLINE and EVENT_RELAY_NUM_OFFLINE Terminal Profile Settings to activate a relay each time the user posts an offline transaction.
EVENT_RELAY_INTERVAL_OFFLINE is the number of seconds the relay will activate for an offline transaction posting. The relay that activates is specified by the EVENT_RELAY_NUM_OFFLINE Terminal Profile Setting.
When a terminal is offline, this setting specifies which relay will be activated when the user posts an offline transaction.
In offline mode, terminal relays are not activated by specific events. Instead, you can use the EVENT_RELAY_INTERVAL_OFFLINE (see above) and EVENT_RELAY_NUM_OFFLINE Terminal Profile Settings to activate a relay each time the user posts an offline transaction.
EVENT_RELAY_INTERVAL_OFFLINE is the number of seconds the relay will activate for an offline transaction posting. The relay that activates is specified by the EVENT_RELAY_NUM_OFFLINE Terminal Profile Setting.
This setting will add the Help button and corresponding help screen to the login screen of B-Web 9300/9500 terminals.
For the Setting Value, select the event that will display the Help button and help screen. Available options are events of type INFO:TERMINAL as defined in the Events form.
By default, a stop stage screen is displayed when time reporter stops labor. However, when this setting is enabled and there are no visible stop stage prompts, the stop prompt screen will not be displayed. The user will only see a message that the labor was stopped.
This setting is used to assign an InTouch Config record to a terminal. An InTouch Config record defines the settings used by InTouch terminals with Shop Floor Time.
In the Setting Value field, the available options are defined in the InTouch Config form.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
Enforces a password for using the local fingerprint enrollment feature on a terminal. Enter a numeric password in the Setting Value field.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
When this setting type is enabled, the terminal will not display CLOCK IN events (such as IN, BREAK, MEAL, TRANSFER, and CLOCK OUT). If the setting is not enabled, all events in the Menu Tree of the Terminal Profile's Menu Group will display.
Allows the system to display the name of the person that logs on to the terminal on the menu form.
This setting indicates whether Offline Charge Validation will occur on the terminal. Offline charge validation allows charge elements to be validated locally on the terminal, so that users will not be able to enter an invalid work order number, project number, or other charge element when the terminal is not connected to the server.
Enabled Offline Only: Select this option if you only want offline charge validation to occur when the terminal is offline. When the terminal is offline, charge elements will be validated against a file that resides locally on the terminal. When the terminal is online, charge elements will be validated against the database.
Enabled Online and Offline: Select this option if you want offline charge validation to occur when the terminal is online or offline. Charge elements will be validated against a file that resides locally on the terminal, whether the terminal is offline or not.
Disabled: Select this option to disable offline charge validation. Charge elements will only be validated against the database (when the terminal is online). If the terminal is offline, no validation will occur.
Note: To limit the number of charge element records that can be downloaded to the terminal, use the MAX_CHARGE_ELEMENT_RECORDS setting in the Terminal Setting form.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
When this setting is enabled for a terminal (via Terminal Profile Setting or Terminal Setting), you can use the Document Transfer button in the Terminal Monitor form or the TRIGGER_OFFLINE_VALIDATION_DOC_TRANSFER service to trigger the transfer of updated charge element data to selected terminals for offline validation.
This setting defines the Charge Filter Policy that will be used for Offline Charge Validation. The Charge Filter Policy determines which charge types will be validated when the terminal is offline.
Note: If you are using Offline Charge Validation, you also need to enable the OFFLINE_CHARGE_ELEMENT_VALIDATION setting.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting determines whether offline charges will be validated against an employee’s assigned Charge Filtration Group. The Charge Filtration Group is part of the Charge Element Filtration feature, which is used to limit the charge elements to which an employee can charge their time. The OFFLINE_CHARGE_PERSON_FILTRATION setting makes Charge Element Filtration available when the terminal is offline.
Select Enabled if you want to validate offline charges against an employee’s assigned Charge Filtration Group.
Select Disabled if you do not want to validate offline charges against an employee’s assigned Charge Filtration Group.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
Note: If you are using Offline Charge Validation, you also need to enable the OFFLINE_CHARGE_ELEMENT_VALIDATION setting.
This setting represents in seconds how often the system will attempt to connect to the server when the terminal is offline. This setting overrides the Check Online Time setting in the Terminal Type form.
By default, the system will attempt to connect to the application server based on the Check Online Time setting in the Terminal Type form. When the terminal is offline, the system will attempt to connect to the server ten times faster than this setting. For example, if the Check Online Time is 60 and the terminal is offline, the system will check that there is a connection every 6 seconds (60/10). If you want to configure a different length of time when the offline terminals will check for a connection to the server, you must use the OFFLINE_CHECK_ONLINE_TIME setting.
The OFFLINE_CHECK_ONLINE_TIME setting can be used when you want the offline check to be performed less frequently. For example, if you are operating terminals in COMPLETE_OFFLINE mode, you may only want to perform the offline check every three minutes to reduce the amount of network communication.
Enter a number of seconds in this field; decimal values are not allowed.
This setting applies to the Offline Person Validation feature. It offers support for validation of data in offline mode locally on XML based terminals. The support includes validation of the following authentication credentials:
Badge Number
Biometric Validation
Biometric Exempt Validation
Terminal Filtration
You must enable the setting in order to allow authentication credentials.
Enabled Offline Only: Local/offline person authentication will take place when the terminal is in Offline mode only. The terminal will validate the badge against the local/Offline Person repository (Person.XML) to check if the badge is valid or not.
Enabled Online and Offline: Local/offline person authentication will take place in both Online and Offline mode.
If the terminal is Online, the terminal will validate the badge against the local/offline Person repository (Person.XML) to check if the badge is valid or not. If the badge is not valid the terminal does not contact the server but displays an error message (for example, "Invalid Badge"). If the badge is valid, the terminal sends the transaction to the server, where it gets validated the second time.
If the terminal is Offline, the terminal will validate the badge against the local/offline Person repository (Person.XML) to check if the badge is valid or not.
Disabled: The setting is disabled.
This setting can be configured as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
When this setting is enabled for a terminal (via Terminal Profile Setting or Terminal Setting), you can use the Document Transfer button in the Terminal Monitor form or the TRIGGER_OFFLINE_VALIDATION_DOC_TRANSFER service to trigger the transfer of updated person data to selected terminals for offline validation.
This setting represents in seconds how often the system will attempt to connect to the server when the terminal is online .It overrides the Check Online Time setting in the Terminal Type form.
This setting defines the Rounding Policy that will be used for transactions posted on this terminal. The Rounding Policy form is used to configure the rules that determine how and when time-related activities, such as Clock Ins, Clock Outs, Breaks, Labor start/stop, etc. are rounded.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting determines how time reporters are prompted to start and stop labor on a terminal.
Note that when adding punch transactions in the web timecard, only STARTSTOP prompting is used.
STARTSTART: Also known as Start Only prompting. The time reporter is required to start labors. When starting a labor, the system checks whether any existing open labors need to be stopped. The time reporter must stop the open labors before starting the new labor. If the time reporter stops the open labors, but does not start a new labor (clicks “Cancel”), then the open labors will not be stopped. A stop labor action must be followed by a start labor action, unless the time reporter is clocking out. The stop labor and subsequent start labor will have the same timestamp. The STARTSTART prompting scheme applies to Single, Batch and Multi Labor.
For example, a time reporter is beginning a new task and posts a labor event for it. Unless this is the first labor of the day, the system will prompt for the quantities worked, completed, etc. of the previous labor that is still open. After the time reporter enters these quantities, the time reporter is prompted for the order number, operation number, etc. of the new labor. The time reporter then returns to the badge screen. When the time reporter begins the next task, the time reporter will post a new labor event for it, but will first be prompted to close the previous labor.
STARTSTOP: The time reporter is prompted to start a labor and to stop a labor. After the labor has been stopped, the time reporter is not required to start another labor. STARTSTOP applies to Single, Batch and Multi Labor.
For example, a time reporter begins a new labor task and posts a Work Order event for it. The time reporter enters the order number, operation number, and similar information about the work order. Two hours later, the time reporter logs into the terminal again to post a Project event. However, the time reporter is first prompted to stop the open Work Order. The time reporter must enter the quantities for the open Work Order and stop the Work Order labor before posting the Project event.
STOPSTOP: Also known as Stop Only prompting. The time reporter will post an event when the labor is complete. When stopping the labor, the system displays all start prompts and stop prompts. The start time for the labor is set at the last activity. If it is the first labor of the day, then the start time is set to the clock in time. STOPSTOP prompting applies to Single and Batch Labor. It does not apply to Multi Labor.
For example, a time reporter clocks in at 8 a.m. and immediately starts to work on WorkOrder101. At 10 a.m., the time reporter posts a Work Order event for WorkOrder101. The time reporter will report all quantities for the work order and stop the labor. On the timecard, the labor will show a start time of 8 a.m. and an end time of 10 a.m. If the time reporter is posting a Batch labor, the time will be divided evenly between the labors in the batch.
See COLLECTION_TYPE for information about Single, Batch and Multi Labor.
This setting assigns a terminal relay schedule to a terminal. A terminal relay schedule is used to schedule one or more terminals to activate a relay signal which can perform an action such as sounding an alarm or opening a door. A relay schedule can be defined for a particular day of the week and time of day. For example, a terminal may be configured to ring a bell for 10 seconds during the start of a shift (9:00 a.m.) and the end of a shift (5:00 p.m.) every week day (Monday – Friday).
For the Setting Value, select the name of the terminal relay schedule you want to assign to the terminal. Available options are defined in the Terminal Relay Sched form.
The RELAY_SCHEDULE setting is typically assigned to a Terminal Profile (as a Terminal Profile Setting Type). If it is assigned to a terminal, the Terminal Setting will override the Terminal Profile setting. For example, a group of terminals in a facility are all configured to ring a bell for 5 seconds when the shift starts at 7:00 a.m.; this relay schedule is assigned to a Terminal Profile. However, one of the terminals has a relay schedule that also opens a door for 10 minutes when the shift starts. This relay schedule is assigned as a Terminal Setting. When the shift starts, this terminal will activate the door opening instead of ringing the bell.
This feature is supported on B-Net 9520 and B-Web 9300/9500 terminals. You will need to know how many relays are on the terminal you are using and which relays are already in use. Consult your terminal’s operation manual for information.
When this setting is enabled for a terminal (via Terminal Profile Setting or Terminal Setting), you can use the Document Transfer button in the Terminal Monitor form or the TRIGGER_OFFLINE_VALIDATION_DOC_TRANSFER service to trigger the transfer of updated relay schedules to selected terminals.
The Save on Enter feature allows a user to save event information by pressing ENTER on the client keyboard instead of having to press SAVE.
Start Prompt: Start stage event prompts will be affected by the Save on Enter feature. Start prompt values will be saved when user presses Enter.
Stop Prompts: Stop stage event prompts will be affected by the Save on Enter feature. Stop prompt values will be saved when user presses Enter.
Always On: Start, stop and no stage event prompts will be affected by the Save on Enter feature. All prompt values will be saved when user presses Enter.
This setting is also available as an Event Type Setting and an Event Setting. Event Setting overrides Event Type Setting which overrides Terminal Profile Setting.
This setting enables or disables the display of seconds in the clock field on a B-Web 9300 or 9500 terminal. The seconds display will update every second.
This setting is disabled by default (seconds will not display). If you do not include this setting in your Terminal Profile, the setting is disabled.
If SHOW_SECONDS_IN_CLOCK is enabled, the terminal will need to use its minimal processing resources to update the seconds display. If the terminal is busy processing transactions, the seconds display may skip an update. To make sure the terminal use its resources most efficiently (for online transactions and offline status checks), it is recommended that you disable SHOW_SECONDS_IN_CLOCK unless absolutely necessary.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
When this setting is enabled, and there is only one event available to the user, the system will attempt to perform the event as soon as the user logs on to the terminal.
The Smart Clock
feature allows the user to scan a badge (i.e. barcode scan, card
scan, proximity badge or Biometric) and have the system determine
the proper type of the punch, such as Clock, Meal, Break, etc. Full
functionality of Smart Clock is dependent on the proper implementation
of schedules. If there is no schedule in place, only a CLOCK
event is allowed.
You must also define your Smart Clock Events.
This setting is also available in Event Type Setting and Event Setting. Event Setting overrides event Type Setting which overrides Terminal Profile Setting.
The STATE_CODE setting is used to populate the F_STATE_CODE prompt when posting a PROJECT, PROJECT_ACCOUNT, PROJECT_ORGANIZATION, or PROJECT_ACCOUNT_ORGANIZATION event. The Setting Value should represent the State Code for the Facility, Terminal, or Terminal Profile where the event will be posted.
The STATE_CODE setting can be assigned to a:
Person Group Setting for Person Group Type FACILITY
Terminal
Terminal Profile
When a person posts a PROJECT, PROJECT_ACCOUNT, PROJECT_ORGANIZATION, or PROJECT_ACCOUNT_ORGANIZATION event, the STATE_CODE that is used for the F_STATE_CODE prompt depends on whether the event is posted from the Web or from a data collection terminal:
If the event is posted from a data collection terminal, the STATE_CODE will come from the Terminal Setting for the terminal where the event is posted. If the terminal does not have a STATE_CODE Terminal Setting, the STATE_CODE will come from the Terminal Profile Setting for the terminal where the event is posted.
If the event is posted from the Web, the STATE_CODE will come from the Person Group Setting for the FACILITY of the person for whom the event is posted.
Use this setting to prevent events from being posted at a terminal.
The Setting Value is the name of an Event Group. The events in this Event Group cannot be posted at the terminal.
For example, if you only want users to Clock In at a terminal, use the TERMINAL_EVENT_RESTRICTION setting to select an Event Group with a CLOCK event that has the Event Stage set to Stop. Clock Outs will then be restricted from the terminal. If a user who is already clocked in attempts to clock out at the terminal, an error message will display that the clock out is not allowed.
You may want to use this setting if you have dedicated clock in and clock out terminals.
This setting can be added as a Terminal Setting or a Terminal Profile Setting. A Terminal Setting overrides a Terminal Profile Setting.
This setting determines how forms such as Accrual Balance and Daily Timecard will display on a terminal. These forms are included in the Form Profile under Terminal Forms.
Form profiles are created in the Form Profile form.
The TERMINAL_FORM_PROFILE setting will override the Form Profile System Setting, Person Group Setting, or Person Setting.
This setting assigns a Terminal Off Policy to the Terminal Profile. The Terminal Off Policy determines the Operating Mode of the terminals. The Operating Mode defined in this policy determines how the terminal will collect and process offline data.
Currently the only available Operating Mode is COMPLETE_OFFLINE. If a terminal is assigned a Terminal Off Policy that has the COMPLETE_OFFLINE Operating Mode, the terminal will operate in offline mode regardless of whether it can communicate with the application server. The terminal will collect transactions and store them locally, without attempting to transmit this data to the application server. The terminal will not send these transactions until its Operating State is changed (via the Operating State form or the COMPLETE_OFFLINE_STATE_CONTROLLER service ).
See Permanent Offline Data Collection with Scheduled Data Pull for more information.
Defines in seconds the length of time that an error message will display on a terminal.
Valid values are 0.1 up to 10 seconds.
Note: Fractional seconds are not supported on LANpoint 7, LANpoint 8, MC70, or MC75 terminals. Do not enter a decimal value for TIMEOUT-ERROR for these terminals.
If your terminal beeps when displaying a message, the length of the Offline Response Time will affect the length or number of beeps you hear. For example, if your terminal normally transmits three beeps with an error message and you decrease the offline Response Time to 0.1 (1/10 of a second), you will only hear one beep with an error message.
If the terminal is configured to allow Event Relays, the duration of the relay signal (e.g., a light going off or a door opening) may be different than the length of time the error message displays on screen. The duration of the relay signal is configured by the Event Relay form for online transaction, and by the EVENT_RELAY_INTERVAL_OFFLINE and EVENT_RELAY_NUM_OFFLINE Terminal Profile Settings for offline transactions.
The duration of the local offline validation error is always 3 seconds; this value is not configurable. The local offline validation error displays when the OFFLINE_PERSON_AUTHENTICATION Setting Type is enabled in the terminal's profile. See Offline Person Validation for more information.
Defines in seconds the length of time that a success message will display on a terminal.
Valid values are 0.1 up to 10 seconds.
Note: Fractional seconds are not supported on LANpoint 7, LANpoint 8, MC70, or MC75 terminals. Do not enter a decimal value for TIMEOUT-SUCCESS for these terminals.
If your terminal beeps when displaying a message, the length of the Offline Response Time will affect the length or number of beeps you hear. For example, if your terminal normally transmits three beeps with an error message and you decrease the offline Response Time to 0.1 (1/10 of a second), you will only hear one beep with an error message.
If the terminal is configured to allow Event Relays, the duration of the relay signal (e.g., a light going off or a door opening) may be different than the length of time the success message displays on screen. The duration of the relay signal is configured by the Event Relay form for online transaction, and by the EVENT_RELAY_INTERVAL_OFFLINE and EVENT_RELAY_NUM_OFFLINE Terminal Profile Settings for offline transactions.
The duration of the local offline validation error is always 3 seconds; this value is not configurable. The local offline validation error displays when the OFFLINE_PERSON_AUTHENTICATION Setting Type is enabled in the terminal's profile. See Offline Person Validation for more information.