The SystemWeaver API has been upgraded from version 1.52.0 to version 1.52.1. Although this minor upgrade does not technically require that all users receive and utilize the R37 version of the client applications (swExplorer, swAdmin2, swArchitect), we do recommend it and it would be required to access all of the client enhancements and bug fixes listed in the release notes. 

To obtain any newly introduced item types, part types, or attribute types, API applications developed in-house will need to be recompiled with the newer version of the SystemWeaverClientAPI.dll. The Rest API would need to be upgraded to obtain them as well.

Note that clients of version 1.52.1 cannot log in to 1.52.0 versions of the server.

Attribute editors

In interface IswDialogs, there are new methods in the extensions API to launch the standard swExplorer dialogs for editing of attribute values. The unbound versions are for when you want to edit the value before the item/issue has been created. Not all attribute-types have an unbound version so there is a method to check if there is. 

ExecutePathAsString

The Mapping item name can now be set with the use of the SystemWeaver Path Language. Paths can be initiated by using standard path language syntax #{?} with starting points from the row item, column item or the currently selected item. Each item can be used as a starting point by using the $CurrentItem, $Row or $Column variable tags.

Executes path within variables  and returns a string.

Unique ID

There is now support for the custom attribute Unique Id dialog in the Extension API. It supports the creation of unique ID attribute values suitable for requirement IDs, etc., similar to Identity attributes. It builds on the use of two custom attributes - one that defines the context (AUIC) and one that defines the ID (AUID).

There is a new attribute data type called Signature for digital signing. Data dimension Single is supported.

You sign by pressing  and entering your Windows credentials.

Only items with a status of "CS released" can be signed.

Signature displayed in attribute preview: 

The Username and Display name is saved as it exists at the time of signature. It is not affected by any future changes to these name properties. 

Once a Signature attribute is added to an item and is used to sign, the attribute can never be removed from the item. A signed item can never be deleted. Since you cannot delete the item, and it has a status of "CS Released", this item and any referenced items, including previous versions can never be deleted.

You can also sign issues. The meaning of signing an issue is determined by the workflow definition.

Our current SystemWeaver.AutosarExport standalone application for AUTOSAR exports is now available as an extension view that support exports of Classic and Adaptive AUTOSAR.

Also, the AUTOSAR Exporter now supports export of System Extract as well as export of a System Manifest

and Service Interfaces on the Adaptive AUTOSAR side.

We now offer two new AUTOSAR deployment extension views - Instance Deployment and Interface Deployment. The views support the Adaptive AUTOSAR workflow by aiding in generation of deployments.

The Interface Deployment extension supports creation of Interface Deployments including Method, Event,

and Field ID generation from a configured ID interval. The view also manages Event Groups.

The first version of an AUTOSAR Topology Editor extension view is now available. 

The AUTOSAR Topology Editor is a dedicated user interface developed to support the creation and maintenace of the topology.

The view supports working with a topology from either a Node-Channel or a Channel-Node perspective:

Node - Channel

Channel - Node

If needed, one can now include the SID of the parent item type which will result in ignoring the description for all sub-types. It is also possible to ignore the description of all cloned item types by adding:

There is now support for both single and list multiplicities on the right-hand (secondary) side of the view whereas previously there was support for only list. A new, optional attribute called distinctMappingPerPair on <Mappings> determines if each pair should have a distinct mapping.  A "true" value enforces 1:1 relation and will always create a new mapping item for the selected pairs. A "false" value enforces replacement for the existing left mapping item. The default is "false".

The NotApplicableMappingItem has been removed from the HazardIdentification extension's Coverage Matrix view. The functionality has been replaced with the optional <ConstraintItems> tag in the <MappingItem> configuration. This gives the possibility to combine different mapping elements when necessary. In addition, the <MappingItem> tag has been extended with two optional settings  <MappingItem itemType ="SID" notApplicable="true/false" quickAddMapping="true/false">. The notApplicable attribute will mark the corresponding cell in the coverage matrix gray. The quickAddMapping attribute allows for a single-click mapping to be created.

