IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > What are monitor models? > Expression support
Content assist
When you are creating expressions in any of the form views or the XML source editor, you can press Ctrl+Space for content assist. Make your selection and press Enter to insert it into the expression.
The content assist window is made up of model elements, operators, and functions (both built-in functions and user-defined XML Path Language (XPath) functions). Selecting an item from the tree and pressing Enter places
the XPath 2.0 representation of that item (or reference to that item) in the expression at the cursor position. The content assist window is sensitive
to the expression that you are editing, and, when possible, shows only valid options. For more information about XPath 2.0, see 
http://www.w3.org/TR/xpath20/.
Launching content assist for a blank expression shows all possible expression options for that expression. As you type text with the content assist window open, options not beginning with the typed text are filtered out.
Many of the available functions have more than one signature, differing by the required argument types. The content assist tree displays all signatures for a given function.
If you are not sure which function signature to choose, select one and the help text will describe the details. You are not required to choose a particular signature; you can simply select the parent element to insert the function text in the expression.
Every event part defined in an inbound event is displayed as a distinct node directly inside the inbound event node. The following example shows a Submit.ClaimEXIT event in content assist.
Each of the event parts (such as BaseData and createClaimResponse in the example) is represented as a node under the inbound event itself. The tree does not represent the actual structure of the event at run time.
For example, some of the elements shown in the tree might be optional and therefore might not be included in a given event, even though the event satisfies the structure described by its various XML schema datatypes. The predefinedData node is shown directly beneath the inbound event and shows the attributes of the event that are present regardless of the type.
In addition, if an extension name is provided for the event, a Property Data and an Extended Data section will also be shown. These sections contain the attributes that are described in the event definition contained in the corresponding Common Base Event file.