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.

The initial loading of the Groups setup dialog has been optimized resulting in significantly faster loading when a high number of user groups exists. 

Example of initial loading time: 

Delsjön (R48):  18.88 seconds

Torp (R49):         4.25 seconds  

We have added new calls to the SystemWeaverClientAPI and SystemWeaverExtensionsAPI to preload the cache. Used in the correct way, this new support can provide improved performance when working in large structures. 

IswBroker.PrepareItems(long[] itemHandles)

This call loads all the specified items into the client cache. This can be used to load many items into the cache with as few server calls as possible.

long[] IswItem.GetDependencies()

Returns all handles of items found in defobj and refobj of all parts of an item. Note that part-handles do not need to be followed, since you can only point to parts on the same item. Nodes are completely ignored in this process. Note that for parts on only 1 item, this is all done automatically by the API. For this to be efficient, you need to call GetDependencies on many items followed by a call to PrepareItems.

In <WithParam>, the select attribute supports the predefined variable $columnObject, which returns the SystemWeaver object (e.g., Item, Part, Node, Issue, or User) associated with the column.

Example

You can dynamically generate grid columns by iterating over a list of Items (e.g., Legal Requirements). Within an ActionBinding, you can now use $columnObject inside <WithParam> to reference the object represented by each column and pass it to the action, e.g., to map each Legal Requirement to a corresponding Company Requirement.

<ActionBinding actionId="mapp" caption="Mapping Requirements">

 <WithParam name="p1_companyReq" objectName="companyReq"/>

 <WithParam name="p2_LegalReq" select="$columnObject"/>

</ActionBinding>

This enhancement enables more flexible and context-aware actions in grid-based UIs.

It is now possible to use Actions within configurable graphs. This enhancement enables any graph to be transformed from a read-only view into an interactive, editable interface.

The underlying technology builds on the same foundation as Actions in configurable grids, and previously created grid Actions can be reused in graphs.

The key difference in graph Actions lies in the use of ActionBindings, which define how an Action receives the necessary input to execute within the graph context.

GraphActionBinding: Supported Parameters

Graph Actions support three types of input parameters via the <WithParam> configuration:

1. Parameter with SystemWeaver Dialog Value

The parameter value is provided through a supported dialog, defined using a Dialog tag. Supported dialogs include:

• DialogSelectItems
• DialogCreateItem
• DialogCreateIssue
• DialogCreateNote
• DialogSelectLibrary
• DialogSelectItemVersion

2. Parameter with Clipboard Value

The parameter value is sourced from objects currently copied to the clipboard. In this case, the WithParam tag only requires the name attribute.

3. Parameter with Path Query Value

The parameter value is the result of executing a path query. Path queries also support the following predefined variables:

• $focused: Refers to the SystemWeaver object associated with the graph element that was right-clicked to initiate the action. Supported element types include: Node, Edge, InPort, OutPort, and InOutPort.
• $selection: Refers to the SystemWeaver object(s) currently selected by the user, excluding the focused object. Multiple elements can be selected, including: Node, Edge, InPort, OutPort, and InOutPort.

Now, if you try to take out a new version of a Config Item from the Definition tab when there already is a newer version, you cannot whereas before a branch was created. 

If branching of a Config Item definition is needed, search for the Config Item using General search and use the Versions view. 

When you select an item in the Context tree, the item is now indicated in the Structure tree to the left. 

We have also added an icon for the view. 

The name of the Context visualizer dialog has changed to Context developer. 

Previously, one could set a value in an Enumeration Single part attribute in the matrix to automatically create a part occurrence. Now, there is support for more attribute types in the matrix: 

• String
• Integer
• Boolean
• Date

Also, when setting a part attribute in the view, the "inclusion" indication for the row item in the matrix will now be immediate rather than requiring a refresh. 

As part of the above improvements, the small part attributes grid previously found at the bottom of the view has been removed. To update part attributes that are not included as columns in the matrix, we suggest using the Attributes view in a secondary item view position, e.g., docked below the matrix or in a separate window. 

Part type configuration enables Architects to put constraints on a part type. A configuration can put a condition on whether a part can be added, created, and/or removed in the GUI. With this release, we introduce support for Path Query for constraints on <AllowRemovePart>. 

The mandatory value attribute determines whether removing a part is permitted. Supported value is a Path Query that evaluates to either true or false. 

Example: 

<PartTypeConfig>

    <AllowAddPart value="true"/>

    <AllowNewPart value="true"/>

    <AllowRemovePart value="if @TC1 = 'Approved' then true else false" disabledTooltip="This part can only be removed if approved."/>

</PartTypeConfig>

There can be cases where a user imports some data that does not have any relation to each other. In this case, the imported structure is not automatically opened in a new tab upon completion of the import. 

A new dialog will now display in these cases to inform that the import is completed. 

This new dialog does not apply to imports of data that has relations to each other. As before, the imported structure is automatically opened

Additional dependency files have been added to the Client installation:

