This document describes new features, improvements and fixes included in this release of SystemWeaver.

There are no changes to System Requirements: 

 

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. 

 

Administrators

Name
Description
Type
User Group
Issue ID
API Upgrade from 1.49 to 1.50
The SystemWeaver API has been upgraded from version 1.49 to version 1.50. This will require that all users receive and utilize the R28 version of the client applications (swExplorer, swAdmin2, swArchitect). In addition, this requires that any API applications developed in-house will need to be recompiled with the newer version SystemWeaverClientAPI.dll.
Improvement
All
12696


API Users

Name
Description
Type
User Group
Issue ID
API Upgrade from 1.49 to 1.50
The SystemWeaver API has been upgraded from version 1.49 to version 1.50. This will require that all users receive and utilize the R28 version of the client applications (swExplorer, swAdmin2, swArchitect). In addition, this requires that any API applications developed in-house will need to be recompiled with the newer version SystemWeaverClientAPI.dll.
Improvement
API Users
12696
SystemWeaverClientAPI: Get Description as Docx
It is now possible to convert Description texts to Docx-format using the SystemWeaverClientAPI:

Improvement
API Users
12514, 12548
SystemWeaverClientAPI: Nlog logging framework
The SystemWeaverClientAPI will now use the nlog logging framework instead of log4net.
Improvement
API Users
12629


Architects

Name
Description
Type
User Group
Issue ID
Configurable XML: Fix for Indent in options error
This fixes an error where using the <Indent> option resulted in the XML not generating.
Fix
Architects
12093
swArchitect: Fix for statistics report column width issue
This fixes a recently introduced issue with column widths in the Statistics and System Variables reports.
Fix
Architects
12617
Clone view: Only active on specified item type(s)
When configured and set to "Active" in Configure the explorer, the Clone item view is now only available for configured item types. It is no longer available, by default, for all item types, but rather the clone settings must be predefined in a configuration.

Given the below configuration example, the view will only be available to users when they select an item of type with a SID equal to "SSRP".

Example:
<Configs>
  <Config id="Create document from template">
    <ViewSettings>
      <Caption>Letters</Caption>
      <RibbonGroup>Documents</RibbonGroup>
      <Description>Create a new document from a template</Description>
    </ViewSettings>
    <TopItemType>SSRP</TopItemType>
    <CloneParts>
      <Part sid="IRHE" action="include"/>
      <Part sid="IRFO" action="include"/>
      <Part sid="IRTF" action="include"/>
      <Part sid="IRTH" action="include"/>
      <Part sid="IRTP" action="include"/>
      <Part sid="IREX" action="include"/>
      <Part sid="IRRS" action="clone"/>
      <Part sid="ISSE" action="clone"/>
    </CloneParts>
    <Transformations/>
  </Config>
</Configs>


For changes to configurations to take affect, users must log out and back in to swExplorer.
Improvement
Architects
12551
Configurable XML: Better conversion of formatted text to XHTML
The functionality to generate XHTML from descriptions has been significantly improved.  

Note that this requires that Configurable XML definitions are updated to use the tag <Extension name="xhtmlDescription"/> instead of the <Description format="reqif"/>.

Below is a minimal working example utilizing the new XHTML functionality:
<XDocument name="Doc1">
  <XElement name="Info">
    <Extension name="xhtmlDescription"/>
  </XElement>
</XDocument>


Validation of generated ReqIF files is still recommended since some descriptions may contain hyperlinks with faulty references that cannot be handled other than through changing the source description.

Improvements:
  • The result will always generate valid XML.
  • The formatting in the resulting XHTML is converted in a much better way.

Known limitations:
  • Paragraph background color that is set for an empty row is not preserved after conversion.
Before conversion:After conversion:
  • Overlined formatting is not preserved.
  • Max allowed width for tables is 31680 twips. if exceeding it will be set to max.
  • Description References are not preserved. The formatting stays the same, but they are no longer clickable links.
  • Horizontal lines are not preserved.
Improvement
Architects
12214, 12632, 12633, 12662, 12608
Meta model exchange of Allow empty value
There is now support for export and import of the Allow emtpy value Attribute Type property, using the SystemWeaver XML format.

For information about the property, refer to the swArchitect Reference Manual.
Improvement
Architects
11960
Meta model exchange of Item Type configurations
There is now support for export and import of the Item Type configuration property using the SystemWeaver XML format.

For information about item type configurations, refer to the swArchitect Reference Manual.
Improvement
Architects
11878
Meta model exchange of Part Type configurations
There is now support for export and import of the Part Type configuration property using the SystemWeaver XML format.

For information about part type configurations, refer to the swArchitect Reference Manual.
Improvement
Architects
11877
XML Export: Only active on specified item type(s)
When configured and set to "Active" in Configure the explorer, the XML Export view will now only be available for the item type(s) as specified in the configuration. It would not be available for all item types.

If no configuration is set, XML Export will be available for all item types and with the system default XML Export settings which can be modified.

Given the below configuration example, the XML Export option will only be available to users when they select an item of type with a SID equal to "4TAR".

Example:
<ExportToXMLConfigs>
    <ExportToXMLConfig id= "unique_id" sid= "4TAR">
    <ViewSettings>
      <Caption>Custom export</Caption>
      <RibbonGroup>XML exports</RibbonGroup>
      <Description>hint shown in the ribbon</Description>
    </ViewSettings>
    <IncludedParts>ISES;ISSC</IncludedParts>
    <IncludedAttributes>ISES;ISSC</IncludedAttributes>
    <IncludeItemOwnerValue>False</IncludeItemOwnerValue>
    <IncludeItemOwnerEditable>True</IncludeItemOwnerEditable>
    <IncludePreviousVersionsValue>False</IncludePreviousVersionsValue>
    <IncludePreviousVersionsEditable>True</IncludePreviousVersionsEditable>
    <IncludeLaterVersionsValue>False</IncludeLaterVersionsValue>
    <IncludeLaterVersionsEditable>True</IncludeLaterVersionsEditable>
    <IncludePlainDescriptionsValue>True</IncludePlainDescriptionsValue>
    <IncludePlainDescriptionsEditable>True</IncludePlainDescriptionsEditable>
    <IncludeAttachmentsValue>False</IncludeAttachmentsValue>
    <IncludeAttachmentsEditable>True</IncludeAttachmentsEditable>
    <SwapForeignIdsValue>False</SwapForeignIdsValue>
    <SwapForeignIdsEditable>True</SwapForeignIdsEditable>
    <CheckStatusReleased>False</CheckStatusReleased>
    <ForeignIdNamespace>CustomerID</ForeignIdNamespace>
  </ExportToXMLConfig>      
</ExportToXMLConfigs>


Active With Configuration:
The configured export options will be available in the View drop-down and, if configured, as a button on the Items ribbon menu.
Active Without Configuration:

Improvement
Architects, Users
12593
XML Export: Item ID Export Type Options
The XML Export view (formerly known as Export to XML) now includes new and improved options for what to use as item and part ids in the export.

The Export Type menu includes options for what to use as item and part ids in the export:
  • Plain export will use the item ids.
  • Export for synchronization between SystemWeaver databases will replace the id of each of the exported objects with their Foreign id value, if a Foreign id value exists. In the Prefix box, you can enter an optional namespace string that will be used as a prefix for all "native" items, i.e., items that do not have a Foreign id. The prefix can be used in the target database to clearly identify that the original of the imported object resides in an external database, and store the id as a Foreign id in the target database.
  • Prefixed export will use the item ids and a prefix which you enter in the Prefix box. The prefix is applied to the item ids of all exported items.
Improvement
Architects, Users
12529
XML Export: Legacy options deprecated
The XML Export Legacy options in the Export to XML view have been deprecated.

This includes the use of these elements in configuration of XML exports:
<ExportBitmapsValue>
<ExportBitmapsEditable>
<ExportFontFileValue>
<ExportFontFileEditable>

Improvement
Architects, Users
12552
Update from XML: Renamed XML Import
With the release of R28, the former default view called Update from XML is now called XML Import. The XML import option is used for both XML updates and imports.
Improvement
Architects, Users
12553, 12638
XML Import: Fix issue with configured buttons
This fixes an issue with the activation of multiple configured instances of XML import.
Fix
Fix
12639
XML Import/Update: Only active on specified item type(s)
The configurations of XML updates and imports have historically been used, but there was no means of limiting their use to only specific item types. There is now an option to do this.

When configured and set to "Active" in Configure the Explorer, XML Import views (the view names themselves are configured by the Architect) will now only be available for the item type(s) specified in the configuration. In other words, if you are using configurations, XML Import will no longer be available for all item types.

When set to "Active" and no configurations are pre-defined by an Architect in Configure the Explorer, XML Import will be available for imports/updates for all item types. The system default XML Import settings will be applied, but can be modified on-the-fly by the user.

Active With Configuration:
The configured import/update options will display in the View drop-down with the configured ribbon and caption labels and, if configured, as buttons on the Items ribbon menu.

Active Without Configuration:
The default XML Import option will display in the View drop-down for all item types.

Improvement
Architects, Users
12638
XML Import: Configure handling of errors/warnings
For Architects, it is now possible to specify in XML import configurations whether or not errors and warningswill be allowed, i.e., if users will be able to complete an import with or without warnings and/or errors.In the view itself, an active Import button indicates that the import will be allowed. A grayed-out Import button indicates that the import will not be allowed.

