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.

For extension errors, the log now prints which extension the error is coming from.

In addition, exceptions are now logged as error and you don't have to switch to debug to see them. One possibly downside is that you may encounter exceptions that are not actually issues.

A clear message will now display to inform there is no support for updating the following attribute types using Actions: 

• Custom ID (AUID): Single
• Enumeration: Set
• External reference: Array, Single
• RVF: Single
• String: Array
• User: Set
• Computed (single value set by logic)
• Identity (single value set by server)
• Signature (uses network authentication)

Example: 

To help users in the event of an error, we have now implemented so that even if a confirmation dialog is not activated via the script, e.g.,:

<ActionBinding actionId="setAttribute" caption="Set Attribute" confirmationDialog="false">

it will still display if there is an error.

With this release, we introduce support for using the Path Query Language for groupBy and objectName attributes in the grid. 

Until now, a hard-coded integer value was always used to represent the order of the column to be grouped by: 

<Options>

  <Grouping groupBy="1,2"/>

</Options>

It is now possible to dynamically generate the order based on a path query:

<Options>

 <Grouping groupBy="#{? pathQuery}"/>

</Options>

Limitation: The grouping tag does not have access to variables or functions in the rest of the grid definition. This is an improvement planned for future development.

In addition, for columns, the objectName now also supports a path query value, i.e., {? pathQuery}.

To enable passing the multi-selected row objects as a parameter for an action, a new behavior for <Item> and <Part> IDs has been introduced which includes dynamic and fixed options. 

• Dynamic ID is the default, unless otherwise specified.
• A fixed ID is enforced by adding #0 at the end of the hard-coded ID to prevent dynamic generation.

Examples:

<Action id="action1" caption="Create Variant with selected TCs">

     <Parameter name="testCases" as="[Item]"/>

     <Parameter name="testSpec" as="Item"/>

     <Item id="TC" match="$testCases"/>

     <!--Dynamic ids will be generated, i.e., TC#1, TC#2, TC3,..-->

     <Item id="TS" match="$testSpec"/>

     <Item id="VAR#0" name="#{? 'Variant of ' + $p2.Name }" itemType="JTSP" lib="HomeLibrary"/>

     <!--Fixed id is enforced i.e., VAR#0-->

     <Part id="TSVA_TS#0" partType="TSVA" owner="TS" defObj="VAR#0"/>

     <!--Fixed id for the the part is enforced i.e., TSVA_TS#0-->

     <Part partType="ITEC" owner="VAR#0" defObj="TC"/>

</Action>

For more managed model release processes, it is now possible to control status changes to "Released" based on specific conditions.

A new <AllowStatusChange> tag is available to define a condition that must be met to allow for a change to the target status of "Released". Supported values are string or path query. The value must return true or false. List is not supported. If a configuration is not added, it will work as before (true).

<ItemTypeConfig>

  <AllowStatusChange status="Released" value="" message=""/>

</ItemTypeConfig>

When a status change to "Released" is not allowed per the configuration, the user will receive a message in the Batch operation dialog for those items for which a status change was not possible. For items that do met the criteria, the operation will complete as expected.

Example 1: Items cannot be released. Default message used.

<ItemTypeConfig>

  <AllowStatusChange status="Released" value="false"/>

</ItemTypeConfig>

Example 2: All parts with SID=ITHP must have 'CS Released' status to allow a status change to 'Released'.

<ItemTypeConfig>

  <AllowStatusChange status="Released" value="all /ITHP satisfy ItemStatus.ToString in ['CS Released']" message="All HW Sub-elements must be CS Released."/>

</ItemTypeConfig>

Please note: 

• For backward compatibility, the previous top tag <TypeConfig> can still be used for item type configuration, however, to utilize the new <AllowStatusChange>, you must use <ItemTypeConfig>.
• Ensure your user organization is aware of this new constraint if you will be implementing it. 