The <MappingItem> now has support for multiple instances meaning that several MappingItems can be a part of each CoverageMatrix instance. 

The CoverageMatrix view now supports the following attribute types:

Identity

User

Custom Identity 

Computed 

Custom Computed 

The Custom Identity attribute type requires context input. The selected item is automatically used as input but it is possible to add information from a parameter by using the 

The Mapping item name can now be set with the use of the SystemWeaver Path Language. Paths can be initiated by using standard path language syntax #{?} with starting points from the row item, column item or the currently selected item. Each item can be used as a starting point by using the $CurrentItem, $Row or $Column variable tags.

<DefaultMappingName>$column.... +'of' + $row...+ $pSelected/..+ $mainItem/....</DefaultMappingName> 

Example: 

The GUI has been updated with a new layout to better utilize the view. The faulty mappings are now found at the bottom of the view and the pane is hidden when there are no faulty mappings. It can be opened by clicking on the ..... splitter.

The <Grid> tag  now includes an optional optimized attribute which defines whether or not each cell value, e.g., in TextColumn and ItemAttributeColumn, will be recalculated as needed or not. We have seen speed improvements of a factor 10 using this option and, therefore, recommend its use if a grid is slow. 

Valid values are "true" or "false". Default value is "false".

true: Each value will only be calculated once when you are working in the grid. This is suitable if the grid is for obtaining a "snapshot" that will be exported to Excel, etc. Grid generation and Excel export times are optimized. To refresh/recalculate the grid cell values at any time during your viewing, hit F5.

false: Each value is recalculated as needed when you are working/editing in the grid. This is suitable if you always want the values to be updated. Grid generation and export times will include obtaining all relevant up-to-date values from the database.

When using a configured graph in an <ItemView> in a MultiButton, a new, optional locked attribute can be used to specify if the graph will be locked or not upon loading. Valid values are "true" or "false". The default value is "false". 

There are now additional, optional attributes for <SecondaryItemView> which can also be used when this view is included in a MultiButton. The new attributes are configItem, locked and orientation. 

The configItem attribute works similar to configItem in <ItemView>.

The locked attribute specifies if the secondary item view will be locked or not. The default value is "false".  

The orientation attribute specifies the position of the secondary item view. Possible values are "right", "top", or "bottom". The default value is "right".  

There is a new attribute for ItemVersionChanges for a change log called includeNoChangeMessage which provides the option of including a message "No changes, additions or deletions have been made to attributes, parts, and description content." in the ChangeLog when no changes have been made between versions of items.

If the attribute is set to "true", then the message will display in that case. The default value is "false" meaning that you must have this attribute included and set to "true" if you want to have the message included.

There are now two options for setting a pre-selected value for a Parameter: the existing hintContextPath and a new, optional attribute called defaultValue. They can be used in the same view configuration for different parameters, but cannot be combined/used together for the same parameter.

The supported data types for defaultValue are: 

• Boolean
• String
• Date
• Integer
• Int64
• User
• Object

The default value must be a valid parameter value, otherwise the default value will be empty.

An <AllowMultiInstance> constraint tag is now available for part type configuration to constrain the addition of parts that already exist under the selected owner item.

The constraint is expressed by an XML element:

Valid attribute values are 'true' (default) or 'false'.

With AllowMultiInstance set to "false", users cannot add multiple instances (occurrences) of the part under the same owner item. 

The optional attribute allowDifferentVersions determines whether or not users can add other versions of an existing part. This option can only be used when AllowMultiInstance is set to 'false'. 

With allowDifferentVersions="false": 

The Path Query Language now supports the following for float: 

Operators

+ operator

• integer + float
• float + float
• float + integer

- operator

• integer - float
• float - float
• float - integer

* operator

• integer * float
• float * float
• float * integer

The result of these will be float.

Evaluation

Float attributes are now evaluated as floats all the way. Previously, @ATR1 = "4.3"  would return "true".  This is no longer the case. Instead, @ATR1 = 4.3 will return "true". 

Methods

In addition, the following methods have been added: 

ToFloat

