Note: Special attention should be given to the items highlighted in yellow as they will require additional planning/steps for your organization pre and/or post-upgrade if the view/tool affected is being used in your installation.

Access rights inherited from a parent library are now highlighted in yellow, making it clear which rights are inherited and therefore not editable. The access rights checkboxes for these are shown in gray to further clarify that they are read-only.

The nuget package DotNetZip in the Client API has been used for compression and decompression of data. The package is no longer maintained and has reported vulnerabilities. Because of this, we have replaced it with the nuget package SharpZipLib.

https://www.nuget.org/packages/DotNetZip

This fixes an error sometimes occurring with attribute types Custom and External reference.

For External reference the error only occurred if you had an attribute with strange data. Then an exception was thrown which meant that no attribute types could be read.

When working on a new config item view in Sandbox mode which has yet to be saved, the properties on the Description tab are now read-only as any values entered there cannot be saved until after the definition is saved. The UI change clarifies this. 

To build a context in the view, enter a definition in the XML editor in the right-side pane. 

To view the virtual context tree on the left-side, click the Refresh button.  

Example:

<ContextTree>

 <Columns>

  <ItemNameColumn caption="Name" width="200"/>

  <ItemStatusColumn caption="Status"/>

  <ItemVersionColumn caption="Version"/>

  <!--TextColumn caption="Next Version">#{NextVersion}</TextColumn-->

 </Columns>

 <Context>

  <AddParts owner="main" sid="PTUR" part="featureListPart" defobj="featureList"/>

  <AddParts owner="featureList" sid="IURQ" part="featurePart" defobj="feature"/>

 </Context>

 <Tree startGroup="main">

  <Case group="main" go="/featureListPart"/>

  <Case group="featureList" go="/featurePart"/>

 </Tree>

</ContextTree>

Once you have finalized your desired context, it can be applied to SystemWeaver views that support the use of <Context>.

Refer to the section SystemWeaver Contexts in the application Help for more details on the usage of contexts. 

In earlier versions, support for Parameter usage in this view was limited to the left side of the view when using Grid. We now introduce: 

• Support for parameter for the whole view (both sides) when using  Grid, StructureTree, or ContextTree. Example: 

The right-side display based on the parameter selection:

• The following new columns have been added, and are mandatory in the column definitions in the right-side configuration beginning with this release. 
  1.    <MappedToIndicatorColumn/>
  2.    <MappedStatusColumn/>
  3.    <MappedToColumn/>

In addition, the NameColumn is mandatory. 

This is a breaking change. The above columns must be added to the right-side configuration.
 Potential problem scenarios: 

• Using a Sävenäs (R47) client with a configuration updated to include the above new columns, users will get an "Unknown column" error. The resolution is to ensure all users receive the new client. 
• Using a Delsjön (R48) client without adding the above new columns to the configuration, on the right side, only the NameColumn will show. The MappedToIndicatorColumn, MappedStatusColumn, MappedToColumn columns will not display.
  To fix, add the columns:

<Columns>

 <MappedToIndicatorColumn/><!--adds "Indicator" column-->

 <ItemNameColumn width="250"/><!--adds "Name" column, which is item name-->

 <MappedStatusColumn/><!--adds "Mapped" column, which is mapping status-->

 <MappedToColumn/><!--adds "To" column, which shows number of mapped-to items-->

• Support for controlling the order of columns on the right side and, for adding extra columns of choice, e.g., <ItemStatusColumn>, <AttributeColumn>, etc.
• An explicit way to define the faulty mapping items using  

The SystemWeaver.ExcelImport has been updated with various improvements with focus on identifying identical data spread out on different rows in the excel document. 

Match On Foreign Id: 

The Match on Foreign Id options provides the capability to identify identical data elements on different rows based on a Foreign Id. The Foreign Id should be found in a column separated from the Item and is set in Item Mappings: 

Allow Empty Cell Value: 

When the allow Empty Cell Value has been checked the SystemWeaver.ExcelImport will ignore empty cells in a columns which are a part of the Item Mappings. Meaning that no Item with a blank named will be imported into the database. 

Improved Match On Name functionality: 

The Match On Name option has been improved so that it now follows the same logic as for the new Match On Foreign Id functionality where Item Mapping columns with cells belonging to the same column (but different rows) and share the same textual value for the name will be treated as the same entity.

The following SystemWeaver extensions are no longer hard-coded to the Extensions ribbon group: 

• SWExtension.ArchitecturalSystemSignals  
• SWExtension.CarConfig 
• SWExtension.ExportDbc  
• SWExtension.FeatureModelling 
• SWExtension.ISOImport 
• SWExtension.InstanceDeployment 
• SWExtension.InterfaceDeployment 
• SWExtension.Jira2 
• SWExtension.PortAdapterMappingView 
• SWExtension.PortReplicator2
• SWExtension.SimulinkImporter 
• SWExtension.SimulinkIntegration 
• SWExtension.Snapshot

This is a breaking change if you would like to have shortcut(s) on a ribbon tab. 

