Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Choosing a flow action with a shortcut key

Suggest edit Updated on September 14, 2020
Note: This article is not compatible with Pega Platform™ 8.1 and later.

Summary

To speed user input, developers can define a keyboard shortcut for flow actions. This is an optional capability available in all applications, and is recommended for accessible applications not using the Take Action drop down menu.

 

Suggested Approach

To create a shortcut key for a flow action:

    1. Create a field value rule by selecting the Application menu and choosing New > Rule > Property > Field Value. The new rule pop-up window displays.

zzz

    1. Apply the new field value to @baseclass.
    2. Enter pyCaption as the field name and the name of the flow action that you are creating a shortcut key for as the field value. Click Create.

zzz

  1. On the Localized labeltab, enter the name of the flow action in the localized label field, making sure to add an ampersand (&) somewhere in the name and that it matches the name of the flow action exactly.

    Note: Although the & can be located anywhere in the name, the letter following the ampersand '&' becomes the shortcut key for the button.

  2. Click OK and Save the rule.

Using the shortcut key

To use a custom-defined shortcut key for a flow action on the harness, hold down the ALT key while pressing the appropriate key.

For example: if you defined a shortcut key for the Resolve As Duplicate flow action with the & located before the D in Duplicate, you would press ALT+D to enable the Resolve as Duplicate flow action.


 

Related Topics

About the Accessibility Framework

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us