• Transforms and type-casts a float (or integer) value string into an float value.

Example: 

/part::5ACV.Select(@5CVA.ToFloat).Sum

Results in the sum of the enum-values of part-attributes of (string) attribute-type Customer Value [5CVA].

Round

• Returns the rounded integer part of a float argument.

Example: 

probability:=0.99999999; probability.Round

Given a delimiter, it is now possible in the Path Query Language to split a string into a list of strings separated by ','.

New application icons

The following applications have received new icons: 

Test server status and port info

In addition, the swTestServer application icon will now indicated if it is running or not: 

 Indicates the test server is stopped

 Indicates the test server is running

Also, the server port number is now displayed in the swTestServer application caption, which also displays when hovering over the executable on the Windows taskbar. 

Note: When swapping out older versions of these executables, you may need to clear your Window icon cache to view the new icon immediately. 

The swExplorer now provides a latency indicator. It shows the approximate time it takes to go from the client application to the SystemWeaver server application and back. It can help diagnose potential internet connectivity issues, and is not necessarily indicative of a problem.

Typical Approximate Latency Times

In milliseconds (ms)

Below are typical latency times under normal load conditions.

• Server and client on same machine:  2
• Server and client on different machines in same geographical location: 8-15

The mirror server log file now provides more  information about the cache update upon start-up. Previously, the log indicated:

It now provides more information about its progress in updating the cache file by including an entry for every 10000 writes that are read to the cache file. 

The main server log file now gives an indication of approximately how many more transactions are left to read to the cache file. 

Most installations do not have over 10,000 writes in one day. In that case, you would only see one of these log entries. If you see many, it is an indication that many write operations occurred while the mirror was stopped, or are still occurring. Information about the volume of write operations can be very helpful to administrators for planning future downtimes.

We do not recommend the use of SyncJournalEntries=True by default, since it can potentially hide network/disk problems that you otherwise would want to be aware of. Please consult Systemite if you are considering using this option.

Warning: If this option is set to "True" and you want to revert to a backup database copy as a means of "wiping out" unwanted database transactions,  you will want to run Remove extra entries on the journal file before you start the server against the backup database.

When using journaling for the mirror server solution, it is now possible to set a minimum number of most recent entries to be saved in the swjournal file which will limit the size of the file. The configuration is done in the swServer.ini. 

MinJournalEntries=x

If total > MinJournalEntries * 1.1, then remove MinJournalEntries * .1

Example: If you specify 10000, the number of entries will grow to 10000, then be somewhere between 10000 and 11000. In other words, without the limitation, the journal will store the total number of journal entries, e.g., 500000, whereas with the journal limitation, the server will remove old entries and maintain only the most recent 10000-11000 entries per the configuration. 

The Journal file info tool in the swDatabaseManager will show the "First transaction id" and "Last transaction ID".

Organizations that want to limit the journal size will need to decide how many transactions to keep. Monitoring the .swjournal and using the swDatabaseManager tool to see how many transactions it contains and, e.g., how many there are on average per day, can help in making this decision.

The built-in configurable Graph view now offers an option to enable users to not only visualize the data in the configured graph, but also graphically design the data directly in the graph. And because it is a generic view, it can be used with all models and use cases in SystemWeaver.

The Edit option is enabled as part of a graph configuration through the use of new tags for: 

• Adding parts 
• Removing parts 
• Mapping connection types

We have also made available a first version of context menu configuration for adding and removing parts to provide users with a context menu style similar to the one found in the structure tree. 

Editability can also be turned off in the configuration of the graph.

When enabled, users can perform the following operations directly in the graph in accordance with the meta model, in the same way as they can in the structure tree: 

• Create new parts and their resulting graph nodes
• Adding parts and their resulting graph nodes
• Remove existing parts and their graph nodes (single or list)
• Update nodes (name and attribute)
• Connect nodes

For connecting nodes, the available connection types are: 

• Explicit connections
• Implicit connections
• Connect through mapping item
• Connect through anchor item

