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.

The theme of the swAdmin2 client user interface (GUI) has been updated to fit our new SystemWeaver color scheme. Additional updates may follow in future releases. 

This fixes an issue with the icon index being off by 1 when using the method:  SWImages.TypeImageIndexToGuiImageIndex

The offset also caused some extensions with a hard-coded icon # to display the incorrect icon.

This is a breaking change if code changes in inhouse developed products were made to fix the offset.  We recommend only using hard-coded numbers for GUI images and to use TypeImageIndexToGuiImageIndex for Type Images.

There is now support in the SystemWeaverExtensionsAPI.dll for accessing issue workflow permissions. 

Permissions here refers to workflow configurations with their definitions of Preconditions, NextStatuses, etc. (Creating a Workflow)

void OpenItemInView(IswItem item, THowToOpenType howToOpenType, string viewName, string configItem = "", 
string configId = "");

The EdgeStyle tag has a new, optional attribute called edgeGrouping. It defines whether or not to merge edges that have the same start and end. Supported values are: "group" or "none". Default, as before, is "none".

If edgeGrouping="group", all edges with this Edgestyle and with the same start and end, will be grouped to one (1) edge. The edge labels of the merged edges will be merged and separated by a new line.

Examples:

edgeGrouping="none" or edgeGrouping not used

edgeGrouping="group"

It is now possible to manually configure the ID for ports in a configurable graph in the same way as one can for edges and nodes using attributes id and objects. This provides a way to create a dummy port, i.e., a port that does not represent an object in the database. More details can be found in the SystemWeaver Script Language Reference Manual in the application Help.

Examples:

<OutPort id="id-1"/>

<OutPort id="#{? 'dummy_' + Handle}"/>

<Options>

 <HideUnconnectedPorts value="true"/>

 <HidePortLabels value="true"/>

 <HideEdgeLabels value="true"/>

 <DelegateImplicitPorts value="true"/>

 <MergeNodesWithIdenticalID value="true"/>

<DelegateImplicitPorts value=""/> defines if the implicit ports are always delegated. By default this option is "false", i.e., that ports with the same connectionIDs are all connected together, no matter if they are under the same parent or not.

If the option is set to "true", ports are only connected to other ports under the same parent. If a child port wants to send or receive a port from cousin ports, this communication should go through, and be delegated through, the parents.

<HideUnconnectedPorts value=""/> can be used to hide unconnected ports in the graph when set to "true". The default, or "false", is to display them.

<HidePortLabels value=""/> can be used to hide port labels in the graph when set to "true". The default, or "false", is to display them.

<HideEdgeLabels value=""/> can be used to hide edge labels in the graph when set to "true". The default, or "false", is to display them.

<MergeNodesWithIdenticalID value=""/> merges nodes with identical IDs in the graph when set to "true". The default, or "false", is to not merge them. Note that if a node appears under different parent nodes, it will not be merged.

The following operations are now supported directly in Grids when configured using Actions.

Set part name

When the Part Name option is enabled for a part type, it is now possible to add or update the part name instead of the default item name when using Actions.  <Part> has a new name attribute. When part name is enabled, the name attribute uses the standard way of parsing text so that it supports path queries.  Example:

<Part id="P" name="#{? $port.DefObj/ARDE.Select(Name).Join('')}" 
owner="ItemSW" match="$port"/>

New note

With the implementation of note creation using the Script Language, users can now work with item and issue Notes in a grid when configured using Actions. To enable this, a new data type "Description" has been introduced.  Example:

<Action id="MyAction">

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

 <Parameter name="noteDesc" as="Description"/>

 <Item id="A" match="$currentItem">

  <Note sid="NND" description="$noteDesc"/>

  <Note sid="NND" value="TextText...."/>

  <Note sid="NND" value="#{? $currentItem.Name + 'TextText..'}"/>

 </Item>

</Action>

Select library

Previously, when creating items in the background as a result of an operation, the Library was hard-coded. Users can now choose which Library to add the items to using the Select Library dialog. A pre-selected value can be configured. Example:

<DialogSelectLibrary defaultValue="$Lib"/>

Select item version

With the implementation of Select Item Version Dialog  using the Script Language,  users can now change an item version to any version using action. Example:

<ActionBinding actionId="DoIt" caption="Change the version">

  <WithParam name="Req">

    <DialogSelectItemVersion/>

  </WithParam>

</ActionBinding>

Presets for issue creation

Some properties, e.g., Type, Name, Status, AssignedTo, Iteration,.. etc., in the New Issue dialog can now be preset for users when they create issues. Example:

<Variable name="currentItem" as="Item" select="."/>