This fixes a server out of sync scenario caused by a Change data dimension refactoring  when invalid values are involved. The refactoring is now handled, and the items with the invalid values are noted in the log file. 

This update enables the use of the '?' in regular expressions for validating String attribute values.

Example: 

^(?!\.).*$

Result: Given the above example, one can write anything except a dot in the first character position, e.g., "kljasd23", but you cannot write "." or ".kaljsdj".

The swExport tool can now be used to export SystemWeaver configurable Reports in PDF format. You can implement your own application solution for report export using this tool based on your organization's needs.

The export functionality has no required meta model, or item structure. It is suitable for all configurable Report use cases, and provides support for specifying parameters. 

Because swExport can also be used for Document and configurable Grid and Graph exports, it is required to set the type attribute to "report" for report exports. See the executable's Help or our Support portal for information about options. 

Example Command Lines:

Using Username and Password:

swExport serverName=sys7 serverPort=1106 serverUsername=admin serverPassword=wagadoff type="report" itemID=x040000000059549B configItem=x3400000000192411 filename="C:\Temp\x040000000059549B_report.pdf"

Using Network Authentication:

swExport serverName=sys7 serverPort=1106 type="report" itemID=x040000000059549B configItem=x3400000000192411 filename="C:\Temp\x040000000059549B_report.pdf"

With parameters:

swExport serverName=sys7 serverPort=1106 type="report" itemID=x040000000062CA1B configItem=x34000000013C29F7 parameter="(p2;x04000000012A91A7)" filename="C:\Work\swExport_x040000000062CA1B_report.pdf"

A new attribute called Opening Method has been added to the Workflow feature meta model: 

The attribute has the following values. If left blank, the default is to Open in Current Tab. 

Current Tab: The view configured for the procedure will be launched for the selected Item in the current tab.

New Tab: The view configured for the procdeure will be launched for the selected item in a new tab where the selected Item will be the TopItem.

The SystemWeaver Notification Server now supports TLS version 1.3. 

For this, the setting In swNotificationServer.ini file should be: 

UseTLS=1_3

As shown in the Test Notification Server: 

The About page in the swExplorer client now has a vertical scrollbar so that the complete list of found extensions can be viewed.

The style of the Charts view has been modernized.

There is now a hovertip over the slices and legend entries that displays the count.

Note: As before, if you do not define a color in a Slice, a default color is used, as in slices 7 and 8 below. Please note that the default colors have changed.

Previous versions required users to resolve mapping version mismatches by clicking two separate buttons—one for the left-side version and one for the right-side version.

With this release, a single Fix Version(s) button has been introduced, allowing users to correct mismatches on both sides simultaneously.

This fixes cases where printing to PDF with bookmarks ended in a "The system cannot find the file specified." error. 

Things to remember when printing with bookmarks: 

• Printing with Bookmarks is only possible using Microsoft Print to PDF. 
• Printing to a network drive is not supported. The output location must be on a local drive.
• While your printing is in progress, the client must remain open.
• Printing entails multiple steps, e.g., data retrieval per the script, formatting, adding bookmarks, and printing, therefore be sure the client is finished before you retrieve and/or open the PDF output file. A PDF file with a size of zero (0) indicates the print job is not completed. This is helpful to keep in mind, especially for very large documents/reports. 

Minor style changes have been made to the display of the Description templates pick-list in both the New issue and New item dialogs. 

The following updates have been made to the view: 

• Section headers, e.g., Properties, Attributes, Description, Parts are now only to the left, and expand collapse buttons are to the right.
• Thirty-forty percent faster loading when there are many attributes, e.g., greater than 10.
• When an attribute is missing in one of the compared versions, it will be indicated with gray in the same way it does for Parts. 
• Each section, i.e., Properties, Attributes, Description, Parts, has its own pane splitter so you can adjust as needed.

• When working with merge conflicts, the Compare and merge conflict menu options are now combined into the same right-click menu.

The XML Export view currently does not display a progress bar dialog for larger exports. In its place is the mouse progress wheel.