It is now possible to configure restrictions in Project workflows resulting in all or specific elements, e.g., properties, attributes, relationships, etc.  of issues becoming read-only when set with a specific Status in the Workflow or for all Statuses. Restrictions are applied by project and effect all members of the project unless specifically configured otherwise.

Example: 

<Workflow>

  <All>

    <Restrictions>

      <Restriction field="*" test="CurrentUser = AssignedTo"/>

      <Restriction field="Attribute:ABAN" test="CurrentUser = AssignedTo"/>

      <Restriction field="Attachments" test="CurrentUser = AssignedTo"/>

      <Restriction field="Relationship:IR" test="CurrentUser = AssignedTo"/>

      <Restriction field="Notes" test="CurrentUser = AssignedTo"/>

    </Restrictions>

  </All>

</Workflow>  

It is now possible to use CurrentUser to filter Issue views where the current user is a value in a User type of attribute. Whereas (single) User and set of User were previously interpreted as strings, they are now correctly interpreted as users.

Example:

<View>

  <Columns>

    <IssueIDColumn align="right"/>

    <NameColumn width="300"/>

  </Columns>

  <Filter>       

     <Satisfies test="CurrentUser in @ATTR"/>

  </Filter>

</View>

The line type, color and thickness of the optional Description Page Width indicator line is now configurable using the same EdgeStyle tag that is used in node graphs to configure edges. 

Example:

<PageWidthIndicators>

  <Editor name="Template1" width="667" default="true">

    <EdgeStyle thickness="10" color="Red" lineType="Solid"/>  

  </Editor>

  <Editor name="Template2" width="687"/>

  <Overview width="667">

    <EdgeStyle thickness="10" color="Red" lineType="Solid"/>

  </Overview>

</PageWidthIndicators>

Result:

If EdgeStyle is not configured, the default will apply (thickness "1", color "Gray", and style "Dash"). 

• Expand and collapse of tree
• Focus remains where you are working when creating features, etc. 
• Ability to rename items directly in the view
• Ability to delete items directly in the view

For ribbon configuration of Item Views that include configItem, it is now possible to use the SID of the configured type along with a defined id instead of the specific xID of a config item version. In this way, button configurations do not need to be updated manually should a new version of a config item be made. When using the configured type SID and defined id, the button will automatically point to the latest version of the config item. Also, when using the Ref id instead of the xID, the configuration will not need to be updated should it be imported into another database.

Example:

A report is configured for items of type CNDE. The report has been given an id value of "ConsistRprt". The resulting Ref id is used in the button configuration. When a new version of the report is made, this Ref id value remains constant (unless the id is manually changed to another valid id value). 

<MergeButton caption="Safety report" image="55">  

   <ItemView name="Report" configItem="CNDE:ConsistRpt"/> 

  <ItemView name="Report" configItem="x3400000000001DE5"/>

</MergeButton>

Note: To utilize this new option for ItemViews, you must first load Item ribbon tab metadata in Configure the explorer. 

For item views and extension views* that allow for multiple configurations, the configured image will now display in the View drop-down as well. 

* The extension must include proper image configuration.

New features of the meta model import now means full support for incremental extensions of a SystemWeaver meta model, through XML import:

• Update the list of default attributes for an existing item type
• Update the formatted text descriptions of types (item/part/attributes)
• Update the detailed information of attribute enumeration types (i.e., the colors and value descriptions)

In addition, the XML generation now supports generation of the format used for the path expression of Computed attributes (i.e. zipped and uuencoded CDATA) from Text format, using the new <AttributePathData> tag, meaning that complete SystemWeaver meta models can be generated by the SystemWeaver XML view, and with the improvements listed above, also imported as complete meta models, with no need for subsequent hands-on modifications.

The Variability Matrix view now includes the Description field. Users can select a part in the view and read its Description while scrolling through the matrix.