<ActionBinding actionId="AddIssue" caption="Add Issue from Dialog">

 <WithParam name="issue">

  <DialogCreateIssue project="AC1" issueType="Issue" name="#{? 
'Issue for' + $currentItem.Name}" status="Closed" assignedTo="#{? CurrentUser}" 
Iteration="Backlog"/>

 </WithParam>

</ActionBinding>

Part matching for part with multiplicity = List

The owner attribute is no longer required when using match for updating parts.

Part matching for part with multiplicity = Single

The owner attribute is still required, but the match will be done automatically based on partType attribute. So no need to use match attribute.

Part removing for part with multiplicity = Single

The remove attribute can be used to remove a part with multiplicity= Single. Note that together with the remove attribute, it is still require to use partType, owner, and defObj attributes in order to be able to remove a part with multiplicity= Single.

Set description for an item and issue 

A new, optional description attribute has been added to <Item> and <Issue> tags to support adding a description (formatted text) to an issue/item from another item, issue, or note. Example:

<Action id="DoIt">

  <Parameter name="desc" as="Description"/>

  <Issue description="$desc"/>

</Action>

Clone an Issue

Using the optional clone attribute, it is now possible to clone an issue.  When cloning an issue, the cloned issue will get its type, properties (e.g., status, iteration, assigned to, etc.), description, attributes, name, attachments, and project from the original issue. Issue's ObjRef (relationships to items and issues) will not be cloned automatically. If needed, they shall be created manually. To clone into another project, i.e., not the same project as original issue, use the project attribute. Example:

<Action id="cloneIssue">

   <Parameter name="issue" as="Issue"/>

   <Issue clone="$issue"/>

</Action>

Clone an Item

Using the optional clone attribute, it is now possible to clone an item. When cloning an item, the cloned item will get its type, description, attributes, name, and library from the original item. Item's parts will not be automatically cloned. If needed, parts should be created manually. To clone into another library, i.e., not the same library as original item, use the lib attribute.  Example of cloning an item to the same library as the original Item:

<Action id="cloneItem">

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

   <Item clone="$item"/>

Nested menus

It's now possible to configure nested menus in grids using Action. Menus are generated based on the caption specified in <Action> or/and <ActionBinding>, adding (->) in the caption attribute will automatically create a nested menus.  Example Structural menu:

<ActionBinding caption="Update (->) status (->) Done">

<Action caption="Update (->) status (->) ToDo">

Result:

Deactivate menu options

Menu option activation can now be conditioned, using two new attributes, enabled and disabledTooltip, added to ActionBinding.

<ActionBinding actionId="DoIt" caption="Add Req" enabled="$req.Select(@TTT) = ['Yellow']" disabledTooltip=
"This option is only available for requirements which are not Yellow">

Result:

DialogSelectItem recommendations

There is now support for configuring recommendations for adding parts. Example:

<DialogSelectItems itemType="ARSI" partType="DSIN" 
owner="$requirement" pathToOwner="container;requirement"/>

Check if RowObject is empty (null)

It is now possible to check if the value of a RowObject is null. This can be used in both <Action> and <ActionBinding>.

Example: ActionBinding

<ActionBinding actionId="DoIt1" caption="Add Signal 1" enabled="$requirement != []">

Example: Action 

<Action id="DoIt">

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

...

  <Choose>

    <When test="$requirement = []">

 .....

    </When>

  </Choose>

</Action> 

Any applicable Issue Workflow restrictions or pre-conditions that are part of a specific Workflow are now applied when working with Issues directly in a configured grid. For example, if you attempt to set a particular Status for an issue using the grid, and the logic in the Workflow does not allow it, the configured message will inform the user. Likewise, if you configure an <Action> to create an issue, there is no need to add the default status in your <Action> as it will be set automatically by checking the workflow configuration.  

Example of a status precondition thrown in grid: 

This applies to the following editable (readOnly="false") columns:

• <IssueAttributeColumn>
• <AssignedToColumn>
• <IssueStatusColumn>
• <NameColumn>
• <DescriptionColumn>

When using DialogSelectItem in ActionBindings for an abstract item type, the Select type dialog will now appear directly, and present non-abstract sub-types from which users can choose. 

Previously, the Open item of type Abstract ... dialog appeared and users needed to click on Select item type... to obtain the Select type dialog.

<Grid>

 <Options>

  <CellAutoHeight/>

 </Options>

 <Columns>

  <NameColumn readOnly="false" width="150" caption="Issue name"/>

  <DescriptionColumn readOnly="false" caption="Issue description" width="400"/>

 </Columns>

 <ForEach select="/issueref::IR">

  <Row/>

 </ForEach>

