Keymaps #
Default Keymaps #
Each customer has a 'Default physical device keymap' which is applied to all devices.
This default keymap can be used to configure keys which will be available on all of a customer's devices. Configuring a key at customer level provides a common set of keys to be used, this speeds up deployment and also provides the users with a standardized interface between devices - simplifying training.
Keymap Types #
The table below outlines the various different keymaps which can be configured on the system:
| Type | Description |
|---|---|
| Default | Used as the base keymap for all devices for the customer |
| Device | Keymap configured for a specific device. Configured from the 'Devices' section by clicking the 'Keymap' link |
| Group Assigned | A keymap assigned to one or more of the 'User Groups' on the system. Any user with this Primary Group will inherit the keymap |
| User Assigned | A keymap assigned to one or more users on the system |
warning
A User or Group can only be assigned to 1 keymap at a time. If you assign a User/Group to a second keymap, they will automatically be unassigned from any previous keymap.
Keymap Hierarchy & Locked Keys #
When a device requests a keymap, ~.Dimensions.~ will take the applicable keymap types and merge them together to get a final keymap which will be provided to the phone.
The different keymap types are merged in the following order:
By default, if a key is specified in more than 1 keymap, the key in the later keymap will take priority unless it has been 'Locked' in a previous keymap
For example, if key 3 is configured on the customer's default keymap, a devices' keymap, group and user keymap, the key 3 configured on the user keymap will take priority unless one of the previous keymaps has a key 3 which is 'Locked'.
If key 3 was locked on more than 1 keymap, the first keymap on which it was locked would take priority.
For example, if key 3 is locked on the customer's default keymap, it could never be overridden at any other level and will always be visible on every device.
Expansion Modules #
~.Dimensions.~ supports the configuration of keys on any 'Expansion Module' which has been connect to a phone. To program a key on an expansion module, press the 'Add Expansion Module' to add up to 6 additional pages of keys.
info
Expansion modules added at User, Group or Customer level will have 84 keys available to program. This may be more than the number of keys available for a specific expansion module type. When configured on a Device level keymap, the number of keys available should exactly match the number available on the module.
Phone Only Device Keymaps & Hot Desking #
Phone Only devices have keymaps applied in the same order as user assigned devices, with the exception that there will be no user or group assigned keymap.
When hot desking, the keymaps will be reapplied to the target device in the same way they would if it was a device permanently assigned to the user logging in. When the user logs out, the keymap will be returned to its previous state.
warning
When hot desking into a Mitel 53xx phone, keymaps are not dynamically loaded. Due to this reason, Mitel 53xx phones will reboot after login/logout to ensure the keymap is reloaded.