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.

Admin/Architect client: New style for initial login page

The SystemWeaver Admin and Architect client has a new, modern look for the initial landing page. 

23744

Admin/Architect client: Support for startup argument

Command-line argument support is now available in the SystemWeaver Admin and Architect clients. This functionality was missing from the initial releases of the new client. The currently supported command-line options are listed below:

--serverName <serverName> The name or IP address of the SystemWeaver server

--serverPort <serverPort> The port number of the SystemWeaver server

--loginName <loginName> The username that will be set in the client

-?, -h, --help Show help and usage information

"C:\SystemWeaver\Client\SystemWeaver.exe" --serverName=sys7 --serverPort=1346

24470, 24213

Admin: Introduction of new role

As part of the ongoing improvements to Role-Based Access Control (RBAC), a new role with SID CONF has been introduced in SystemWeaver.  This is a breaking change if your organization already uses the SID CONF for an existing role.  In that case, you must assign a different SID to that role to avoid a conflict when this new role is enabled. More details to follow in a later release of the client. 

In addition, Administrators and Architects will now see a Roles selector that displays their assigned roles in the server. If a user has both roles, they can hide the tab associated with either role by deselecting it in the drop-down list.

24701, 24941

AI Product licensing

With this release, the AI products require license add-ons.

• WeaverAI: Only users assigned a license key with the WeaverAI add-on can use the functionality. If you are upgrading from the initial WeaverAI release to R53 and want to continue using it, this is a breaking change.
• SystemWeaver MCP Server: Only users assigned a license key with the MCP Server add-on can access the full set of tools. Without the add-on, only server information is available.

Add-on access takes effect immediately when users are assigned the appropriate license key. No server restart is required.

Contact SystemWeaver Support to obtain either or both add-ons. Both add-ons are complimentary for the R53 release.

API: Major version update

24813

API: Support for creating description references

22316

REST API: Entra ID Token/Client certificate based auth

This release includes support for Entra ID authentication with our REST API.

curl --insecure -X POST http://127.0.01:9000/token -d "entraauthentication=true&grant_type=password&id_token=[entra_id_token]"

22875, 23039

REST API: Token timeout is random and not correct

The REST API uses two tokens with separate timeouts: an access token, valid for 2 minutes, and a refresh token, valid for 10 minutes.

Previously, the token lifetimes could vary randomly by an additional 0–16 minutes. Now, both tokens consistently expire after their configured set times.

New feature: Token expiration times are now configurable through appsettings.json, allowing the validity periods to be adjusted to meet specific requirements.

