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.

In the .NET Framework Client API:

Login with option EventSynchronization.Dispatcher now works as intended.

There was an error in the event handling when you logged in with option EventSynchronization.Dispatcher. This has now been fixed.

For extension views, the method: 

IswItemViewContent.SetCurrentItem 

that you implement on the item view content is now called with item == null when the view goes out of scope. Ensure that you check for this and clear the control, removing all references to any SystemWeaver API interfaces. If this is not done, the following message will now display when a user moves away from the view, if the item view content is not cleared properly. This is a breaking change.

Example: 

This does not apply to MultiInstanceItemView. 

When using a SystemWever Grid with <Grid Optimized="True">, the following will now be refreshed when the listed actions/edits are made. 

What is refreshed: 

• All values in a column that has been edited.
• Columns of type ItemAttributeColumn with datatype Computed.
• Columns of type PartAttributeColumn with datatype Computed.
• Columns of type NodeAttributeColumn with datatype Computed.
• Columns of type AttributeColumn with datatype Computed.
• Textcolumn

Upon these actions/edits:

• Item attribute with popup editor.
• Item attribute no popup 
• Part attribute with popup editor.
• Part attribute no popup 
• Node attribute with popup editor.
• Node attribute no popup 
• Attribute with popup editor.
• Attribute no popup 
• Name column

Note: Edits in StringValueColumns will not result in refreshed values.

It is now possible to explicitly define what is to be considered a faulty mapping. This is suitable for cases when the mappings are steered from a parameter rather than from selection in the tree structure.

This is done by the use of a new tag in the configuration: <CompleteRightSide select="/ASID/BSID/CSID"/>

The <CompleteRightSide> provides the full scope of the right side to the view upon loading. So, if the right side has been filtered in some way, the complete scope given by the <CompleteRightSide> will be used when calculating for any Faulty Mappings, thus not listing any correct mappings as Faulty. 

<CoverageMappingItemConfigs>

     <CoverageMappingItemConfig id="12">

         <ViewSettings>

              <Caption>Requirement mapping</Caption>

              <RibbonGroup>Mapping</RibbonGroup>

              <Description>hint shown</Description>

              <Image guiImage="72"/>

         </ViewSettings>

         <Parameters>

              <Parameter name="p1" caption="Baseline">

                  <Values>

                       <ForEach Select="/FUPA/REDC">

                       </AddValue/>

                  </ForEach>

              </Values>

         </Parameter>

     </Parameters>

     <ComepleteRightSide select="/FUPA/REDC/IBRA/3SBH"/>

     <TopItem itemType="BIDM"/>

     .....

These fixes apply to the Coverage matrix view in the SWExtension.HazardIdentification dll. 

• A "Common Language Runtime" error received when right-clicking in a cell to access the context menu has been fixed.
• A fix was made to the quick access option. This option enables SystemWeaver Architects to emphasize a special mapping to be more quickly accessible, using notApplicable and quickAddMapping attributes.

The Autosar Datatype Editor view now has a button for showing/hiding the graph: 

The default behavior is set in the configuration with a new <GraphVisible/> tag.

The SWExtension.SysML extension dll has been renamed to SWExtension.EAImport because the import is primarily developed and tested towards Enterprise Architect XMI format 2.1. 

In addition, this extension view is now a multi-instance view. 

The configuration now requires: 

• <EAImportConfigurations> which should contain all of the <EAExportConfiguration> elements. 
• Each <EAImportConfiguration> must have a unique id and <ViewSettings>. 

This is a breaking change. 

New and updated configuration elements are highlighted below: 

<EAImportConfigurations>

    <EAImportConfiguration id="1">

        <ViewSettings>

            <Caption>EAImport 1</Caption>

            <RibbonGroup>Extensions</RibbonGroup>

            <Description>EAImport extension.</Description>

            <Image guiImage="40"/>

        </ViewSettings>

     ...

    </EAImportConfiguration>

    <EAImportConfiguration id="2">

        <ViewSettings>

            <Caption>EAImport 2</Caption>

            <RibbonGroup>Extensions</RibbonGroup>

            <Description>EAImport extension.</Description>

            <Image guiImage="-139"/>

        </ViewSettings>

     ...

    </EAImportConfiguration> 

</EAImportConfigurations>

Additionally, sequence diagram has received a few new attributes. Below is the list of all attributes for sequence diagram:

<Attributes>

    <XmiType>SA0044</XmiType>

    <MessageSort>PART</MessageSort>

    <MessageKind>PNUM</MessageKind>

     <FragmentType>ARLP</FragmentType>

</Attributes>

The Feature Model Editor extension view (SWExtension.FeatureModelling) has been updated to support an updated Feature Model meta model: 

It is still possible to create, add, and delete Structure, Feature Family, and Feature items from within the view: 

The Variant cardinality attribute refers to the relationship between Features in a Family. * equals an OR relationship whereas 1 equals an XOR relationship.

The Structure cardinality attribute refers to the cardinality of the Family within the specific Structure Item. 

New for the updated Feature Model meta model is the Structure Cardinality attribute for Structure Items:

The new configuration of the view is shown below: 

<FeatureModellingConfiguration>

   <FeatureFamilyScope partTypes="10IVA;10IFP"/>

   <CanAddFamily itemTypes="10ST"/>

   <Version nr="2"/>

   <Attributes>

      <StructureCardinality sid="10SC"/>

      <VariantCardinality sid="10VC"/>

      <Cardinality sid="10CA"/>

   </Attributes>

</FeatureModellingConfiguration>

<FeatureFamilyScope> refers to the scope of the Feature Families and is valid for the calculation of families out of scope. 

<Version> refers to what version of the meta model is being used. 1 is for the previous version and 2 is for the updated meta model pictured above.

The new CMS Project Roles are now available when using the Path Query Language. This is useful in project workflow configuration, e.g., when configuring AssignedTo, Restriction, etc.:

<Restriction field="RequestDueDate" test="CurrentUser.HasRole('PR1.APPR')"/>

A valid value consists of the role's SID (e.g., APPR) prefixed with the Project ID (e.g., PR1). The Project ID can be found on the General > Project page.

Note: Finding a project with given prefix is a server call. It is not recommended for use in config item view definitions, e.g., report, grid, graph, chart, xml. 

The Product Builder view, used in the context of Variability, has been updated, and the new version is configurable.

<ProductBuilderConfigs>

  <ProductBuilderConfig id="1">  

    <ViewSettings> 

      <Caption>Product Builder</Caption> 

      <RibbonGroup>Feature Model</RibbonGroup>

      <Image guiImage="21"/>

    </ViewSettings>

    <TopItemType itemType="10PP"/>

    <BaselineItemType itemType="3PTA"/>

    <FeatureModelPartType partType="10IFM"/>

  </ProductBuilderConfig>

</ProductBuilderConfigs>

The old version of the view has been marked with "(deprecated)", and will be removed from the client in a future release. Therefore, we recommend moving to the new view. 

The new version of this view is based on an updated Feature Model meta model (referred to as Version 2): 

The new isNull returns if the SystemWeaver object (items, nodes, parts, issues, attribute, etc.) exists or not.

Syntax

Return type

• true or false

Valid for object:

• object

Example:

AssignedTo.IsNull

>returns true or false

<Options>

<ManualExecute/>

</Options>

A Copy Database 1.45 button used for copying databases with version 1.45 has been added to the DataPump tab in the swDatabaseManager tool. 

The Test Notification Server GUI theme has been slightly modified. All functionality is the same as before. 

Additions and changes have been made to the files included in the Notification Server installation. Most importantly: The log configuration file, swNotificationServer.props, has been replaced by swNotificationServer.exe.nlog. You will need to replace the old file with the new one, and configure notification server logging using this new file. See https://support.systemweaver.se/en/support/ solutions/articles/31000147274-configuring-the-systemweaver-notification-server.  This is a breaking change. 

A new CommMatrixImporterExporter extension view for the swExplorer client is now available. It supports our updated network model and can be used for both DBC export and import. 

Importer: 

Exporter: 

The view can replace the use of the Systemite.CommMatrixImporterExporter application and the SWExtension.ExportDBC extension view. 

Note: Support for signal groups is not yet available. 

There is now support for adding larger images to the item Description. When a pasted image results in the total size of the Description exceeding the 131 kb size limit, the Move image to file repository  solution will enable you to save the image file to the server's file repository used for attachments. 

A preview of the original image will display in the Description, print previews and printed output. The preview size is small, and easily fits in the maximum size of the Description, which remains unchanged.

Viewing the original

There is a View image option in the client to open the original image for viewing.

Document Print Preview and Print

