When activating a new or existing account, you will now clearly specify which license type the account should use: Read/Write or Read-only. 

This information will display in the Status column in the Users list: 

Accounts that are deactivated have a status of "Disabled".

Note: As before, if you select Read-only and there are only Read/Write licenses available, a Read/Write license will be used.

• Logging in
• Changing their own Name
• Changing their own email 
• Changing their own password

Note that non-administrator users can also obtain the Server ID information which is needed during license set-up.

SwAdmin2: Search and filter in Roles

It is now possible to search in the Users in role list when viewing a Role membership. 

In addition, more user properties, e.g., Network id, E-mail, Active status, etc. are displayed.

It is now possible to log in with the API using Windows username and password from a computer that is not connected to Windows AD.

SWConnection.Instance.ServerMachineName = "localhost";

SWConnection.Instance.ServerPort = 1768;

SWConnection.Instance.AuthenticationMethod = AuthenticationMethod.NetworkCredentials;

SWConnection.Instance.LoginName = "windows-username";

SWConnection.Instance.Password = "windows-password";

SWConnection.Instance.Login();

If you specify AuthenticationMethod = AuthenticationMethod.NetworkCredentials, then the Windows username and password are used for authentication, instead of the SystemWeaver username and password. If correct, the user will be logged in as the SystemWeaver user associated with given Windows user.

Note that while the client does not have to be connected to the AD, the Server has to have access to Windows AD or this will not work.

Note: The method SWConnection.Instance.AuthenticationMethod 

replaces the method SWConnection.Instance.UseNetworkAuthentication which has been marked as obsolete.

If you want to use network authentication, set

SWConnection.Instance.AuthenticationMethod = AuthenticationMethod.NetworkAuthentication;

The default behavior, which is to validate with SystemWeaver username/password, is the same as before and corresponds to

SWConnection.Instance.AuthenticationMethod = AuthenticationMethod.SystemWeaverCredentials;

Documentation containing methods that can be used by the SystemWeaverExtensionsAPI will now be included in deliveries as a resource for in-house developers of extension views. 

SystemWeaverExtensionsAPI.xml

There are now endpoints for attribute types so you can get, patch and post:

restapi/attributetypes

Get attribute type by handle:

GET restapi/attributetypes/{handle}

Get attribute type by SID:

GET restapi/attributetypes/sid/{sid}

Get information about an attribute type including lists of associated item types and part types:

GET restapi/attributetypes/{handle}/full

Get list with extended information about AttributeType: 

GET attributetypes/extended

Update an attribute type:

PATCH /restapi/attributetypes/{handle}

Properties that cannot be changed are:

• Handle
• DataType
• Data dimension
• SID

Create a new attribute type:

POST /restapi/attributetypes

The following endpoints have been added for libraries:

Get all libraries and sub-libraries for a structure by handle:

GET libraries/{Handle}/tree

Get root library information:

GET /restapi/libraries/root/full

Get root library tree:

GET /restapi/libraries/root/tree

Update a library:

PATCH /restapi/libraries/{handle}

Properties that cannot be changed are:

• Handle
• DataType
• Data dimension
• SID

Create a new library:

POST /restapi/libraries

It is now possible to modify these additional user properties using the existing endpoint:

• Username
• Name
• Add user to a role
• Remove user from a role

PATCH /restapi/users/{handle}

The Database Status Report available in the swArchitect now includes information about whether an item type is abstract, and whether an item type or part type is deprecated. 

The following new Type icons have been added. They can be used as image icons for item, part, and issue  types, as well as for multi-instance configurable views, and plugins:

The fixes issues where ItemAttributeColumn wasn't working as intended with RowObject in grids.

• The ItemAttributeColumn appeared gray and readOnly="false" was not working
• The color of an attribute (in the ItemAttributeColumn) was not working

An AllowRemovePart constraint is now available for part type configuration.

The constraints are expressed by an XML element:

<AllowRemovePart value=""/>

Valid attribute values are 'true' (default) or 'false'.

The <AllowRemovePart> tag defines if it is possible to perform a Delete or Remove part(s) action in the GUI, i.e., delete a part.

