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.

Planning

System requirements for the new client: 

.NET 8 (Desktop Runtime)

Login

Upon opening the client the first time, new initial landing page: 

It works as follows depending on how you most recently logged in: 

• If you used username/password, you will be immediately redirected to the login page where you can enter your password. 
• If you used (windows) network authentication or Entra ID authentication, you simply click the button on the initial landing page to log in. 

Filter login entries by server name or port

More visible tool for deleting unnecessary login entries

New User Settings menu added far right on the Title bar

Introduction of Dark theme

New zoom in/out tool

The new swArchitect has a new layout of the functionality.

Metadata

Tools

Data

Reports

There is improved support for path queries containing String array attributes in Configurable Charts. The attribute is now evaluated as an array in this view. 

?> /IXRQ.Select(@STAR)

Before: 

[, , 鱸劍櫋ッ鰐ꅳ郿栯ⁿ簄귈ኇ⁨╇뛚堸퉶㬻᮵䰛䈈㌵楚ʎ긫ᬂ瀬㮏료壦ង᤬䙽蒍뙊ﻡ놁㈦䎲銋臞ꃱ앜ೳ啧ቿ燧㒄뾍♄쁒葾树碣洭닮᱙횝ﶫꫤ밅禕ᣖ甫梪穫檎㧢흳㖪㱱꣜앻ᏺ豱ᜈ褅䜼엞✦ꔓ㈤㪟庾굞�ꤗ駕ᎅᖰ귃୊縲艨䃍铩ₖ黫Ἡ⼇뗡㑱퓫즽ﺾ帣⏵봮⾆㝵�➖ꄅ稌]

Now:
[Prioritize documentation work, Escalation and discussions within the management team to raise awareness., Review the implementation deadlines to ensure they are reasonable., Adjust the deadlines as needed and add the missing documentation for the existing implementations]

Further support for more views and attribute types to follow in later releases.

A new Default attachments feature allows CMS Project administrators to configure default attachments for one or more Issue Types in any Project they manage. Once the Default Attachments metadata is added to the database, the feature becomes available across all Projects and Issue Types. When enabled for use with an Issue Type, the configured default attachments are automatically copied to every new issue created of that type.

File repository