If the preview image has been resized manually, then it will appear this size in the Document. 

If the preview image has not been resized, it will try to resize it to the width of the page. 

As before, if an image does not fit within a page, you must resize it manually before printing. 

Report Print Preview and Print

The preview image will be displayed and included in the output.

XML Export/Import

There is an option to include the original images (in .png file format) in a data export. When applied, the images are exported in a zip file along with the XML file. To import, the zip file must be located next to the XML file in order to be included in the import. If not, the import will only include the preview images. 

swExport of Documents

For document export to PDF, the preview image is included in the PDF.

swXMLExport

For data export using swXMLExport, there is a new parameter called IncludeBigImages=true/false to define if the full size image files are to be included in the export. Default is true.

Things to consider:

• Server Administrators should ensure there is available storage for the File repository. Expect the size of the repository to increase; monitor the file repository size regularly.
• Supported image file formats are png and bmp.
• The maximum size for an image file to be saved to the file repository is 2 MB.
• The built-in Image editor (Edit image...) cannot be used with images saved to the file repository. In other words, you cannot edit  these images. 

• TcpUdp port config option is now allowed to be empty or non-existant, and both ports are visible by default.
• Standing on InstanceDeploymentList no longer enables every config. Instead, only the config that has the correct item type is enabled.
• Invalid port values in instance deployments are now cleared after sync.
• Sync is now enabled to handle event group version mismatch, instead of just removing current mappings in that case. A new version is now taken.
• A fix for automatically updating the instance event group has been made to handle the case when data is faulty.

When a column header text has been truncated due to column width, one can now view the entire text in the Status bar by hovering over the header. 

A new option enables users to close all tabs to the right of the selected tab. 

The PortAdaptorMapping extension view, used when having both Adaptive and Classic Autosar, has been updated. The key updates are: 

• Indication of mapping. When selecting a Primitive or record data type the already mapped data types will be indicated in a better way on the other side.
• Batch mapping. It is now possible to map a Structure data type towards a record data type. The mapping will be done in part number order
• Improved removal and mapping logic.

There is now an option to include bookmarks in PDF output when printing Documents and Reports. (A bookmark is a type of link with representative text in the Bookmarks panel of your PDF reader.)

Bookmarks are added as a final step in the output generation process. Your PDF with bookmarks is ready when the "Printing to PDF done!" message displays in the Status bar to the far left:

Example PDF with bookmarks opened in Adobe Reader: 

Notes: 

• The existing Document and Report Print and Print preview options work as before. No bookmarks are generated with these two options. 
• You must have Microsoft Print to PDF printer enabled in Windows. 
• To include bookmarks in the PDF, you must use Print PDF with bookmarks. 
• Support for Chinese section titles is limited.

Each Assignee added to a Request for status change will now receive an email notification informing that they have been assigned to review (approve or reject) the request. 

A new <AutoRequest> tag can be used to transition issues automatically to the next Request in the workflow, when the current Request is completed either manually or using auto-completion. 

<AutoRequest> is added to the "source" status, and requires the existance of <Request> in the next status. It has two attributes. 

• The status attribute is required, and defines which status the issue will be set to if the condition is met. The status does not need to be the "target" status; it can be set to any valid status in the workflow. 
• The test attribute is optional, and defines a SystemWeaver Path expression that must evaluate to true. 

In the below example, an issue will auto-transition, once it is completed, from the Request to change status to "In progress",  to the Request to change status to "Test". 

<Workflow initialStatus="New">

 <Status name="New">

  <NextStatuses>

   <NextStatus name="In progress"/>

  </NextStatuses>

 </Status>

 <Status name="In progress">

  <Request>

   <Users select="@DEVE"/>

   <Complete status="In progress" test="ActiveRequest.RequestAcks[AckStatus.ToString 

='Approved'].Count > 0"/>

  <Complete status="Blocked" test="ActiveRequest.RequestAcks[AckStatus.

ToString = 'Rejected'].Count > 0"/>

  </Request>

  <NextStatuses>

   <NextStatus name="Ready for test"/>

  </NextStatuses>

  <AutoRequest status="Ready for test" test="true"/>

 </Status>

 <Status name="Ready for test">

  <Request>

   <Users select="@TEST"/>

  </Request>

  <NextStatuses>

   <NextStatus name="Done"/>

  </NextStatuses>

 </Status>

 <Status name="Blocked">

  <NextStatuses>

   <NextStatus name="In progress"/>

  </NextStatuses>

 </Status>

 <Status name="Done">

 </Status>

