Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      


Updated on December 15, 2021

Pega Marketing User Guide

To support keyboard-based entry and navigation within the User Experience (UX) for the Smart Claims Engine, screens are implemented with hot key support. This section details how the hot keys are implemented and the limitations in the implementation.

Hot keys implementation

You configure hot keys in the Cell Properties screen for a button or link label. To configure a hot key, enter an ampersand - “&” - before the button caption or link label that you want associated with a hot key; the letter immediately following the ampersand is configured as a hot key:

After you implement this hot key in the UI configuration, the character configured as the hot key is underlined as illustrated below:

Selecting the appropriate hotkey will perform the action associated with the link or button.

Browser differences for hot keys

Hot key access differs by the browser in which you open the application. To enable the hot keys, use the alt or alt+shift depending upon the browser listed below.

Chrome – Alt + Hot key character (For example: Alt + A)

Firefox – Alt + Shift + Hot key character (For example: Alt + Shift + A)

Internet Explorer (IE) – Alt + Hot key character (For example: Alt + A)

Microsoft Edge – Alt + Hot key character (For example: Alt + A)

Limitations with hot keys
  • In IE/Edge browsers, hot keys are not available for links.
  • IE, Edge and Chrome browsers, claim form header hot keys do not work directly from the screen. To use claim form header hot keys, you must initially click on header of the portal to activate it.
  • Hot keys are not available for icons.
  • Duplicate hot keys in the same screen will not work.
  • Hot keys cannot be used for property reference links (for example a link generated by a Provider ID).
  • Field values cannot be configured for hot keys.
  • Hot key is not available for selecting tabs in tab-based screens in tabbed layout.
  • Hot keys are not able to move to another screen directly; you need to use the Next or Submit keys.
  • Hot keys can only be configured for alphabetic letters within the label.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us