</Grid>

The Deprecated status (IsDeprecated) for Attributes is now displayed in the Metamodel Diff tool and included when exporting this list to Excel. 

The Deprecated status for Attributes is now included in the XML export and import of the meta model. This applies to all meta model XML Export/Import options: 

swArchitect

• XML Export/Import
• Metamodel Cutter

swExplorer

• XML Export/Import when including metadata with data export

Exported XML: 

<AttributeType sid="2APH">

 <Name>Comment</Name>

 <Info>Calibration parameters</Info>

 <DataType>adtString</DataType>

 <DataDimension>admSingle</DataDimension>

 <Range/>

 <EnumTypes/>

 <Format>250</Format>

 <Description>

  <Binary><![CDATA[AQAACNgEAAHicrZLfa8Idpt6qMK+8lJpIGnX9E/dfrWnp=]]></Binary>

 </Description>

 <IsRestricted>False</IsRestricted>

 <IsDeprecated>True</IsDeprecated>

 <DefaultValue/>

 <EmptyValueIsValid>True</EmptyValueIsValid>

It is now possible to use <Depends> to connect parameters of type String, Boolean and Integer. Until now, the use was supported for parameters of type Item.

The <Depends> tag defines a dependency of a Parameter to another Parameter, with a specified name. For example, a selection of a specific value in one parameter list can trigger the presentation of specific values in a second parameter. Example: 

<Report>

    <Parameters>

      <Parameter caption="1st Selection" as="String" name="p1" 
defaultValue=" 'Yes'">

            <Values>

                <ForEach select="['Yes','No']">

                    <AddValue/>

                </ForEach>

            </Values>

        </Parameter>

        <Parameter caption="2nd Selection" name="p2" defaultValue=" 'Y1'">

            <Log>---- #{? $p1}</Log>

            <Depends name="p1"/>

            <Values>

                <Choose>

                    <When test="$p1 = 'Yes'">

                        <ForEach select="['Y1', 'Y2', 'Y3']">

                            <AddValue/>

                        </ForEach>

                    </When>

                    <When test="$p1 = 'No'">

                        <ForEach select="['N1', 'N2', 'N3']">

                            <AddValue/>

                        </ForEach>

                    </When>

                </Choose>

            </Values>

      </Parameter>

    </Parameters>

With this release, we introduce two new parameter types: checkbox and text box.

A new, optional type attribute is used to specify checkbox or text box. As before, the default type is combobox. See the application Help for more information.

It is now possible to input a String and have it split into separate characters. This can be used, e.g., when you have filtered a string and then want to remove any type of character.

It could also be used when making attribute type definitions for ReqIF where the attribute type name there shall only contain alphanumerical characters. 

String.ToChar -> [Character]

It is now possible to use <DescriptionColumn> for Issue Notes and item Note. 

Example Issue notes

<Grid>

 <Options>

  <CellAutoHeight/>

 </Options>

 <Columns>

  <TextColumn caption="Changes" rowObject="issueNote">

   #{?.}

  </TextColumn>

  <DescriptionColumn width="auto" caption="Issue Note" rowObject="issueNote"/>

 </Columns>

 <ForEachIssueInObj type="IR">

  <ForEachNote type="NISS">

   <RowObject name="issueNote">

    <Row/>

   </RowObject>

  </ForEachNote>

 </ForEachIssueInObj>

</Grid>

<Grid>

 <Options>

  <CellAutoHeight/>

 </Options>

 <Columns>

  <DescriptionColumn id="itemNote" caption="Note" objectName="itemNote" 
readOnly="false"/>

 </Columns>

 <ForEachNote type="NND">

  <RowObject name="itemNote">

   <Row>

   </Row>

  </RowObject>

 </ForEachNote>

</Grid>

In Grids, Item Notes can be edited using the readOnly="false" attribute setting in DescriptionColumn. Issue Notes can never be edited.

This release includes the first version of a Workflow process meta model and feature which can guide users through a work process consisting of activities and procedures. The workflow will inform the users which activities need to be done to fulfill a process, and also lets them know how the activities can be done in SystemWeaver (procedures). The user can then select a context in which they want to perform the activity, thereafter the user will be taken to the correct context and the appropriate views to perform the procedure will automatically load. Example Process data: 

It's ideal to use for a particular domain, e.g., Cybersecurity, Adaptive Autosar, or for any other use case you have as our Workflow meta model is generic. The process can also include descriptions of procedures done outside of SystemWeaver. Procedures can be configured to guide users to the right context and the proper view(s) to use. This is a first version of the feature. 

Configuration

Workflow is a Feature configured via Configure the explorer. 

