There are several different types of configuration in SystemWeaver that are handled by SystemWeaver Architect users.
- Basic views
- Config item configuration
- View configuration
- Views for specific meta models
- Views for meta model pattern
Basic views are the views that are applicable for all item types and are always part of the SystemWeaver Explorer client. They are available on the Items ribbon.
The basic views cannot be turned off. They are always part of the client. Some of the basic views can be configured to become configured views. For instance, the Complete status view can be configured to cover a specific case of releasing a structure. These custom views can be added to the Items ribbon and would always appear to the right of the basic views.
Config Item Views
SystemWeaver can be configured, adapted and fine-tuned for specific applications and use cases. One way of doing this is through the configurable item views. These item views are:
- XML generation
These are introduced in various script language courses and the Help can provide more detailed configuration guidance.
Saving Config Item Views
A report is configured by accessing the View drop-down and selecting Reports. Below is an example of a configured report.
When a config item is saved, the New Config Item dialog will require you to select an item type for which the new config item will be applicable. In the below example, the new report config item will only be available (active) to users if they have a Test Scope item selected.
Adding Config Item Views to Items Ribbon
Once saved, config item views can be added to the Items ribbon to be easily accessible by users. In the below example, the new report config item is made available in a new Ribbon Group called Config item example.
Config items associated with different item types can be added to the same Ribbon Group. In that situation, the Ribbon Group will become visible to users when they select one of the associated item types. The selected item's associated config item option will appear active while the config item options associated with other item types will appear inactive (grayed out). In the below example, the config item called Config item example 2 (A) is associate with the Adaptive cruise's item type (Test Scope) so it is available as an option. The view option called Config item example - Report (B) is unavailable because it is associated with the item type Test Specification.
Note: Not only can a view be associated with a particular item type; it can also be associated with a particular context for the item type. In other words, the view option may only be available for an item type within a specific context.
Managing Config Item Views
All config item views are stored as items in the database. So, when users wish to open an item of a specific type, they can check the Include Base Item box and find the different config item types in the Select Type dialog. From there, they can select one, click OK and proceed with their search. All items of that config item type will be presented for them.
Given that config item views are items, they can be managed. For example, they:
- Can be versioned
- Have an owner
- Can be imported and exported
Configuration of Explorer Views
Users that have the Architect role can configure all of the SystemWeaver views. A list of all views can be found by navigating to File > Configure the Explorer.
Configure the explorer shows all views in SystemWeaver. The Item views list can be sorted by any column.
The status of the view is shown in the On/off column. It indicates if a view is active or not. Views that are set to 'off' are hidden from all application users.
Note: Some views are activated automatically by a specific item type and those are not indicated in the column.
The Group column shows in which ribbon menu group (if any) the view option will display in the SystemWeaver Explorer client.
The Caption column shows the name and the icon of the item view button as displayed in the ribbon:
The Visibility column indicates the principle of when a view is available/visible. The availability/visibility conditions can be very complex and are for some views configurable. The basic views will be available for any item and they are indicated by 'sid:B(Base Item)':
Configurable views are indicated by 'configurable':
Configurable views for specific meta model patterns can be edited in XML and example XML can be viewed:
Configurable views can be:
Single instance: The view can only be instanced once and usually where the instance often has the name of the view.
Multi instance: The view can be configured as multiple different views where each instance can have different a name.
If a view is activated by a specific item type, the SID of the item triggering the view will be indicated in the Visibility column. In the below example, the Product Builder menu option will appear in the Feature Model menu group on the ribbon and will only display when a user selects an item with sid 10PP:
The Name column gives the internal ID for the view as used for example in a configuring XML script:
A few views are configured using Feature Configuration on the Features tab. The feature configuration includes functionality to install the meta model used for config items. It also holds configurations that configure several views in the same domain. For example, the test views can be configured with the “Test” feature. A number of the test views use the configuration in the “Test” feature. Another example is XML generation. It is a generic core view in the SystemWeaver Explorer client and does not need to be activated. However, since the XML configurations are stored as Config items, these types must be created. This can be done using the Configurable XML generators entry of this tab. In the below screenshot, this has been done which is indicated by the "Metadata installed" message.
Refer to the Help for a more detailed overview. You can also learn more about Explorer configuration in Items Ribbon Configuration.