{

"SystemWeaver": {

"restApiBaseURL": "localhost",

"restApiPort": 9000,

"requireHttps": false,

"certificateSubjectName": "localhost",

"systemWeaverHost": "localhost",

"systemWeaverPort": 8888,

"allowHttp2": true,

"DomainName": "SYSTEMITE"

 },

"Tokens": {

"Key": "0123456789ABCDEFX",

"Issuer": "http://systemite.se",

"Audience": "http://systemite.se",

"AccessTokenValidTimeSeconds": "120",

"RefreshTokenValidTimeSeconds": "600"

 ...

}

21692

XML Export/Import: Updated version

This release includes an updated version of XML Export and Import to support the new Description References. The XML schema itself remains unchanged.

Important: XML exports and imports must now be performed using the R53 clients or standalone tools, such as swXmlExport.

Although the XML schema is unchanged, the updated Description format introduces a compatibility requirement. XML files exported using earlier client versions are not compatible with the updated Description format.

Attempting to import such files will result in an "Invalid file" message and the following log entry: The XML file uses an old format (root element 'SystemWeaver4') that is not supported by this version. Re-export the file from a SystemWeaver version that matches this one.

The resolution is to re-export the data using an R53 client or export tool before importing it.

Impact on XML Data Exchange Between Organizations:

This change may be a breaking change for organizations that exchange XML data. If one organization upgrades to R53 while the other continues using an earlier version, XML data exchange between them will no longer be supported. Both organizations must upgrade to R53 to continue exchanging XML data.

24943

Architect: Attribute type description refresh

Now, when you update an Attribute type Description in the Architect, the change will appear immediately without having to refresh the page. 

This information is available to users upon Alt+Click on an attribute: 

23916

swExport: Introduction of generated XML export

The swExport tool now supports exporting generated XML, providing the same functionality as the configurable XMLs view in the client. This enables you to implement custom export solutions tailored to your organization's needs.  The export functionality has no required meta model, or item structure. It is suitable for all generated XML use cases, such as .reqIF exports. 

Since swExport also supports Document exports and configurable Grid, Graph, and Report exports, you must set the type attribute to "xml" when exporting generated XML. See the executable's Help for information about options. 

Example Command Lines:

Using Username and Password:

swExport serverName=sys7 serverPort=1344 serverUsername=john serverPassword=password itemID=x040000000011A242 type="xml" configItem=x34000000001DFB9B filename="C:\Work\Specification document(1).reqif"

Using Network Authentication:

swExport serverName=sys7 serverPort=1344 itemID=x040000000011A242 type="xml" configItem=x34000000001DFB9B filename="C:\Work\Specification document(1).reqif"

WeaverAI: Various improvements

Attributes: Part names shown in blue

Parts with part names now display the names in blue in the Part attributes grids. 

24507

Attributes: Support for copy item in part attributes grid

The Part Attributes grid now supports copying selected items to the clipboard using Ctrl+C and sorting the grid by part attribute values.

Change log: Template display

If a Change log template is configured, it will now always display when the change log is empty. This is the case even after clearing a Change log entry. 

What is a Change log template? An option for Item Type Configuration called ChangeLogTemplate. It supports presenting a template to users for Version change Log entries.

Example:

<ItemTypeConfig>
 <ChangeLogTemplate name="">
 Version:
 Date:
 </ChangeLogTemplate>
</ItemTypeConfig>

24360

Clone item: Support for clone with signature attribute

Using the Clone item view, it is now possible to clone items that have Signature attribute(s). The resulting clone will not have a value set in the attribute. 

What's a Signature attribute? The Signature type attribute provides a means of electronically signing an item. The signing attaches a block of identification data to the item that you sign.

19714

Complete status: Immediate refresh

Changes made to Type and Home library are now also immediately reflected in this view in other clients. 

Description: Updated description reference links

With this release, Item and Part reference links in Item Descriptions are now represented as standard hyperlinks, replacing the previous special link format. This change lays the foundation for greater flexibility and additional link options in future releases.

Users should notice no difference in functionality. However, since these links are now standard hyperlinks, they can be styled using regular formatting.

24829

Issues: Add note and lost connection

When staging an Issue note and your connection is lost to the server, e.g., VPN or internet down, you will now have an opportunity to save your content to clipboard. In this way, you can paste it in a Note again once your connection is reestablished. 

Occurrence matrix: Refresh option

Views that are not real-time collaborative require an explicit refresh action by the user, like switching between views or using the F5 refresh shortcut. The Occurrence matrix view now supports the F5 shortcut as well as a right-click menu option. 

Paste special: New search tool

The Paste Special option in the Structure tree now includes a search tool. When the dialog opens, you can simply use the keyboard to search for the desired part type and press Enter to select it and apply. Arrow keys can also be used. 

Printing: Option to print with watermark

The initial* version of a Watermark option for printing Reports and Documents to PDF is now available.

To enable this feature, a SystemWeaver Administrator must enable "Watermark" in Capabilities in the Admin utility. Supported values are string or path query. The value must return true or false. Examples: 

<Capabilities>
 <Capability name="Watermark" test="true"/>
</Capabilities> 

< !--Using Path Query: --/>
 <Capabilities>
 <Capability name="Watermark" test="CurrentUser = Owner or CurrentUser.Name = 'admin'"/>
</Capabilities>

When enabled, the Watermark capability enforces watermarking for all Print to PDF with bookmark print jobs and disables the print options that do not include bookmarks (i.e., the Print button).

When the Watermark capability is not enabled, both Print with bookmarks and Print without bookmarks options remain available, as before. 

The current watermark is hard-coded to include: Username, Name, Date of Print to PDF

For more information, see Restricting Standard Capabilities and Example Watermark Capability Configurations

* This is a first version. Additional updates may come in later releases

24178, 24069, 13926, 13389

Printing: Improved error handling for PDF bookmark case

In cases where a PDF with bookmarks does not generate due to a problem in the Document's XML configuration, users will now receive a message "The PDF was created successfully, but bookmarks could not be generated. Contact your SystemWeaver Architect to ensure that the section elements in the document's XML configuration are correctly defined." and the print job will be completed without bookmarks. 

24197

Reconnect behavior for Entra ID

Following the introduction of Entra ID authentication in a recent release, we have now improved the Reconnect behavior in the Admin/Architect client. 

23790

Server: Faster searches

We sped up General search and Search in project in several ways:

• Searching on a text attribute (<ItemAttributeCompare>) is much faster on large databases. In a large customer database, a search on an attribute used by 2 million items dropped from over 3 minutes to just 35 seconds.
• Searches that combine several conditions with <And> or <Or> now narrow down the search space much faster.
• Issue searches on CreatedBy or LastChangedBy are faster, and run in parallel like item searches.

24666

Server upgrade and overall benefits

If you have yet to upgrade to the next-generation server, you'll be doing so with this release. Please review the updated system requirements for the server: https://support.systemweaver.se/en/support/solutions/articles/31000179376-server-application-system-requirements-r53-and-later

swServer.ini

There are very minor changes to the server configuration file. You can either:

1) Keep your existing swServer.ini and make the minor changes described below or 

2) Use the provided swServer.ini.example included in the Server directory and replace the example settings there with the settings from your existing swServer.ini.

New [General] section

There is a new section called [General] which is required. It contains swServer log settings. Assuming you have server logging turned on today (using the swServer.props file) and want to continue to generate a Server log (which we recommend), you would need to set the log setting here in the swServer.ini. See the example file provided in the swServer.ini.example. The settings are self-explanatory.

In the [MainServer] section, it is unchanged. Just make sure these two lines are commented out using ; symbol if you are using an older swServer.ini

;CallLogging=on/detailed

;LogFileDirectory=

In the [Tcp] section, it is unchanged. Just make sure that this line is commented out using ; symbol if you are using an older swServer.ini

;DLS=True/False

Monitor Service: Because the swServer log configuration is now set in the swServer.ini, you will no longer need the swServer.props configuration file. You can remove the <props> line from the <Server> in the swServerMonitorService.settings file since the next-gen server does not use the swServer.props. 

Example swServerMonitorService.settings file - remove the entry shown in yellow below and save your change:

The overall benefits of the server upgrade are:

Smoother work when many people use it at once

• Reading and writing no longer hold each other up, so the system stays responsive while others work.
• Logging in and everyday edits no longer wait for large writes to finish.

It's faster in so many ways

• General search can be thousands of times faster. The larger the database, the bigger the gain. With many results, most of the time goes to fetching them from the server.
• The server starts up to 7× faster.
• Creating new versions of items is up to 8× faster.
• Removing items is up to 21× faster.
• Server-side Path queries can be 5× faster depending on the query, sometimes much more.

Option to run on Linux

• The server, tools and GUIs all run on Linux as well as Windows.

PostgreSQL support

• You can now store your data in PostgreSQL, as well as SQLite and MS SQL. PostgreSQL performs about as well as SQLite, and much better than MS SQL.

Server: Update of database version

The database version identifies the version of the internal database schema used by SystemWeaver. With Utby (R53), the version has been upgraded from 1.48 to 1.49 due to updates to Description references in the formatted Description. This is a breaking change. 

System Administrators use the swDatabaseManager to update the database version. See Updating the Database Version.

With the new swDatabaseManager in this release, if you are upgrading from a database version earlier than 1.48, you would simply click the Upgrade to 1.49 button and it will run each database version update automatically.

Example upgrade from database version 1.47 to 1.49: 

Once the upgrade operation is completed, it will indicate completion and provide a log of the process. The log can be printed to a text file by clicking the Save as button. Note that there may be cases where content was invalid (unreadable "garbage" even by an earlier release), and could not be converted. In such instances, the conversion process will provide information of what the rvf contained, e.g.: 

With this information, it's easy to see if it's zip file data or text utf-8/16 and recreate the text. In all likelihood, it is "garbage" data entered for testing purposes that can be ignored.

.NET Upgrade 8.0 to 10.0

The SystemWeaver Admin and Architect client has been upgraded from .NET 8.0 to .NET 10.0. This upgrade delivers improved performance, security, stability, and compatibility with modern technologies, while providing a stronger foundation for future enhancements and ongoing support. This is a breaking change if .NET 10.0 or compatible version is not installed. Users who do not have .NET 10.0 installed will be prompted to install it when they launch the client. 

SystemWeaverClientAPI

The SystemWeaverClientAPI will continue to use .NET 8.0 to maintain compatibility and support for all customers.

Important Note: The ClientAPI is planned to be upgraded to .NET 10.0 in a future release.

24681

Client: UI and development component upgrade

In line with our maintenance standards, a UI and application-development component library has been upgraded. The upgrade provides:

24685

Initial release of SystemWeaver MCP Server

Introducing our initial version of the SystemWeaver MCP Server!

The SystemWeaver MCP Server connects AI assistants to a SystemWeaver model. It implements the Model Context Protocol (MCP), so any MCP-capable client (for example Claude Desktop or Claude Code) can navigate, read, and — where you allow it — change SystemWeaver content in natural-language conversations.

The server runs locally on Windows and talks to your existing SystemWeaver broker over the SystemWeaver ClientAPI. It uses the permissions of the SystemWeaver user it connects as, so the AI assistant can see and do only what that user can.