The tags used to define the options are:
<AllowErrors>True</AllowErrors>
<AllowWarnings>True</AllowWarnings>


Valid values are "True" or "False".

Defaults
By default, if the options are NOT defined in a configuration, warnings will be allowed, but errors will not be allowed.

Example Configuration:
<AllowErrors>False</AllowErrors>
<AllowWarnings>True</AllowWarnings>


Per the configuration above, the below import will not be allowed (the Import button remains gray) because there is one error and errors are not allowed.

Improvement
Architects, Users
12591
XML Import: Selection of configuration required
When using New Item: Import from XML, users are now required to select a configuration for their import. If custom imports are not configured by an Architect, the drop-down will present the default XML Import configuration. Users can then modify the import settings on-the-fly as needed.

Improvement
Architects, Users
12553


IT Administrators

Name
Description
Type
User Group
Issue ID
API Upgrade from 1.49 to 1.50
The SystemWeaver API has been upgraded from version 1.49 to version 1.50. This will require that all users receive and utilize the R28 version of the client applications (swExplorer, swAdmin2, swArchitect). In addition, this requires that any API applications developed in-house will need to be recompiled with the newer version SystemWeaverClientAPI.dll.
Improvement
IT Administrators
12696
API/swAdmin2: Login issue when SSL encryption enabled
This fixes an issue where users could not log in to the server using the swAdmin2 application nor the API when SSL was enabled.
Fix
IT Administrators
12566
Server: Improved handling of disrupted database connection
To avoid unwanted consequences (e.g.,corrupt data) caused by the server attempting to continue to run during network outages, etc., the server will now shut down and must be started again when the environment has stabilized. To avoid such restarts, it is of extreme importance that the connection between the SystemWeaver server and the database be kept stable.
Improvement
IT Administrators
12530
Server: Trace call
We have implemented a trace call to follow and measure reading times between client and server. See the SystemWeaver Administration Manual in the Help or on the Support Portal for more information.
Improvement
IT Administrators
12520
Server: Ability to implement monitoring
Systemite can now offer their customers assistance with monitoring by having continuous debugging information sent to Systemite from the SystemWeaver server. Contact support@systemite.se for more information.
Improvement
IT Administrators
12720
SplitServer: Fix of location for generated dlq file
This fixes an issue with the placement of the .dlq log file. When enabled, it now generates in the server directory.
Fix
IT Administrators
12566
swServerService no longer available
The swServerService application is no longer part of the SystemWeaver offerings.

Note: swServerService has effectively been replaced by the swServerMonitorService, which has been available for many years.
Improvement
IT Administrators
12604
swSlaveServer: Optimization of event transactions
The swSlaveServer has been optimized for improved event synchronization between master and slave servers.
Improvement
IT Administrators
12516


Users

Name
Description
Type
User Group
Issue ID
Attributes: Reinstate identity attribute button for parts
This reinstates the Identity attribute button for part attributes which was removed in the previous version.
Fix
Users
12595
Description: Unable to remove text
This fixes an issue with not being able to remove "locked" text segments after pasting them into the Description.
Fix
Users
12659
FMEA Grid: Fix access violation errors
This fixes an access violation error thrown when adding and/or deleting FMEA items in the FMEA grid. It also includes a fix for the same error when adding an action (Issue) to the grid.
Fix
Users
12589, 12577
Part List Editor: Fix access violation errors
This resolved an error thrown when switching between two different part list editor configurations. It also resolved an issue when selecting a parameter value.
Fix
Users
12568, 12606
Reconnect: Dialog presents itself in front of the client
When a connection between an Explorer client and the SystemWeaver server is disconnected, e.g., internet connection is unavailable while moving a laptop from one building to another, the Reconnect dialog will now present itself in front of the client application.
ImprovementUsers11135
Reports: Improvement to report-generated table scaling
This fixes an issue where report-generated tables, i.e., tables defined in Report XML Definitions, were not scaling to fit 125% and 150% display scaling, and instead were shrinking width-wise.
Fix
Users
12570
Reports: Table of Contents scaling
The Table of Contents will now scale when the display setting is properly reset between 100%, 125% and 150%.
Fix
Users
12569
CMS Projects: Issue Progress Column
There is a new column type available for project views.

The column indicates the status of listed issues according to status color, similar to the Status column, but in addition offers a bar style where the position of the bar enhances the indication. An example is given below:
At this time, sorting by Progress is not supported. Read more about the new option in the Help manual.
Improvement
Users
12628
swExplorerMonolith: Application no longer available
The swExplorerMonolith application for offline use is no longer part of the SystemWeaver offerings.
Improvement
Users
12557