Operating State

Detail Form: Terminals

The Operating State form is used to change the Operating State of a group of terminals that have been assigned a Terminal Off Policy. The Operating State form also shows the Terminal Profiles and individual terminals that are assigned to the Terminal Off Policy.

The Operating State determines when offline data will be transmitted and processed. 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 the data to the application server. The terminal will not send these transactions until its Operating State changes.

You can also use the COMPLETE_OFFLINE_STATE_CONTROLLER service to change the Operating State of a group of terminals.

See Also:

Operating State Field Descriptions

Find an Operating State

Modify an Operating State

Allowed Operating State Changes

Operating State Field Descriptions

Policy Name

Identifies a Terminal Off Policy.

Operating Mode

Operating Mode defined for the Policy Name in the Terminal Off Policy form.

Operating State

Shows the Operating State of all the terminals that have been assigned the specified Terminal Off Policy. The Operating State determines when offline data will be transmitted and processed. See Permanent Offline Data Collection with Scheduled Data Pull for more information.

OFFLINE_NO_PUNCH_TRANSMISSION: In this state, the terminal will collect offline punches, but will not attempt to transmit the offline data to the application server. This setting will allow the terminals to collect the transactions more quickly.

OFFLINE_QUEUED: In this state, the terminal will continue to collect offline transactions, but will send all of the collected offline data to the application server. However, the Offline Data Processor service will not process this data.

OFFLINE_PROCESSING: In this state, the terminal will continue to collect offline transactions, but will not send the offline data to the application server. When the terminals are in this state, the Offline Data Processor service will process the offline data that was sent to the application server when the terminals were in the OFFLINE_QUEUED state.

ONLINE: In this state, if a terminal is able to connect to the application server, it will transmit any locally stored offline data to the server. The Offline Data Processor service will process the offline data that was sent to the application server when the terminals were in the OFFLINE_QUEUED state. ONLINE is the default value when a new Terminal Off Policy is created.

When you modify a policy’s Operating State, the available options will depend on what the policy’s current Operating State is. See Allowed Operating State Changes for more information.

Find an Operating State

1. Click Main Menu > Administration > Terminal > Operating State.

   All the available records will display in the grid.

2. To narrow your search, select a Policy Name and click Find.

   The updated search results will display in the grid.

Modify an Operating State

1. Click Main Menu > Administration > Terminal > Operating State.

2. Find the Policy Name with the Operating State you want to change and click Modify.

3. Select a new Operating State from the drop-down list. The available options will depend on what the policy’s current Operating State is. See Allowed Operating State Changes for more information.

4. Click Save when you are done.

Allowed Operating State Changes

The following Operating State changes are allowed: