Context Entities 
Voice components inherit resources from their parent application through context entities. You can configure context entities while configuring the advanced settings of a voice application or a voice component or voice entity. The context entities are listed below:
Event handlers
An event handler is a function that responds to an event. The event handlers are of two types:
Pre-defined: You can use existing event handlers provided by SAP NetWeaver Voice. These event handlers are triggered by the system for some automatically generated events.
For example, a common event handler, nomatch, plays Sorry I did not get that, when the caller says something that was not recognized by the speech recognizer.
User defined: You can create your own event handlers and trigger them based on a user action.
VoiceXML properties
These entities enable the setting of a list of standard properties that control the behavior of the VoiceXML gateway and dialog runtime environment. Non-standard properties can also be set. Such properties are passed on as-is to the VoiceXML gateway and can be used to control gateway-specific properties
Jumpwords
These are the words or the DTMF (touch-tone) key sequences for which the program listens and triggers an event whenever the caller speaks or enters a key. This moves the caller to a different part of the dialog in a voice application.
Jumpwords are also known as hot words or link grammar.
You must define an event handler for the jump event either in the current scope or in a parent score.
Resource targets
These entities define the locations from which external resources, such as prompts, grammar files are loaded. It also specifies the locations where you can store the transaction recordings.
The resource targets are set with default values. You can modify them and add additional ones.
Languages
These entities allow you to specify the languages that you want to use in your application