</Workflow>

The "transition status" of an issue that has a currently active Request for status change will now only display the current status, i.e., the "source" status, in gray font. The status to which the issue will transition is no longer included in this status, as there may be multiple "target" statuses that are valid.

Note: Email notifications and Notes will still display both the source and expected target status. 

There is now an Open issue option so you can redirect from the My Requests dashboard to the full display of the issue.

By default, assignees reviewing a Request for status change have options to Approve or Reject either with or without including a comment. 

Now, it is possible to restrict these options using Restrictions. 

<Restriction field="Approve" test="false"/>

<Restriction field="Reject" test="false"/>

<Restriction field="ApproveWithComment" test="false"/>

<Restriction field="RejectWithComment" test="false"/>

If test is set to "false", the assignees will not have the option that is given as the field.  

The restrictions are placed in the "source" status, applying to the request to transition to the "target" status. 

The buttons will reflect the available options to the assignees. In this UI example, it is optional to include comments when you approve, but required to include comments when you reject a request: 

<Workflow>

   <Status name="In progress">

      <NextStatuses>

         <NextStatus name="Ready for test"/>

      </NextStatuses>

      <Request>

      </Request>

      <Restrictions>

         <Restriction field="Reject" test="false"/>

      </Restrictions>

   </Status>

   <Status name="Ready for test">

      <NextStatuses>

         <NextStatus name="Done"/>

      </NextStatuses>

      <Request>

      </Request>

      <Restrictions>

         <Restriction field="Approve" test="false"/>

         <Restriction field="Reject" test="false"/>

      </Restrictions>

   </Status>

   <Status name="Done">

      <NextStatuses>

         <NextStatus name="In progress"/>

      </NextStatuses>

      <Request>

      </Request>

   </Status>

</Workflow>

If a reference's owning item is already open on another Page, double-clicking on a reference or using the right-click option Open owning item in a new tab will now redirect to the already open tab. It will no longer open a new tab if it is already open. 

We have also added a Copy option to the right-click menu.

This extension view now follows the project workflow logic, e.g., Preconditions, NextStatus, Restrictions, AssignedTo.  Note: The view must be refreshed to update. 

Tip: Check out the built-in Request for status change feature as an alternative, or compliment, to the ReviewSupport extension views.

When the server fails to find an object, the error message seen in the client and in the server log file will now use the hexadecimal format instead of the decimal format for ids, to make it easier to understand.

Instead of:  Object with id '3602879701897209360' not found.

It should be: Object with id 'x0D00000036028797' not found. 

One example is if an item has been removed from the server, but is still part of a ribbon configuration.

The swExplorer now makes you aware of how many items you currently have cached from the server. This information can help users to understand potential slowness problems.

The counts are displayed on the Status bar at the bottom of the client.  

The middle display for regular hints will now also show the # of items in the currently selected tree and the # of rows in the tree. A higher # of rows simply means that items are being reused in the structure tree. In the below example, there are 1237 items in the tree and 5397 rows. 

The count to the left of the Ping indicator is an estimated sum of the # of items in active Pages. 

Below, the user has activated/viewed 3 pages in the client for a total of 4203 cached items from the server. The client will work to keep these items up-to-date during your session. Closing a viewed tab will decrease this number. 

A new Tree settings option enables a user to select one of the predefined tree settings that is configured for a selected part's item type in a structure tree. This is useful when you want to view the parts under the selected item type which are not displayed as part of the top-item's applied tree setting. 

When you select a tree setting for a part, the top-item's currently active tree setting gets the "(modified)" suffix to indicate that you have made a change to the currently active tree setting for the structure. 

To remove or change any applied part type tree setting, you simply use the existing Select part types dialog or View menu.

If the selected item already displays parts and you apply a predefined tree setting, note that the part types included in the setting are added to the already visible part types; the setting does not replace them.

Note: There is no support for switching between part tree settings.

At any time, to return to the top-item's predefined tree setting, select it again. 

The new Tree settings option is also available in the Dual view. 

Important things to consider:

Making all parts visible in a structure tree, especially in a large model, can affect performance. 

This fixes an issue where double-clicking on an item in the Workflow feature resulted in it opening in the same tab, replacing the existing top item. Instead, it now redirects to the double-clicked item in the current tree structure.