Visio hangs updating directory cache
Previously, when you changed the view, the selected attributes did not change to match the attributes in the new view. Previously, when you were working in a table in a module, and you inserted a table containing an enumerated attribute, and then moved the inserted table to a different location, there were problems with continuing to edit the module. When you create or edit an enumeration attribute type you can define the order the values are displayed in.
If the value contains a related number, and you assign the values to objects, the objects are no longer sorted according to the related number.
Create a new attribute in a module, edit the attribute, clear the Inherit from parent check box on the Access (Value) tab, and then click OK. Select the Access (Value) tab and select any user or group in the list.
The Remove and Edit buttons are now available and the access rights can be edited.
The problem has been identified and a fix from Microsoft is pending.
In the meantime, IBM has developed a workaround to this problem and implemented it in Rational DOORS version 22.214.171.124.
var microsoft = microsoft
Previously, when you deleted a link on the Links tab of the Object Properties dialog box, and then selected a different link, selecting Follow Link caused the wrong link to be followed. In versions 9.0 to 9.2, customers who had enabled the Leak Track feature in UPHclean had problems starting the Rational DOORS client.Migration - Importing Rational DOORS generated Req IF into Rational DOORS Next Generation, creates all artifacts of Rational DOORS modules at the top level folder of Rational DOORS Next Generation project.When you create linkset in a link module and the source module is open for editing, a warning message is displayed.If the Object Properties dialog box is too small to allow all the tabs to be displayed, a left and right arrow are displayed to allow you to select the tabs. The scroll bar is now in the correct position, allowing you to edit the final lines of text.Previously, when two words in an object were identical, and you searched for that word, if you changed one of the words and clicked Find Next, the word was changed back to its original value. Previously, when you tried to export a module to Microsoft Word in table format, and the module had either the Object Number or Object Level attribute in the view as a column, a DXL error was displayed. Previously, there were issues if the naming attribute of a user contained a comma (the naming attribute is used in the distinguished Name (dn) attribute) that caused problems with users and groups. If a user was deleted from the system, and the user was a member of a group, the reference to the user stayed inside the group.