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.

SystemWeaver will no longer deliver the ICSharpCode.AvalonEdit.dll (v 6.1.3.50) which up until now has been included in all SystemWeaver Client deliveries. If you have used this dll provided by SystemWeaver in any inhouse built extension views, you will need to include this file yourself in swExplorerExtensions. 

Note that if your extension view uses a version earlier than 6.1.3.50, your extension should be placed in a subdirectory as illustrated below: 

<PortStyles>

  <PortStyle name="Event" borderColor="#d96f4a" legend="Port 
with event" legendLabel="p1"/>

  <PortStyle name="Port" borderThickness="1" 
legendLabel="p2"/>

 </PortStyles>

Item Notes:

<Grid>

  <Options>

    <CellAutoHeight/>

  </Options>

 <Columns>

  <DescriptionColumn width="auto" caption="Item Note" rowObject="itemNote"/>

 </Columns>

 <ForEachNote type="NND">

  <RowObject name="itemNote">

   <Row/>

  </RowObject>

 </ForEachNote>

Issue Notes:

<Grid>

  <Options>

    <CellAutoHeight/>

  </Options>

 <Columns>

  <DescriptionColumn width="auto" caption="Issue Note" rowObject="issueNote"/>

 </Columns>

 <ForEachIssueInObj type="IR">

      <ForEachNote type="NISS">

        <RowObject name="issueNote">

          <Row/>

        </RowObject>

      </ForEachNote>

    </ForEachIssueInObj>

Two new scripting elements have been added as tools for performance analysis. 

There is a new, optional parameter for <Variable> called logTime. It writes the time it took to calculate the parameter value to the log (Ctrl+Shft+L, 'Info').

Example

<Variable name="currentTARA" select="." as="Item" 
logTime="true"/>

A new Prepare tag prepares the local client cache with items starting at a given start item and following the given part types, much like how the structure tree works. This will load the cache with as few calls to the server as possible.

To determine, if using the Prepare tag with your script is beneficial, i.e., provides performance gains, we recommend reviewing log times and/or other means with and without the statement, to verify that you actually get performance gains. If the data is already in the cache, it should not take a long time to execute, at most 10-100ms. 

For details, see the application Help.

Disclaimer: The Prepare statement always forces a call to the server, so it can potentially have a negative effect on performance, similar to when using Axis: back. Due to this, it is advised that <Prepare> not be used unless you are an expert in SystemWeaver Script Language.

Example

<Graph>

 <Prepare start="." partTypes="ARSC;ARPP;ARRP" logCaption=" My test log"/>

  <Node>

   ...

  </Node>

</Graph>

In the case of roundtrip imports, i.e., Items included in the import file have their origin in the receiving database,  there is now an option called Ignore changes to returning items. 

If this option is selected, the comparision between the imported file and existing data in the database will end at the DefObj linking to the Item. All differencies between import file and existing data will be ignored for the Items that have the receiving database's prefix in the xID. The only thing that matters is that the ItemType in the import file must be recognizable.

<JiraConfiguration>

    <Jiras> 

        <Jira OverrideScreenSecurity="False">

            <Name>Head-office</Name>

           <BaseUrl>http://jiraserver:8085</BaseUrl>

            <MainProject>ESP</MainProject>         <CustomField>customfield_10200</CustomField>

            <Relationship Floating="True/False" />

            <Epic>

                <EpicTypeId>10001</EpicTypeId>             <CustomField>customfield_10004</CustomField>

                <EpicName>Epic issue</EpicName>

            </Epic>

        </Jira>

    </Jiras>

    <ItemType>I,SID2,SID3</ItemType>  

    <ServerCode>DEMO</ServerCode>

</JiraConfiguration>

Note that there are no changes to the SWExtension.Jira2.dll extension view file for the swExplorer client. The file can be used with either Jira Server and Jira Cloud type of installation. 

The graph will now use the currently displayed layout as a reference point rather than any saved layout when data is modified using the graph right-click menus, or upon a Refresh that results in new/modified data in the graph. Note that some further manual adjustments may be needed to make room for newly added data, e.g., grandchildren. Alternatively, Relayout can be used. 

In addition, incremental layout will be used when the graph is not manually editable. 

It is now possible to multi-select on the left-hand side and manage mapping.

If one or more of the selected items on the left-hand side are "Released", the Map button will not be available. This means that if any one of them is "Released", the mapping operation will not be possible for any of the selected items.

If multiple items are selected on one side, and there is a version mismatch, the Fix sec. version operation will only be completed if all the selected items, on both the left-hand and right-hand sides, have the same type of issue. Otherwise, the button will be disabled.

This release includes improvements to the scaling of some elements in the swExplorer client on 4K monitors when using 250% display scaling. 

• Open Issues in Overview
• Versions view 
• Sandbox editor
• New issue attribute labels

Further improvements are planned for later releases.

This fixes an issue with the loading of Sharepoint to the embedded Home page in SystemWeaver.

The new client theme includes new icons for the standard views and ribbon options, as well as for the main SystemWeaver executables. 

New View icons:

New Application (exe) icons:

This fixes a problem when swExplorer is used over more that one screen, and the tree vertical separator is moved to the second screen, resulting in losing the separator when moving back to using only one screen.   

This fixes a problem where creating a Test Case when right-clicking in "In Test Case" column threw an error.

In addition, we have fixed a problem with multi-select of items when using either of the Add options in the right-click menu, as well as fixed a problem with deletion of results when navigating between different contexts.

We continue to replace the green progress bar in the views, with a "Loading..." message and notification banner displaying server call count. The change is now implemented in additional views. The "Loading..." message, along with the notification banner, help to ensure users that their client is still working.

This release includes a first version of a new view called the Snapshot view.The view can be used to display a variety of information, such as Attributes, Description, Properties, and Traceability, Attachments, etc. for an item structure (based on a configuration) - all in one place. For more details, see the application Help.

Known limitation: Only jpg and png images are shown in the current version.

The view will be delivered as a standard extension with all named releases.