To have shortcuts display on a ribbon, you must now add them to the ribbon group of your choice, and can utilize the available <ItemView> element to do this. Example: 

<RibbonGroup caption="My ribbon group">

 <ItemView name="SWExtension.xxx"/>

 <ItemView name="SWExtension.xxx"/>

 <ItemView name="SWExtension.xxx"/>

</RibbonGroup>

The following changes have been made to the swXMLExport.exe tool for exporting data. 

• Instead of:   ServerPort=1345   one must now use:  -ServerPort=1345
  If using scripts to run this application, this is a breaking change. You must update any scripts. 
• .NET 8 is required on the computer running the application. 
• The 64-bit swExplorerExtensions folder is now delivered together with the application.
• If you log in using a username and password, the app will no longer switch to network authentication if either ServerUserName or ServerPassword is missing from the command line. This means:
  • If you provide a username and password via the command line, the app will attempt to authenticate using those credentials.
  • If either ServerUserName or ServerPassword is missing, the app will not try to use network authentication as a backup method. Instead, authentication will simply fail if the required credentials are incomplete.
  • If both ServerUserName or ServerPassword are missing, you must use network authentication (-UseNetworkAuthentication=true).

Along with making some minor style improvements, the following changes have been made to the XML Import UI: 

• Improved scrolling in the import data and error lists.
• We have improved the error message that appears when an attribute type is missing in the target database during import, making it more informative.

• New item>Import from XML: The Import version numbers option is now set when selecting the configuration, in line with the other options.

The view now includes advanced filtering for all columns, allowing users to filter for specific sets of items. Once filtered, batch operations to release, freeze, or set to work can be performed.

The view now also displays an item Type column. 

The initial loading time of the view has been significantly optimized. 

Example: A structure with over 24,000 server calls

Before:  Intial loading time:  5:13 minutes

Delsjön (R48): Intial loading time:  2:47 minutes           >>> 50% faster!

The following improvements have been made to Parameter usage in configurable Charts. 

All parameter combo boxes now has a fixed width, and the drop-down list adjusts to the length of the longest value. 

In cases with multiple parameters present, these will now wrap to remain visible when resizing the client or view. 

Note: When selecting a parameter for a large data chart, the processing now begins upon selection of the parameter value in the drop-down list. 

Longer labels are now truncated, and one can view the entire label and count by hovering over the slice or the legend entry. 

Given the above change, more room is given to the charts themselves: 

Before:

Delsjön (R48): 

Slice label placement is improved to better avoid overlapping labels: 

Before: 

Delsjön (R48): 

The View tab has been renamed Chart.

Previously, multi-select was supported on the left-side only in the Coverage (mapping item) view. Now, there is support for multi-select on the right-hand side as well. 

Given this update, the view now supports multi-select on both the left and right sides for all three options: ContextTree, StructureTree and Grid.

The dialog now includes horizontal scrollbars for easier viewing of item and part attributes. 

The <HasNextVersion/> filter has been optimized for faster searches server-side.

Example 60 GB database: 

General search (server operation) for all items which have next version.

Previous release: approx. 10 secound 

Delsjön (R48): approx.  2 secound     >>> 80% faster

Note: This improvement requires upgrade of the server. 

There is a new filter available for General Search (server operation) called <HasReferences/>.

The tag <HasReferences> can be used to find objects that have one or more references.

The filter is valid only in the context of items.

Example:

<Filter>

  <HasReferences/>

</Filter>

Result:

All objects that have one or more references.

Note: This improvement requires upgrade of the server. It cannot be executed on the client side, e.g., applied in a Find operation in a structure tree.

Using the right-click context menu, users can hide and add columns to many grids and matrices. However, when there are many columns listed in the menu, it can be time-consuming to select only the columns you are interested in seeing. 

In this release, we introduce a new menu option called Columns. 

• When the number of displayed columns is fifteen (15) or less, the menu will display the columns just like before, as shown above. 
• When the number of displayed columns exceeds fifteen (15), the displayed columns will not be listed at the top of the menu as shown above. Instead, a Columns option will display them in a sub-menu. This way, users can quickly access the Select columns... and Remove column options, making it easier to select the columns that you want to see, and hide the ones you do not. 

The Open in PowerPoint button has been changed to Print to PDF. 

Part type labels and item type SIDs are now easier to read.

Previous release: 

Delsjön (R48): 

This fix hides an message shown in the client status bar that requires no action by the user. 

Note: The clear button clears only the ID value and not the display of item version number. 

To also clear the displayed item version number, use the right-click Remove attribute... option which is now activated as expected. 

• The Cancel button to stop the loading of the view is not currently available.

• Copy (Ctrl+C) of a slice to get items to clipboard is not currently available.
• Parameters display at the top of the Definition and Description tabs.

• The XML Import views do not display a progress bar dialog for larger imports. In its place is the mouse progress wheel.
  
• While we actively work on improving the import performance, we ask kindly that you contact us if you face any problems.