When configured and activated, the Workflow guide loads just below the structure tree via the Overview drop-down menu: 

More details about the Workflow Process meta model and how to configure and use the feature can be found in the application Help.

This fixes a misleading "Invalid def obj type: XXXX in part of type YYYY" warning displayed when exporting, when, in fact, the def obj is correct. Now, the correct warning is displayed during XML import.

There is a new option in the swServer.ini for the main server called AllowLocalCache. Supported values are True or False. True is the system default. If AllowLocalCache is set to False, mirror servers connecting to the main server can only run using in-memory cache (CacheInMemory=True). 

As always, we do recommend the use of a cache file for mirror servers. CacheInMemory is a suitable option for smaller databases and/or QA environments only. 

When upgrading to R42, both main and mirror servers must be updated. 

When cloning items in a structure that includes parts with RefObj(s) (Referenced Object) to a part or item, there are now options to clone, ignore, or include RefObj(s) in the resulting clone. If no RefObj Option selection is made, ref objs are ignored by default, as before. 

When you make your selections for RefObj, they are displayed in a new RefObj option column. The RefObj's name is also displayed. 

A new attribute called actionRefObj has been added to the Clone item view configuration. 

actionRefObj specifies the action for RefObj according to the part type. Supported values are include, clone and ignore.

• 'include' for RefObj means that the original object (Item or Part) included (as-is) in the cloned structure, without being cloned.
• 'clone' for RefObj means that the original item or part will in fact be cloned.
• 'ignore' for RefObj means that the original object (Item or Part) will be ignored.

If actionRefObj is not specified, the RefObj will be ignored by default, as before. 

<CloneParts>

  <Part sid="6PRR" action="clone" actionRefObj="clone" 
traceparttype="QQQ">

       <Include>@ABAN="include"</Include>

    </Part>  

When working in Edit mode with manual layout, users will now receive a Proceed dialog should they mistakenly double-click on a node in the graph which redirects to the node's item in the structure tree. This action previously resulted in losing any unsaved manual layout changes. 

This fixes many cases of ports overlapping making it difficult to read and follow the connections. 

Before:

After: 

After upgrade to Bagaregården (R42): If you are currently using the system default layout and have overlapping ports, consider, using the Relayout option in Edit mode to potentially lessen overlapping ports.  Use Save layout to save the changes. 

Note: The logic takes into account any maxHeight settings for Shapes.

This fixes the displayed color of excess data size in the Image Editor.

With this release, we are introducing support for exporting a grid to MS Excel via command line using the swExport tool. Using this application, you can, e.g., implement your own program that utilizes the swExport.exe based on your organization's needs.

This tool's grid export functionality has no required meta model, or item structure. It is suitable for all configurable grid use cases, and provides support for specifying parameters. 

Because swExport can now be used for both document and grid export, it is important to set the type attribute to "grid" for grid exports. See the Support Portal for more details.

Example Command Lines

Using Username and Password:

swExport serverName=sys7 serverPort=1345 serverUserName=john.doe serverPassword=test type="grid" itemID=x04000000000C5AD4 configItem=BIVD:ECU filename="C:\Work\ECU_allocation.xlsx"

swExport serverName=sys7 serverPort=1345 type="grid" itemID=x04000000000C5AD4 configItem=BIVD:ECU filename="C:\Work\ECU_allocation.xlsx"

With parameters:

swExport serverName=sys7 serverPort=1345 type=grid itemID=x04000000000A76C1 configItem=SREL:Release_Summary parameter="(p1;x0400000000051B65)" parameter="(p2;'Iteration')" parameter="(p3; true)"  filename="C:\temp\release_summary.xlsx“

Known Behavior 

• Export is of plain text only, just as it is with all Export to Excel operations in the client.

There is now a Copy issue button in the Issue editor. Clicking the button puts the issue's SystemWeaver URL in your clipboard. This is useful to use when you want to copy the URL of an issue that is not displayed in the issue view that you currently have loaded. 

You can then paste the URL as needed.

The following improvements have been made to the Snapshot view. 

It is now possible to edit item Descriptions by double-clicking on the Description to open the editor. 

In addition, Description scrollbars have been removed, and the Description will auto-size based on the data.

The view now also includes two new options - Lock and Refresh. 

• Lock enables you to lock the view on the selected item. 
• Refresh will refresh the contents of the view.

In addition, any images included in an item Description will now appear in the view. 

Note: There is no support for viewing values for RVF, Calcuated, Custom, Array of External Reference, and XML type attributes at this time.

The Architectural System Signal extension has been updated to support multiple senders of the same signal allowing for platform architecture design: