The first step in configuring a context for your data is to define the context. Each context needs a starting point for filling the context with data. You then define item groups to contain the items of interest. This article describes how to configure this structure.
- Familiar with the SystemWeaver meta model building blocks (e.g., Items, Parts and Attributes)
- Familiar with the SystemWeaver Explorer Interface and common operations
- Familiar with the SystemWeaver Script Language
- Familiar with Using the XML Editor
- An installation of the SystemWeaver Explorer client (swExplorer)
- Knowledge of XML (A good resource is w3schools' XML tutorials)
- Assignment of the SW Architect role in the server
Things to Consider
- Items within a context are seen as context items (TcontextItem) and not "ordinary" items which enables the use of the context functionality. In general, context items are treated as ordinary items. However, when using . or only a variable, they currently are not. A rule of thumb when working with context is to compare using Handle/AncestorHandle and using .Select(Name) in log.
The starting point can be the currently select item (referred to in the context definition as "main") and/or Parameters. The <Context> tag must be used to define a context. It can be defined anywhere in a configuration and is valid for the item for which it is defined. There are two attributes:
Tip: To produce an empty row for readability between each context in your definition, use <Text></Text>.
<Report> <Context name="architectureTop"> <AddParts owner="main" sid="3EFL" part="archToE2EList" defobj="E2EList"/> <AddParts owner="E2EList" sid="3PEN" part="E2EListToE2E" defobj="E2Es"/> </Context> ... </Report>
|Note: It is not possible to use Description Reference (IDR) in a context. The defobj of IDR is Referenceable (R) which can be a Part, Node, or Item, and the defobj in AddPart only supports Item.|
|SystemWeaver version R36 or later is required for the use of <ItemGroup> in <Context>.|