Right-click context menu options and shortcut options for editing in the Graph view are similar to those in the structure tree, e.g., New, Add, Copy (Ctrl+C), Paste as (Ctrl+V) with the addition of Connect Ports. Not only can the Copy and Paste options be used within the graph, you can also copy from a grid or the structure tree and paste in the graph. To create a connection, select the objects, right-click and select the appropriate Connect option. The label for this option is configurable.

It is also possible to configure the Remove part option for the menu using a string or path query.

For released items, New, Add, Paste, and Connect options will be grayed out.

Secondary item view: New layout options: Aside from the default right position, it is now possible to position the Secondary item view at the top or bottom of the view area. With editing enabled in the graph, you can, for example, copy and paste items between a grid and a graph.

More detailed information about the new Graph tags and how to work in edit mode can be found in the application Help. 

Example configurations are available on the Support portal.

The following enhancements have been made to the configurable Graph view.

Support for using Path Query to select style for node and edge 

It is now possible to use a path query to select a style. 

Node

<Node style="#{? path query}"/>  

Edge

<Edge from="." to="." style="#{? path query}"/>

Selection of style by providing the name of the edge or node style as a string is still possible.

Support for using Find (Ctrl+F) in a graph to locate nodes and ports

Hits are highlighted with a green frame.

Neighborhood for a selected port

In addition to viewing the neighborhood for a selected node, it's now possible to show the Neighborhood for a selected port.

Lock the Graph in Primary View

The view can now be locked in the primary view position enabling you to keep the selected item in focus in the graph as you navigate through the structure tree. With the view locked, when you make selections in the tree, you will see them highlighted in the view. 

And combined with the use of the Secondary item view, you can make edits to, e.g., attributes, description, etc., to an individual item selected in the graph while keeping the graph in view. Working this way, the structure tree view can basically be minimized altogether since most work tasks can be completed directly in the graph. 

Refresh button

The existing Refresh option using the F5 key is now also available as a button on the view's toolbar

Port Selections Highlighted in Tree

Selected ports in the view are now highlighted in the structure tree.

Legend Option

It is now possible to configure a legend for a graph using a new <Legend> tag along with legendLabel attributes in <NodeStyle> and <EdgeStyle> tags. The legend can be viewed in the same way as Neighborhood. 

More detailed information about Legend configuration can be found in the application Help, and an example configuration is available on the Support Portal.

Improved Message for Tree and Balloon Layout Problems

"tree" or "balloon" layout requires that the graph data is topologically a true tree structure, i.e. no edge loops are allowed. When using layout="tree" or "ballon", and the data is not a tree, a "Exception: Graph is not a tree" message will display in the view. 

The programmable mouse side buttons can now be used to navigate back and forward between items in a structure tree as well as views, and issues, in the same manner as when using the Items ribbon Navigation options. 

There is now an optional Error Info column that will provide information if a part type has been changed in such a way that it is no longer supported by the meta model. The column can be added by right-clicking on the head row and selecting it.

The part type multiplicity has been changed to "Single" and there are multiple occurrences of the part type, (which is no longer supported): 

The part type is no longer supported by the meta model. i.e., part type has been changed/removed: 

The part type is deprecated: 

There are now additional layout options for the Secondary item view. Aside from the default right position, and existing Undock options, you can now select to position the Secondary item view to the top or bottom of the view area. The options can be found when expanding the Close button: 

In the below example, a grid in the secondary view is located at the top of the view area while the primary view contains a graph.

For Architects, it is also possible to configure the layout via an orientation attribute for the position of the Secondary item view in a MultiButton on the ribbon (See Item Ribbon: New multi-button configuration options above).

The loading of simple parts in the structure tree has been optimized. This enhancement entailed the minor upgrade to the API from version 1.52.0 to 1.52.1.

In doing this optimization, we also changed the initial view setting for item structures. Previously, a Default structure tree setting of all structural parts along with a fixed list of legacy part types was loaded for new item types or for item types where items of that type are yet to be created. This has now been removed. When opening an item of a new or unused item type for the first time, users will not see any part types by default. Architects will need to set up the needed Default view.