The error message for PathInTagWriter (used in the configurable views) is improved to contain more information about the error.

Before: 

After: 

The following methods, object properties, and operators have been added to the Query Language to retrieve data related to library and access rights. 

Methods

• Admins
• AllUsers
• GetUserAccess
• Groups
• Users
• User

Object Properties

• Owner (Valid for: item, issue, attachment, node, HomeLibrary)

Operators

• in

Example Graph

See Viewing Library and Access Rights for more examples.

Two new Path Query methods are supported: Min and MinByDate, corresponding to the already available Max and MaxByDate methods. 

Min 

Returns the minimum value in a set of integer values.

[Integer].Min -> Integer

Example

/part::5ACV.Select(@5CVA).Min

MinByDate

Returns the objects from the list with the oldest date property.

[a].MinByDate(a -> date) -> [a]

Example

/IRRS.MinByDate(LastChanged)

The SystemWeaver <Context/> now supports the use of ItemGroup, which results in reducing the context size in the use case where AddParts is only added for structuring items.

Example

<Context name="context1">

  <ItemGroup name="g1" select="/SID1/SID2..."/>

  <AddParts owner="g1" sid="SECL" part="req" defobj="requirement"/>

  <AddParts owner="main" sid="SECT" part="sect" defobj="section"/>

</Context>

The "as" attribute in <Variable> and <Parameter> (Function's Parameter) now supports additional data types, aside from Item, Integer and String. With R36, the supported data types are:

List

• [xxx] creates list of type xxx

Single

• Boolean
• String
• Date
• Float
• Integer
• Int64
• Item
• Part
• Node
• User
• Issue
• Object

Legacy

• Items (for a list of items or instead one can use [Item]).

Examples

<Variable name=".." as="[User]" select="..">

<Variable name=".." as="User" select="..">

<Function name="fun1" as="String">

  <Parameter name="para1" as="[User]"/>

  ...

  <Value select="$para1 ..."/>

</Function>

The Reg exp pattern for attributes of string data type is now included in meta model XML exports (incl. via Metamodel Cutter in swArchitect) and will then also be included in meta model imports.

Reg exp is now also included in Metamodel Diff. 

The ComponentGraph extension view reference dlls have been upgraded. The upgrade results in the following improvements: 

• Less edge crossing
• Improved placement of edge labels
• Increased performance

In addition, it lays the groundwork for future improvements to the extension. 

The following improvements have been made to the configurable graph view. 

The menu options previously located in a right-click context menu are now available on a toolbar at the top of the view. 

Similar to when working in the structure tree, the Graphs view now interacts more with the standard options on the Items ribbon. 

Open and Copy

When selecting a node in the graph, the Open and Copy options on the Items ribbon are now also available for more interactivity.

You can also use their respective shortcuts, e.g., Ctrl+C, Ctrl+O, etc. 

Copying an object in the graph, i.e., node, port,..etc., using Ctrl+C or the right-click Copy ID(s) option will put the object(s) unique ID on your clipboard. You can then, for example, use Ctrl+G to find all occurrence in the structure tree, paste it in an email, etc. 

Multi-select is supported as well, as shown above. 

Find

With the graph view in focus, you can use the Find menu group options (including the Ctrl+F shortcut) to find objects in the graph.

Add Note

With the graph view in focus, you can use Add note to add a note to the selected item.

Selection

A new style for indicating selection of node and parent node has been introduced. 

It is possible to select ports now and copy them if needed.

In addition, the "SGraphML" file format for exports has been deprecated.

Improvements have been made to the image editor which can be used to decrease image size. There is now a Scale option that can be utilized. Also, the Image preview now adjusts visually when you scale the size.

Note: The primary purpose of the editor is to reduce an image's size. If an image fits within the overall description size limit, i.e., no "excessive data size" message is thrown, then a quick resizing of an image's height and width can be done directly in the Description. The editor is not needed for this purpose. 

Some enhancements to the plugin have been made: 

• Support for creating sub-issues
• Support for creating Epic link
• Support for mandatory custom field types when creating a Jira issue
• Support for linking and creating Jira issues to test case results