An execution context is an internal structure used during the run time of an AWM model to store data throughout the execution of a modeled action descriptor. It primarily but not exclusively contains property values of selected elements and returned tool output parameters.
Before an action descriptor is executed, AWM creates an execution context and stores all properties of the current selection in it. Tool descriptor input parameters with the attribute Parameter From set to Context are resolved with their values at run time.
If tool descriptors return output parameters, the parameter values are kept in a separate part of the execution context. It is referred to as the parameter memory. These values can be accessed by subsequent tools by setting the parameter attribute Parameter From to Previous Tool.
Execution context can also have a mass processing flag and contain multiple sub-contexts representing, for example, several selected elements. See Mass Processing Overview for more information.
The following rules apply to the search order within the execution context of an AWM action:
Execution contexts are typically deleted as soon as an action has finished executing. The only exceptions are actions which open editors, for example, from tools like Eclipse Open File or MVS Remote Edit. In these cases, the execution context is mapped with the editor session, so that Global Editor Actions and Related Save/Close actions have access to the main edit action’s execution context.