P release (PM5 1.1.2034)

Improvements of DOORS adapter

Improved filter for attributes holding multi-valued enumerations

For artifacts extracted from DOORS, it is now possible to filter based on the set literals for enumerations. In addition, we added filters considering unset literals. They can be defined by using the new keywords contains_not and not_in .
Find more details in our help.

YT can now store links in DOORS invasively

It is now possible to store links in DOORS invasively. YT uses DOORS external links to store links to any artifact type that is configured in YT. When storing the information in DOORS, YT considers the lock mode of the target module in DOORS. YT tries „exclusive edit” if „shareable edit” is not configured for the DOORS target module.

Note that these links are not (not yet) navigable – they need to be evaluated by YAKINDU Traceability.

Improvements of PTC Integrity adapter

The name of extracted artifacts is now configurable

Now it is possible to configure the names of artifacts that have been extracted from PTC Integrity.
Here’s an example for an artifact type configuration specifying the name:

map to "Requirement"
    if ("Category" = "User Requirement") 
    name valueOf("ID") + ":" + valueOf("Text")
    { ... }

PTC Integrity adapter now supports string expressions

When configuring PTC Integrity artifacts, string expressions for attribute mapping are supported.

Rhapsody adapter: Improved evaluation of attributes

We improved the evaluation of built-in and custom attributes for Rhapsody model elements. You now can use any attribute for filtering and mapping.

XML and Serna adapters support XML Inclusions

It is now possible to configure XML or Serna Data Accesses to follow include tags. See W3C documentation of XML Inclusions .

Please specify in the configuration whether YT should honor inclusions or not.

The Enterprise Architecture adapter supports now eapx files

The title says it all: The EA adapter supports models in databases, .eap files and .eapx files.

YT checks out licenses more accurately if configuration editor is open

On open configuration editor, YT checked out licenses for all adapter types. The motivation for this behavior was to provide license information to the user pro-actively. We removed the pro-active checkout to get more accurate license usage statistics. The user is now lacking information about available licenses during configuration, but he’s notified directly after he configures an adapter which is not licensed.

Bug Fixes

Made Rational Rhapsody adapter more robust with regards to renamings

YAKINDU Traceability did not always handle renamings of folders containing Rhapsody models correctly:
Imagine you extracted data from a Rhapsody model and – while YT is running – rename one of the folders containing the model.
In some cases, YT reads the data from the updated folder again – without deleting the obsolete data. This resulted in duplicate artifacts in YT.
Now YT correctly updates the extracted data.

Improved synchronization of Rational Rhapsody and YT

In some cases – e.g. when triggering multiple selection propagations from YT to Rhapsody in a row – the selections were not in synch.
We fixed this.

DOORS adapter: Fixed a bug in selection propagation

YT polls DOORS regularly to detect selected requirements in DOORS. The goal is to show in YT the selected requirements and the linked artifacts for this requirement.
Now the „poll” works also for modules with more than 10,000 objects.

DOORS adapter: Enforced the use of configured launcher

In YT, you can configure a command line command to launch DOORS. This is e.g. useful to pass parameters to DOORS.
In some cases when restarting YT, YT did not honor the configured command and started DOORS without parameters. We made this more robust.

DOORS adapter: Discard broken cache files

YAKINDU Traceability caches the data read from DOORS in files. These files may by invalid or broken – e.g. if you shutdown DOORS during data extraction.
In some cases, YT tried to read broken cache files instead of discarding them. Now, YT discards such files and automatically reloads the data.

YT supports „:” (colon) in Artifact Type names

It is possible to specify Artifact Types with colons, e.g. SWE1:Software Requirements . In some cases, queries or reports broke when evaluating the configuration.
This has been fixed.