There are several different types of views in the SystemWeaver Explorer that are managed by SystemWeaver Architect users. 

This article briefly describes these view types, and the options and tools available. 


Prerequisites

Built-in Basic Views

Basic views are the item views that are applicable for all item types and are always part of the SystemWeaver Explorer client. They are available on the Items ribbon and consist of 7 ribbon groups containing basic functionality, such as opening items, searching, viewing issues and versions, etc. 

 


The basic views cannot be turned off and are not configurable, with the exception of the Complete status view which can be configured to cover a specific case of releasing a structure. 


Tip: Shortcuts to configured views can be added to the Items ribbon. See Adding Ribbon Groups and Buttons to the Items Tab or 



Built-In Item Views

There is around 100 different built-in Item views available in the swExplorer. There are: 

  • Generic views
  • Views for specific meta models
  • Views for a specific meta model pattern


Some are configurable and some can be turned off. When a view is activated, it is available for all swExplorer users.


Users that have the SW Architect role manage all of the SystemWeaver Item views. A list of all views can be found by navigating to File > Configure the Explorer.



It is possible to add a button for a multi-configuration view to a ribbon tab so users can easily access the view. 


For more information on Item views and Configure the explorer, see Configuring Item 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 use of configurable item (also know as Config item) views. The most common Config items are: 


Config items are tied to a specific item type. This means that they will only activate/become available when a user has selected an item of the specific item type. 


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 can be made available for an item type only within a specific context.


Configuration, using the Script Language, is done directly against the item type in a Definition "Sandbox" so that Architects can move back and forth between the configuration and a preview as they work. 


 

Once the configuration is completed, it is saved as a Config Item in the database by selecting the item type for which it will be applicable. Users can then generate the view to display and/output information about the models created. 



There is also an option to add a button for the view to a ribbon tab so users can easily access the view. 


Config Items are introduced in various script language courses and on the Support Portal, and the application Help can provide more detailed configuration guidance (See Reference Guides further down in this article.). 


See Configuring Config Items for more information on Config Item views.

Extension Views

If none of the built-in views or Config Item views meet the needs of an organization, It's also possible to develop extension views in-house. Systemite also has a number of standard extension views available. Contact support@systemite.se for more information.

Reference Guides

Although we do publish configuration examples on our Support Portal, you'll find the complete Reference Manuals in the application Help to be an important resource during your configuration work. They contain all of the XML elements and field codes that you will need and are full-text searchable. To access the Help, press "F1" or click the ? in the top-right corner of swExplorer.



Special Entities

For special characters in XML, you must utilize character entity reference. See Special entity references in the application Help.

What's Next?

Learn more about Config Items views, built-in Item views, or Items Ribbon Configuration.