By default, AWM creates a single execution context per action. This context is used to store all property values and file descriptor instances from selected elements and returned tool output parameters so that the values are available for every subsequent tool in the tool chain of the action.
With the complex attribute Action_Has_Tool_Has_Named_Context it is possible to create a new named execution context within an action descriptor. The new context contains at least the tool’s output parameters and can either be created or can be copied from the previous context. Subsequent tools can be explicitly executed using this context by referencing its name in the Context attribute of the Action has Tool relationship. This can be used to manage multiple logical contexts dynamically created within a single action.
Additionally, it is possible to set the Mass Processing attribute of the newly created context to true. This means that it is possible to define mass processing tools within a single processing action or vice versa. See Mass Processing Overview for more information. This enables a flexible and dynamic handling of execution contexts within an AWM action.
Attribute | Type | Description |
---|---|---|
Context Name * | String | Context name to be used as an identifier; this has to be unique within the related action descriptor. |
Copy From | Selection | Can be specified to copy an existing context, including all of its property values and stored output parameters.
Valid values are:
The default value is Current Context. |
Mass Processing | Boolean | Specifies whether a mass processing context should be created. When true, the tool will also be executed in mass processing
mode.
The default value is false. |
This example displays an action which creates a story and adhering tasks in an agile project planning system. There are two different tools used to create an implementation and a test task (TOOL_CreateImplementationTask and TOOL_CreateTestTask):
There is another general tool that applies a template to a task (TOOL_ApplyTaskTemplate). This tool is called twice, once with the context created by the implementation task and once with the context created by the test task.