Tool overview

The server provides 46 tools, grouped into capability areas ("axes"). Each area can be turned on or off separately. A disabled area is not offered to the AI assistant, and a call to one of its tools is refused.

* All write areas are off unless you turn them on. The example configuration that ships with the server is configured for read-only.

Features

Requirements

Known limitations and recommendations

Getting started

1. Run SystemWeaverMCP.CredentialTool.exe, enter the broker connection details, and click Test & Save.

2. Copy appsettings.example.json to appsettings.json next to the server. Turn on the write areas you need.

3. Register the server in the MCP configuration of your AI client.

4. Check the setup with mcp_server_info from the client, or run SystemWeaverMCP --test.

See INSTALL.txt in your delivery for the full setup guide.

Jira: Limited support for integration with Data Center

As Atlassian is phasing out Jira Data Center and no longer sells Data Center licenses to new customers as of March 30, 2026, please note that our ability to support an integration with Jira Data Center is limited and may require that testing of new features and/or bug fixes be done by the customer until Data Center reaches final end-of-life for those existing customers. We continue to support an integration with Jira Cloud. 

Not familiar with SystemWeaver's built-in Issue management? Learn more at https://support.systemweaver.se/en/support/solutions/folders/31000115369, or contact us for a demonstration. 

Jira: Support for filtering projects

SystemWeaver's integration with Jira now includes an option for specifying which Jira Projects are to be integrated with SystemWeaver. The configuration of the SystemWeaver add-on in Jira includes a new setting called Jira Projects. Here, you include a list of the Jira projects where the SystemWeaver "tab" in Jira will display linked Item information. 

The SystemWeaver–Jira integration now allows you to specify which Jira projects are integrated with SystemWeaver. A new Jira Projects setting has been added to the SystemWeaver add-on configuration in Jira. Use this setting to specify the Jira projects in which the SystemWeaver tab displays information about linked Items. 

15894, 23928

Server: New swDatabaseManager

R53 comes with a new Database Manager for the R53 server. It handles the same everyday tasks as the legacy Database Manager, with these improvements:

23346

Server: Continued Linux improvements

R52 introduced early-access Linux support. R53 brings more support for running the server as a regular service on Linux.

Server: Further improved startup time

The next-gen server now starts faster, since it does more of its startup work in parallel. On our largest test database, startup went from 24 m 50 s to 8 m 30 s on Windows and to 7 m 10 s on Linux. The cost is slightly higher memory use during startup, but steady state memory use is technically the same as in R52.

24361

Server: Legacy scheduler removed

The legacy request scheduler in the TCP subserver was disabled by default in R52, and is completely removed in R53. The scheduler tried to make request handling fairer back when the server had a global reader/writer lock. Since R52, the next-gen server no longer has that lock.

Server: Mirror initialization over the network

A mirror server can set itself up by fetching all data from its main server over the network. In R53, this works better for large databases:

While we continue to recommend using a cache file for mirror servers for production environments, in-memory caching is a good alternative for a test environment or when a persisted copy of the database on disk is undesirable for other reasons.

Example swServer.ini for mirror server using in-memory cache: 

21169

Server: Non-blocking writes

In R52 we removed the global read/write lock so that read calls to the server no longer block a writer. 

With R53, the next-gen server can run some writes at the same time as other writes! This brings an overall performance improvement to the server, and greatly alleviates worst-case slowness. 

How it works: Each write works on its own snapshot of the database, and when it is done, the server checks whether another write that finished in the meantime changed the same objects. If not, the write goes through. If there was a conflict, the server throws away the result and runs the call again on the new state of the database.

Two writes can conflict even if they change different objects. For example, if two different users are renamed to the same name at the same time, each write on its own sees that the name is free, but together they break the rule that user names are unique. We went through each call below to find cases like this, and made the server treat them as conflicts too. Together with the write conflict check, this is why data consistency guarantees remain unchanged. 

These operations now run concurrently with other writes:

All other writes still run one at a time, as before. We plan to add more calls to this list in coming releases, starting with the most high-impact ones.

From the perspective of an API client, like swExplorer.exe, the only difference brought by this change is better performance. To show the difference, we ran a load test where one user keeps running long writes while other users log in and rename items. We repeated it with long writes of different durations, from none at all up to 20 seconds.

The curve shows the time within which 9 in 10 logins and renames finished, on R52 and R53 Next-Gen.

With R53, logging in and renaming an item take the same time no matter how long the other write runs. A single, slow write will no longer block users from logging in, reading data, and making certain simple kinds of edits.

24810, 24567, 24569

Server: Improved swTestServer