• DevExpress.Xpf.Themes.SystemWeaverOffice2019Colorful.v24.1.dll
• Systemite.Common.dll
• Systemite.TreeView.dll
• Systemite.Windows.dll
• SystemWeaver.Explorer.Common.dll
• SystemWeaver.Explorer.TreeView.dll
• SystemWeaver.Explorer.UI.dll
• SystemWeaver.Logic.TagWriters.dll
• SystemWeaver.Logic.XmlExportImport.dll
• SystemWeaver.Vanilla.Dialogs.dll

The configurable Action options in Configurable Graphs now display at the top of the right-click context menu above the two Copy options. 

It is now possible to get warned before you Close other tabs or Close tabs to the right. 

The default is to provide the warning. This can be turned off by checking Don't tell me this again in the confirm dialog or by navigating to File>Options and deselecting the option: 

A new Reassign option has been added for Assignees to Request for status change in the Issue editor. The option is available to an Assignee who wants to remove themself and reassign the request to someone else who is not already assigned to the request.

A log entry for the reassignment is added to the Changelog:

The initial loading time of the view has been optimized further. Examples: 

Structure with over 24,000 server calls

Before (R47):    5:13 min

Delsjön (R48):  2:47 min      

Torp (R49):       2.08 min       

Structure with 100,000+ items: 

Delsjön (R48):  23.23 min

Torp (R49):       13.05 min 

The Computed attribute type can be used to display the result of a calculation of multiple attributes, e.g., Inherited ASIL. It can be thought of as a "stored procedure". The calculation is defined using Path Query expressions.

We have reduced the execution time of Computed attributes by an average of 4x. It benefits all uses of the computed attribute in views, such as StructureTree, Overview, Grid, and others.

Example:

We have significantly improved the initial loading time of the Configurable graph view specifically when ManualLayout is enabled in the configuration. This is most apparent when the graph has a lot edge (bus) routing.

Example of optimized initial loading time with ManualLayout in use: 

Delsjön (R48):  9.35 minutes

Torp (R49):       8.70 seconds  

It is now possible to multi-select all or a sub-set of faulty mappings to remove them using a new Remove mapping(s) option. This change applies to both the Coverage (mapping item) and Coverage (item-item) views.

The Float attribute editor now includes an expression check for users for added support.

The graph component used in the following views has been upgraded from 3.4 to the lastest version 3.6: 

• Configurable Graphs (built-in view)
• SWExtension.MetaModelGraphs (extension view)
• SWExtension.ComponentGraph (extension view)

As a result, some auto-generated layouts may appear different, with often improved node positioning and less edge crossings.  

Tip: To ensure you see the updated layouts for configurable Graphs that you typically load (cached to your computer), navigate to C:\Users\YOURUSER\AppData\Local\Systemite\SystemWeaver\3.0\0, and delete any cached graph files found in this folder. The files are zip files similar to the below example. This will force the system to regenerate the graphs. 

The newly introduced Columns submenu on the right-click context header menu is now available in the following views: 

• All references
• Complete status
• Context tree
• References
• Status
• RM+ Light
• XML Export/Import

When the number of displayed columns is fifteen (15) or less, the menu will display the columns just like before. 

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 Hazard Identification views (Coverage matrix and Safety analysis) have been optimized for faster initial loading times and item creation/edits. The initial loading time improvement is more significant the larger the data. 

Examples from Damage Scenarios (Coverage matrix) view:

Initial view load time: 

Delsjön (R48):      7.02 sec

Torp (R49):             0.46 sec   

Create/edit items in top grid in view: 

Delsjön (R48):     2.40 sec

Torp (R49):           1.70 sec   

When working with item creation and edits in the Mappings grid or in the Details tree, your focus will now be maintained after an operation is saved. 

The view refreshes faster now when you make use of the Only show open issues option. 

The progress bar has been replaced by the mouse progress wheel.

The initial loading of the Select library dialog found throughout the client and the Manage libraries page has been optimized resulting in significantly faster loading when a large number of Libraries and Groups exist. 

Example of initial loading time with 1000s of libraries: 

Delsjön (R48):  2 minutes

Torp (R49):         3 seconds  

It is also now possible to vertically scroll through the Item type list when applicable. 

Hovering over a column header will display the entire header text in a hovertip making it easier to view. Previously, the complete header text was displayed in the Status bar at the bottom of the client. 

Note to Architects: Column order may appear different than in earlier versions when using  <ColumnLists path="/ASID"/>. If this is the case, and you would like to have the same order as before, add OrderBy(Handle) to the path: <ColumnLists path="/ASID.OrderBy(Handle)"/>.

When using multi-select in a column to Include/Remove/Sync values, only the selected cell is now highlighted—rather than the entire row—making it clearer which cells are selected.

• Tree options temporarily replaces the View option in the right-click context menu in the matrix tree.
• Indication in Structure tree is not working in some cases when selecting a cell.
• When doing a Find in the view and Select search result, the results are selected, but are not shown in blue.