Keyboard Event

Description

Monitors for specific keystrokes, such as a hot-key or auto-key combination to be typed on the keyboard and evaluates as TRUE when the event occurs.

Practical Usage

Useful for creating hot-key "shortcuts" for repetitive multi-step processes.

Related Topics  

Parameters

General

Property

Type

Description

Trigger on the following hot key

String

If selected, specifies the hot key combination to be monitored. Selecting this parameter enables the following secondary parameter.

Allow hot key to pass through to application

Yes/No

If enabled, specifies that the hot-key combination will continue to be active in an open application. If disabled, the hot key combination will have no effect on any application other than AutoMate (disabled by default).

Trigger on the following auto keys

Yes/No

If selected, specifies that the trigger will monitor for the specified word or phrase to be typed. Selecting this parameter enables the following secondary parameters.

Erase text before triggering task

Yes/No

If enabled, the monitored text will erase itself from any document or application before triggering the task. However, if you want the typed text to appear in the open application or document, disable this parameter.

Only when the following process is active

Yes/No

If selected, the trigger will activate only when the selected process is active on the system during the time that a user enters the specified hot key, word or phrase (disabled by default). Selecting this parameter enables the following secondary parameter.

And the application is in the foreground

Yes/No

If selected, the trigger will activate only when the selected process is active and the application window corresponding to that process is currently in the foreground during the time that a user enters the specified hot key, word or phrase.

Additional Notes

AMTrigger

When the Key event is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the SQL Query and E-Mail actions. The fields that AMTrigger generates can be used to determine properties of the object that caused the workflow to launch, such as the type of trigger, when the trigger was activated and what system event or condition took place to activate the trigger. Along with a collection of global AMTrigger fields that are created and populated by every instance of AMTrigger, a unique set of AMTrigger fields exclusive to each AutoMate trigger are created as well.

To view AMTrigger values exclusive to the Key event, see AMTrigger - Key.

AMCondition

When the Key event is used in the middle of a workflow as wait or conditional object, it automatically creates an AMCondition dataset. Similar to AMTrigger, the fields that AMCondition generates can be used to determine properties of the object that caused the condition to activate. Along with a collection of global AMCondition fields that are created and populated by every instance of AMCondition, a unique set of AMCondition fields exclusive to each AutoMate condition are created as well.

To view AMCondition values exclusive to the Key event, see AMCondition - Key.

NOTE: A full list of AMTrigger and AMCondition fields exclusive to each trigger/condition can be viewed from Expression Builder by expanding the Objects folder and selecting the desired object from either the Triggers or Conditions folder.