1-6
Cisco Interactive Experience Client 4600 Series User Guide
Chapter 1 Introduction
Kiosk Navigation
2.
Policy applied to the device overrides devices’ own configuration.
Properties are additive,
therefore if policy doesn’t override a property, the property will stay unchanged.
3.
Multiple policies can be attached to the same device (group).
If policies contain conflicting
settings, the policy that is higher in the stack order takes precedence. Device policies take
precedence over group policies.
4.
IEC
and IEM software versions are best-effort compatible.
A device that has a version that is not
actively supported by the IEM will still be supported although some things may not have full
functionality. A device version which is out of sync is indicated by the red FW flag. Communication
between client and the IEM is defined by the communication protocol and specification that defines
capabilities of each FW build: older communication protocols are supported in the newer IEM
builds, but older specifications that reflect properties of the firmware are often not fully compatible
with the later versions.
5.
Policies can be persistent or transient (applied for short periods of time).
Persistent policies are
long-term or permanent. Persistent policies are applied when the device is booted or rebooted.
Persistent policies are permanent until they are unapplied.
Transient, runtime, or IsAction policies are created by checking the IsAction checkbox when
creating the policy or in the General tab of the policy. Transient policies are marked by a blue circle
with a white arrow and are made available in form of a button under “Custom Actions”. These
policies change the settings on the devices temporarily and will be reset by changing the settings
within the policy, by applying another IsAction policy with settings that will reverse the original
settings, or on the next reboot. IsAction policies can only work for runtime properties, which are
marked by an orange arrow in the policy or profile.
6.
Notifications and alerts work on a subscription basis.
Once notification/alert has been created, it
has to be assigned to a user. Notification/alert can submit to a third party application collecting the
data – the URL has to be provisioned through User profile.
7.
In order to optimize screen behavior, the application has to implement native components.
Native components are available in form of a Browser API (refer to the documentation) and
essentially move resource-intensive or asynchronously used components outside of the browser
process-space.
Kiosk Navigation
If the navigation panel is enabled, customers will interact with the buttons on the navigational panel. If
the display is a touch screen, customers can touch the buttons and virtual keyboard with their fingers.
Otherwise, the customers can use a mouse to choose the buttons and a keyboard to enter keystrokes. The
following buttons are visible to the customer on the navigational panel:
•
Question/Help button – Customer uses this button to access a help page.
•
Go back one page button – Customer uses this arrow to go to a previous page.
•
Stop loading this page button – Customer uses this button to stop the current page from loading.
•
Go to startup URL button – Customer uses this button to go to the startup URL
•
Reload current page button – Customer uses this button to reload the current page.
•
Go forward one page button – Customer uses this arrow to go to the next page.
•
Print currently loaded page button – Customer uses this button to print the current page if the kiosk
is hooked up to a printer.