The feature requires the use of a file repository. Ensure disk space is sufficient. (https://support.systemweaver.se/en/support/solutions/folders/31000117154)

Configuration

The metadata for Default issue attachments must first be added to the database. This is done by an SystemWeaver Architect user by clicking the Create metadata button in Configure the explorer > Features. 

Or alternatively, by manually adding the needed Config item type to the metamodel: 

Item type=JDFA, Parent=Config Item

Enabling default attachments for Issue Type

Next, a user with "Change" access rights to the Project must enable the use of default attachments for the Issue Types where it is needed. This is done by navigating to Setup > Issue Types, selecting the Issue type and clicking Enable attachments on a new tab called Default attachments.

Adding default attachments to issue type

Once enabled for an Issue type, CMS Project administrators with "Change" access can upload one or more default attachment files in the same way it is done in the Attachments view. 

A copy of the attachment(s) are then added to each new issue of the given Issue type, and displayed read-only in the New issue dialog: 

Once the issue is created, the attachments are handled as usual. 

The list of item types in the New item dialog and page now includes the item type SIDs and supports filtering the list by Name or SID. 

Expand and Collapse options are now provided in the Types structure tree. 

We’ve reorganized the Refactorings list to group operations by the object they apply to, such as Item Type, Part Type, and Attribute Type.

In addition, there's now expanded support for viewing refactoring results without having to log out and log back in to the swArchitect to verify changes.

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

• Review the Prerequisites for the update operation outlined in above article.
• Maintain a copy of the original database.
• The database update operation takes less than 1 minute to complete.
• If you need to restart the Update operation, close the application in between update attempts.
• If running a mirror server:
  1. Journaling must be cleared and re-initialized after the version update. Previous .swjournal file cannot be used.
  2. New mirror .cache files must be created. Previous .cache files cannot be used.

Example upgrade from database version 1.46:

We're excited to introduce our next generation server with this release!

We've benchmarked the next generation server against an array of databases of different shapes and sizes.

Below are some highlights*: 

Significantly faster startup time

In every single instance measured, we've reduced startup times by more than half on multi-core systems.

For example, a database of ca. 45GB on disk went from a 31-minute startup time to 13 minutes. That's almost 60% less time!

Significantly faster general search

We've fundamentally reworked and optimized the filtering system, and many kinds of search queries are now hundreds or even thousands of times faster. They are so fast, in fact, that the new server's measurements are hard to even perceive in the graph below. We're talking searches now measured in microseconds that used to take whole seconds!

There is still overhead from network data transfer etc to account for, so the greatest improvements will be experienced with searches that used to take a long time but returned few results, e.g. searching for a very specific item name in a very big database.

Faster loading of structure trees

Loading structure trees is now a bit faster in general. The exact improvement experienced will depend on how many items, parts, and attributes are in the structure.

Faster write operations

We see a significant improvement for removing items and creating new versions / branches of items with many parts and attributes.

In the below example, the "NewVersion" procedure was about 4.3 times faster! The real breakthrough isn't just that this procedure is now faster, but that it scales better. Thanks to having improved the time complexity of the algorithm used, adding more parts or attributes to a versioned item will now have a much less explosive impact on performance.

Improved SystemWeaver Path Language (SPath)

The server runs SPath queries as before, but now it's faster, provides more explicit error messages, and includes an improved type checker. The example below illustrates the performance improvement using a recursive algorithm query.

Want to try it out?

If your organization would like to receive the next-generation server for a test environment, please include this with your upgrade package request to SystemWeaver Support. 

The next-generation server is optional in this release and will remain optional in release R52 (June 2026). The legacy server will be retired and no longer available starting with release R53 (October 2026).

* Actual performance improvements may vary depending on database size and the structure and content of the data.

Due to updates to Jira application components and the Jira Rest API, changes needed to be made to our Jira integration with Jira Cloud so as to work properly. 

Jira Cloud now requires https URLs for integrated applications. Therefore, the configuration of the SystemWeaver.RestAPI now requires "requireHttps": true, and a certificate: 

{

  "SystemWeaver": {

    "restApiBaseURL": "localhost",

    "restApiPort": 9000,

    "requireHttps": true,

    "certificateSubjectName": "enter certificate subject name here",

    "systemWeaverHost": "localhost",

    "systemWeaverPort": 8888,

    "allowHttp2": true,

    "DomainName": "SYSTEMITE"   

  },

....

This is a breaking change as without this, the SystemWeaver tab in the Jira web issue will not display SystemWeaver data.

This release includes security and stability improvements through a maintenance update of a third-party component. No functional changes are expected as part of this update.

In addition, a number of code analysis warnings were resolved.

Similar to what is already in place for General search for Items, there is now a 3-minute time limit on searches done against an entire project (QGetIssues) for improved user experience. It is very rare to come even close to the time limit. If it happens, it is almost always not the user's intended/needed search. Setting the limit minimizes the effect these searches have on other users' ability to work. 

Should one of these searches reach the new time limit, the user will receive the following message: 

The user can then refine their search by adding additional criteria, e.g., Reporter, Assigned to, Issue type, etc.

Server administrators or project managers can find instances of long QGetIssues searches in the swServer.log if they wish to use the opportunity to provide suggestions for refining the search.

Mirror server users will experience better performance as mirrors now handle more traffic directly instead of forwarding requests to the main server.

Some optimization has been done related to the removal of objects having attributes. One example is when you are deleting an item structure with many parts. 

By upgrading to Skår (R51), you will receive this optimization automatically. No additional steps are needed.

To obtain the improvement without upgrading, you can run a new script provided in the swDatabaseManager which we strongly recommend. Runtime is a few minutes.

To run the script without upgrading to R51:

1. Stop the server. 
2. Open the swDatabaseManager. 
3. Run the Add association table indexes script. The script takes some minutes to run. 
4. Once it is finished, the server can be started. 

Log window upon script completion: 

The Statistics log can now include a log of when an item is moved from a library to another.  The call type is named "ChangeLibrary". 

• "item" is the xID of the moved item. 
• "fromLibrary" is the xID of the library from which the item was moved.
• "toLibrary" is the xID of the library to which the item was moved. 

{

   "time":"2026-01-20 14:28:13.0092",

   "seqId":"183",

   "sessionId":"8",

   "ip":"127.0.0.1",

   "userId":"x0E0000000000A8C0",

   "username":"tracy.klein",

   "email": "tracy@company.com",

   "call":{

      "type":"ChangeLibrary",

      "item":"x040000000001673B",

      "fromLibrary":"x13000000000085A7",

      "toLibrary":"x1300000000014021"

   }

}

To include this with your upgrade:

• Ensure you have sufficient disk space given the assumption that the log file will grow in size. 
• The main server installation handles the "change library" operation as it is a database operation. "ChangeLibrary" is not logged in a mirror server Statistics log. Replace the Systemite.SystemWeaver.TcpSubServer.exe.nlog in your main server installation with the one provided with the delivery. Again, no need to do this on the mirror server(s).

The Statistics log can now include the project's Name for IssueViewLoaded entries. 

Before: 

{

  "time": "2025-11-26 12:01:51.8677",

  "seqId": "0",

  "sessionId": "1",

  "ip": "127.0.0.1",

  "userId": "x0E00000000000009",

  "username": "john",

  "email": "john@company.com",

  "action": {

    "type": "IssueViewLoaded",

    "view": "Open bugs",

    "loadTime": "00:00:00.007"

  }

}

Now: 

{

  "time": "2025-11-26 12:01:51.8677",

  "seqId": "0",

  "sessionId": "1",

  "ip": "127.0.0.1",

  "userId": "x0E00000000000009",

  "username": "john",

  "email": "john@company.com",

  "action": {

    "project": "Global Requests",

    "type": "IssueViewLoaded",

    "view": "Open bugs",

    "loadTime": "00:00:00.007"

  }

}

We have recently added support for Select all (Ctrl+A) and multi-select in the All references view. 

Changes to an Item Owner now display immediately in the Complate status view for all clients. 

This resolves an access violation error in the Configurable Grid view when using Select search results.

A new Default attachments feature allows CMS Project administrators to configure default attachments for one or more Issue Types in any Project they manage. Once the Default Attachments metadata is added to the database, the feature becomes available across all Projects and Issue Types. When enabled for use with an Issue Type, the configured default attachments are automatically copied to every new issue created of that type.

File repository

The feature requires the use of a file repository. Ensure disk space is sufficient. 

Configuration

The metadata for Default issue attachments must first be added to the database. This is done by an SystemWeaver Architect user by clicking the Create metadata button in Configure the explorer > Features. 

Or alternatively, by manually adding the needed Config item type to the metamodel: 

Item type=JDFA, Parent=Config Item

Enabling default attachments for Issue Type

Next, a user with "Change" access rights to the Project must enable the use of default attachments for the Issue Types where it is needed. This is done by navigating to Setup > Issue Types, selecting the Issue type and clicking Enable attachments on a new tab called Default attachments.

Adding default attachments to issue type

Once enabled for an Issue type, CMS Project administrators with "Change" access can upload one or more default attachment files in the same way it is done in the Attachments view. 

A copy of the attachment(s) are then added to each new issue of the given Issue type, and displayed read-only in the New issue dialog: 

Once the issue is created, the attachments are handled as usual.

The following improvements have been made in the Occurrence matrix view for Enumeration attributes: 

Any enum value colors and descriptions are now shown in the drop-down list. 

A filter tool enables you to find hits anywhere in the values.

We recently made a significant performance improvement in the Occurrence matrix view decreasing the initial view loading time by 50-80%. 

Example:  Matrix with 334 columns, 1252 rows, one attribute column:   

Before: 12.00 sec

Now: 3.00 sec

What is the Occurrence matrix? Generic and flexible view that presents a matrix of rows of items to be managed, and columns of items that can include the row items as parts, or "occurrences", of the row items. 

Note: For dropdown attribute editors, the dropdown arrow currently is not shown. 

References: Optimized loading

The initial loading of the References view is significantly faster now when working with items with many references. 

Examples (in seconds): 

An item with 675 references

>> ~40% faster

An item with 1077 references

>> ~68% faster

An item with 1032 references

>> ~85% faster

The User account options, found under File>Options, now includes the display of the current user's access rights (Read/Write or Read-Only)

The Matrix for Working with Variant Models view now loads >50% faster than before for a significant improvement when working with larger matrices. 

• Type icons:  Visibility of darker icons is less optimal. We are working on new versions of the type icons.
• Help:  The F1 shortcut to open the Help section is not working. 
• Description: To add/modify Description content, double-click is needed to open the editor. 

• Dropdown arrow for combobox attribute editors is currently not displayed.