Serena® Dimensions® CM 10.1.2 Release Notes
This file contains information about new features in Serena Dimensions CM
It also contains important information about defects corrected in this version
of Dimensions CM. See the relevant sections below.
This release includes all the fixes that were present in the 10.1.1.1 patch
release to Serena Dimensions CM 10.1.1.
See the Serena Dimensions CM 10.1.1 Readme and Release Notes for information
about the Dimensions CM 10.1.1 release.
To view defects corrected in previous releases, visit the Serena Support Web site at http://support.serena.com.
For late-breaking information, see the accompanying Readme HTML document.
Table of Contents
1.0 Startup Documents
The following startup documents are available from the Serena
- Upgrading to Dimensions CM 10.1.2
- Introduction to Serena Dimensions CM
- Serena Dimensions CM Installation Guide
- Serena Dimensions Installation Quick Start Guide
- Roadmap file
Return to Contents
2.0 What's New in Dimensions CM 10.1.2
2.1 General Usability Enhancements
CM Rules Selectable by Project
There is now the option to choose how CM Rules take effect for a specific
project. The default option for new projects of a particular type can be set in the Administration Console
| Object Type Definitions | CM Rules section. This option can also be set
for a specific project in the web client and desktop client. This means that you
can choose one of the
following options for a project:
- Items in the project will obey the CM rules that are defined for their
specific item types.
- Items in the project will behave as if the CM rules for all the item types are
enabled, regardless of whether they are specifically enabled in the
- Items in the project will behave as if the CM rules for all the item types are
disabled, regardless of whether they are specifically enabled in the
Merging Items on Check In in the Desktop Client
Dimensions CM can now be configured to determine whether an item has any leaf revisions that need to be merged, and prompt the user
with a number of options when they are checking in or updating an item in the
desktop client and
Dimensions CM has detected a conflict. The user will have a choice of actions to
take, including to merge the
work file with the version in the repository (invoking the file merge tool) or to check
their file in as the tip revision. For
full details, see the Dimensions CM User's Guide.
The option to perform this check can be set on the Dimensions CM server using
the parameter (DM_DISABLE_BRANCH_CHECKINS)
in the dm.cfg file. Setting this option will force
all users to merge their changes with the tip revision in the repository.
If this has not been set for the server, users of the desktop client can also choose
to set this option in the Preferences dialog.
Default Design Part
A Dimensions CM user can now set a default design part for a project. This is used as the default owning design part for new
items, requests, design parts, and baselines that are created by that user when working in the context of that project.
This is available in:
- Desktop client
- Web client
- Synchronize Wizard
- Windows Explorer Integration
Enhancements to Desktop Client
The following enhancements have been made to the desktop client:
- Importing a Request into a Project: A new wizard is available in the desktop client enabling the user to select a Request (and optionally, its child requests) and import them into a Project. Dimensions CM will detect any item revisions that need to be merged and prompt the user for the action required.
- Resolving Merge Conflicts for a Project Folder: You can now perform Resolve Merge Conflicts for the items in a folder within a project and optionally, for all its subfolders. You can also perform Resolve Merge Conflicts for a Request.
- The Merge Item dialog box has been replaced with a more user-friendly wizard.
- You can now compare the contents of item files from the History dialog.
- An icon has been added to indicate where you can click the column heading to select all the rows in a grid display.
- You can open the Build Administration console from the Tools menu.
- The Find dialog for requests now enables you to specify projects to which the requests are related (or explicitly not related).
- There is a text field in the tool bar of grid displays that provides a quick way of filtering the list of objects to show only those that contain a specified string in a chosen column.
- The following dialog windows can now be resized:
- Resolve Merge Conflicts
- Merge Item Revisions
- Resolve Project Merge Conflicts
- Find Baseline, Customer, Design Part, Item and Release dialogs
See the Dimensions CM User's Guide for full details.
Enhancements to Synchronize Wizard
- It is now possible to select which items are synchronized according to
change type: additions, deletions, modifications, or moves and renames. You
can individually select which of these change types to include when
performing an upload, download, or synchronization.
- Two toolbar buttons have been added to the item changes tree, and are
selected by default:
Hide Unchanged. When this is selected, files that are calculated to be ‘unchanged’ are not shown in the display.
- Hide Ignored. When this is selected, files and folders that have a resolution of ‘Ignored’ are not shown in the display.
- A secondary sub-progress bar has been added to the synchronizing page to display the progress of the Dimensions
CM Download command when it is processing the bulk-fetching of items.
- There are now browse buttons to enable you to select the default design part and the working request.
See the Dimensions CM User's Guide for full details.
There is now an option in the desktop client and web client to easily print a request including its expanded browse template.
Purging Library Cache Areas
The new PLCA command enables you to remove all files from a library cache area. For details, see the Command-Line Reference.
SCWS Command /USERS qualifier
The SCWS command now accepts a /USERS= qualifier.
Using this option requires the privilege ADMIN_USERMAN
This new qualifier will accept both user and group ids. For example, to change the project settings for all users defined in
the group "uk_users":
scws repx:repx4 /users=(uk_users) -
/dir="d:\temp\user4" /USER_BRANCH="4" -
/LIBRARY_CACHE_AREA=lca4 /PART=REPX:P4 -
This example will expand the group "uk_users" into its constituent user ids and iterate through
those user ids updating the project settings for each in turn.
Note that if, at a later date, a new user is added to the group "uk_users", this new user will not inherit the
project settings defined above. You would need to issue a specific SCWS command for the new user
to update their project settings accordingly. For details, see the Command-Line Reference.
Enhancements to SET Command
There is a new option available for the SET command:
SET EOL WINDOWS|UNIX|DEFAULT|UNCHANGED|SHOW
Sets or displays the end-of-line handling mode for the current connection that will be used when getting text files over
the current connection.
- SET EOL WINDOWS ensures that gotten text files follow the Windows convention for line termination, i.e. each line is terminated with a CR/LF character pair, regardless of the client operating system.
- SET EOL UNIX ensures that gotten text files follow the UNIX convention for line termination, i.e. each line is terminated with a single LF character, regardless of the client operating system.
- SET EOL DEFAULT restores the default Dimensions end-of-line handling mode, i.e. text files gotten to a Windows node will have each line terminated with a CR/LF pair, while text files gotten to a UNIX node will have each line terminated with a single LF character.
- SET EOL UNCHANGED ensures that text files are gotten as-is from the item library without any end-of-line processing at all.
- SET EOL SHOW displays the current end-of-line handling mode.
Also, all Dimensions commands that result in files being gotten from item libraries (DOWNLOAD, ECDI, EI, FBI, FCDI, FI, FWI, REL) have been enhanced with a
/EOL qualifier that takes one of the following values -
WINDOWS, UNIX, DEFAULT, UNCHANGED - and allows the user to specify the end-of-line mode for the duration of the command only.
Note that these changes are not yet documented in the Command-Line Reference.
2.2 General Performance Improvements
WAN Performance Improvements
There have been a number of performance enhancements when using Dimensions CM over a WAN (Wide Area Network):
- Library Cache processing has been improved. Transfers to the library cache are now deferred to a memory cache for downloads and then performed in bulk when a threshold
limit is reached or there are no more items to process.
- The performance of the Eclipse plugin when adding a project to Dimensions CM has been improved.
- The performance of the Eclipse plugin when displaying request attributes has been improved.
- Check in and check out performance has been improved.
- The Synchronize Wizard now uses the Upload and Download commands instead of multiple fetching and updating of files to improve performance.
Upload and Download Commands
The performance when using the Upload and Download commands has been improved
by only querying the privileges Download Files from Project, Upload
Files into Project and Download Files from Baseline once in a
Mainframe Performance Improvement
General mainframe performance has been improved through the addition of a metadata server and the caching of commonly used DD names. For further details, see the Dimensions for z/OS User’s and Administrator's
OS Password Change in Dimensions CM Clients
In addition to Windows servers, users can now also change their password from Dimensions CM Clients for UNIX servers, provided that LDAP is enabled on the server.
Support for PAM
For Solaris servers, Dimensions CM now provides support for user authentication via a Pluggable Authentication Module (PAM):
- Connections from a client user interface where authentication is via PAM.
- Connections from a client user interface to a remote Dimensions CM node where authentication is via PAM.
- The creation and use of item libraries on a node where authentication is via PAM.
Authentication is via username and password only. This connection method is available from all supported Dimensions CM Clients to a supported Solaris server.
For further details, see the Administrator's Guide.
Prior to this release, each Dimensions CM work or deployment area required a set of credentials (operating-system user-id and
password) stored against it to be used for any operations performed against that area. When a password
expired or changed with respect to a given user-id, the user had to search out the areas using that
set of credentials and update them appropriately.
To facilitate managing credential sets, user-id and password information is now
available as a separately managed object which can maintained centrally and
assigned out as needed.
The following commands are available to manage credential sets:
- CCS – Create Credential Set
- DCS – Delete Credential Set
- UCS – Update Credential Set
- LCS – List Credential Sets for Current User
For further details, see the Administrator's Guide.
Using dmcli to connect to remote UNIX Dimensions CM servers without specifying a password
Dimensions CM now allows dmcli to use rhosts(5) authentication when connecting to a remote server. Because this method of authentication is considered too insecure for use in most
environments, the feature must be explicitly enabled by specifying:
in the dm.cfg file on the server. Furthermore, the client environment must have the same variable defined, either as an
environment variable or in the dm.cfg file.
Please note the following constraints:
- Only UNIX servers are supported by this feature.
- The user must have an operating system account on the Dimensions CM server. LDAP authentication is not supported by this mechanism.
- The user name on the client system must match the user name on the Dimensions
- The user must create a .rhosts file in their home directory on the server. This file must have mode 0600.
- This feature cannot be used with named connections. Instead, the -host option to dmcli must be used to specify the Dimensions
2.4 Build and Make
The following features have been added to Dimensions Build version 10.1.2.
For further details, see the Dimensions CM Build Tools User's Guide.
- The Dimensions CM client build panels now have options to automatically download and, optionally, apply the current system date/time to files when performing work area builds.
- To simplify maintenance of mainframe build configurations, support for wildcards has been added.
- Source rules used in build configurations can now be scoped by item format/build type. This will provide a more granular selection of items with a common file extension and is especially useful in build configurations with
- The impacted targets/build targets list has been extended to include derived items discovered during the build. In the
past, only targets in the build configuration were displayed.
- The output collection logic has been extended to relate build targets to the same design part of the corresponding
source item in certain situations.
- For build configurations with wildcards, build steps can be ordered numerically to control what order build steps will get executed.
- Support for using SVA and MVA attributes as build options has been added.
- When you create a build area you can specify a credential set instead of a user ID. For details about credential sets see the
Dimensions CM Administrators Guide.
- The following build-related commands have been updated, or are new (for full detail see the Command-Line Reference):
- BLD: new qualifiers: /TYPE, /SRC_CHANGE_DOC_IDS, /SRC_FILES,
/SRC_ITEMS, /[NO]CANCEL_TRAVERSE, /[NO]POPULATE, /[NO]TOUCH]
- BLDB: new qualifier: /[NO]TOUCH
- RABC (Relate Area to Build Configuration): new command that relates a build area to a build configuration.
- ECFG: (Extract (Check Out) Build Configuration): new command that checks out a build configuration to the current user ID.
- RCFG: (Return (Check In) Build Configuration): new command that checks-in all the changes to a build configuration.
- IMPORT: new command that imports a new build configuration to Dimensions from an XML file.
- EXPORT: new command that exports a build configuration to an XML file.
The following build options have been added to the Build Request, Build Item, Build Baseline, and Build Project panels:
- Download: If you have selected a work area as the target build area, you can transfer files to the area before the build is executed.
- Apply system time/date: If you have selected the download option (see above) you can apply the system date/time to each file being transferred.
For further details, see the Dimensions for z/OS User's and Administrator's
Dimensions CM Make
Dimensions CM Make now provides the ability to generate an XML bill-of-materials suitable for use with Dimensions Builder.
In this mode, the Dimensions CM database is not accessed directly by Make - Builder is responsible for populating the build area before the build and collecting build outputs once the build is complete.
To use this feature, specify the --xml-bom[=bom-file-name] option on the command line for dm_make, dm_nmake or adg. If no bom-file-name is specified, the default is
New Third-Party Integrations
The following integrations are now supported:
- Remedy 7
- RAD 7
- CruiseControl .Net
Selection Wizards Added to Visual Studio
There are Selection wizards now available in the Visual Studio integration to enable you to select objects in certain situations. These are available for Items, Requests, Baselines, and Design Parts.
For details, see the Dimensions CM for Visual Studio User's Guide.
Historical Transitions Support in TeamTrack Integration
There is now support for historical transitions in the TeamTrack Dimensions integration.
When multiple transitions have occurred between runs of the synchronization, the
history of the intermediate transitions is applied in Dimensions CM.
2.6 Supported Platforms
The Dimensions CM 10.1.2 Agent for Red Hat Linux ES 4.0 on 32-bit platforms
can also be installed on following newly supported 64-bit platform (Agent
- Red Hat Linux 4 AS (64-bit) on Intel (EMT 64)
- This is not supported for use with 64-bit Intel Itanium chip architecture.
- As this is a patch release to Dimensions CM 10.1.1.x, you will need to
install the Dimensions CM 10.1.1 Agent first.
2.7 Guide for Optimizing WAN Development
A new user guide is being added to the documentation set. It is called Dimensions
CM Optimizing WAN Development and is available from the
Serena Support Web site. This guide contains recommendations
and suggestions for optimizing the use and performance of Dimensions CM over a
Wide Area Network.
Return to Contents
3.0 What Was New in Dimensions CM 10.1.1.1
3.1 Enhancement to Synchronize Wizard
The Options fields for request and design part in the Synchronize Wizard now
have a browse button to enable you to select the required object. Clicking the
browse button displays a selection wizard. The first page enables you to enter
selection criteria for the request or design part. The second page displays the
matching list, from which you can select a request or design part with which to
populate the field.
3.2 Requirement Titles now Displayed in Desktop and Web Client
The Dimension CM desktop and web clients now display the "Title" attribute for Dimensions RM Requirements.
Note: If using Dimensions RM requirements, all Dimensions Clients and Servers must be updated with this patch.
3.3 Performance Enhancements in the Desktop Client
There have been a number of performance enhancements when using the
desktop client over a WAN (Wide Area Network).
- Faster Delegation of Items and Requests in the desktop client and VS .Net when running over a WAN.
- Faster display of the parts and directory displays when running the
desktop client over a WAN.
- 112746: Performance improved when displaying a large number of attributes in the desktop client.
- 112749: Performance improved when scrolling large lists of requests.
4.0 What's Fixed in Dimensions CM 10.1.2
4.1 Administration Console
73202: When exporting a request template, the browse dialog did not enable the user to save it in the required directory unless the file already existed.
74171: When editing an attribute update rule for a request, and using the Edit
button rather than the hyperlink, the
attribute name was not being displayed.
105847: The wording in tooltips and field prompts has been improved in the User
Interface Profile Assignments.
114468: You can now change the network node of a deployment area in the Administration Console after it has been associated with a build configuration.
123803: In the Mail Events function of the Administration Console, the
event name 'Item deleted from Project' had an incorrect description.
126828: It was not possible to changing an existing attribute update rule's "Required when actioned
to state" checkbox.
127630: Creating stage names which began with a common prefix in the Global Stage Lifecycle
caused problems in deployment.
110643: When the user had removed all the stages and transitions from the Global Stage Lifecycle it was not subsequently possible to add any.
4.2 General Client Issues
- 114100: The default setting for new project types is now set to Manual Deployment, which is the recommended method.
- 124113: Mandatory attribute values that were entered when creating an item were being ignored.
- 55208: The MIT command was producing an error "Item spec <item id> is already used" when auto-generating item IDs.
- 55228: The MIT command was failing when the library filename already existed for an item of the same type.
- 55312: It was possible to delete a design part that had roles assigned, and subsequently be unable to delete the role assignment.
- 55400: The MIT command was producing an error: "Cannot open file <path of the file> No such file …" under certain circumstances.
- 73984: The FIF command was not always finding files successfully when using the
- 75886: The Project Merge tool was incorrectly showing a folder as being deleted when it existed in the derivative folder.
- 111059: After creating a merged baseline the resulting table contained duplicate item entries.
- 112179: There was a problem where a certain upload rule was not being found when adding an item.
- 113365: There was an error occurring when creating a delta release under certain circumstances.
- 114187: The full user name is now displayed when browsing requests.
- 116491: An error "KM-Dim9: Error: ORA-00001: Unique constraint (.CM_DBFILES_K1) violated" was occurring when two users were updating a request at the same time.
- 123005: When checking out an item where the file already existed as
read only, the file was not set to writeable when the item type option was set
to check out a file with the same revision number.
- 123794: Item header substitution was not working for user-defined attributes.
- 124410: It was possible to create an item with values that did not exist in the valid set for those attributes.
- 124984: You can now prime a new request from a closed request if the relationship between the requests is "Info".
- 71199: Dimensions CM now automatically checks whether any revision of an item already has an “in response to” relationship with the request that is about to be associated with a new revision of that item. If this is the case, it will automatically set the current revision to be "affected" and the new revision to be "in response
to" that request.
- 71599: Items that had been actioned to the last state in the lifecycle were still showing in the user's inbox.
- 72052: Dimensions CM was not handling group privileges on UNIX platforms correctly when getting items.
- 79231: The Upload command was uploading items onto the main branch in the project instead of
using the correct branch according to their pedigrees.
- 80502: The RPCP command was failing with parameters
/SECTION=all and /DETAIL if there are item lifecycles with state transitions from a state back to the same state.
- 111165/111166: There was a performance problem when populating an area.
- 113391: When performing a merge project or
MWS command with the /REPORT option, the message in the emailed report contained the text "PM_SHORT_NAME_TEXT" instead of "Dimensions CM"
- 114356: The DLGC (Delegate Request) command performed from dmcli was failing to execute.
- 115191: Creating a baseline with the CBL command resulted in mandatory attributes being ignored for the resulting baseline.
- 122749: There were performance and stability issues with the Project Merge tool
- 122834: Dimensions Upload and Merge functions were not supporting Windows case-insensitivity in folder names.
- 123005: If you checked out an item where the file already existed on disk as read only, the file was not set to writeable
if the option "Don't Force new Revision Number on Checkin" was set for the item type,
- 123123: Using the PCSSC command to get a specified filename was resulting in an an error.
- 125250: Creating a user with an apostrophe in the name was failing with an error saying that the quoted string was not properly terminated.
- 126795: There was a problem under certain conditions where getting a file using
substitution variables was resulting in an extra CR/LF character being appended to the end of the file.
- 126797: There was a problem when using a work area on a Dimensions CM agent where filenames containing accented characters were not being handled and displayed correctly.
- 127163: Uploading a modified file with the UPLOAD command was resulting in the file being ignored because the metadata had recorded that it was not the latest revision in the Project.
- 129069: The functions relating to renaming and removing items in a project have been changed so that they do not affect files in projects and deployment areas other than DEV.
- 129543: An error "Failed: triangle hook not installed" was occurring when getting an item from the Windows Explorer integration.
4.3 Desktop Client
51199: Column sorting was not working in the related items pane of the request content window.
51215: When selecting a request and selecting the Print menu option, the client was actually printing the Output Console instead.
51226:When Actioning multiple items of the same type, the pull down list in the Action dialog contained available states for other item types.
55166: There was a problem in the New Item dialog where the selection of a design part was not working on subsequent use of the dialog.
55447: After the user had selected the option to hide the console window, the client did not remember this when it was subsequently
55565: Using the Alt key to drag and drop an object in the Unrelated tab in the Relate dialog box was
70586: When clicking on the name in a design part tree, and then clicking in another place, it was possible to unintentionally change the part ID.
72173: The option to take roles from all affected design parts was not working for a
73765: In the Find Request dialog, sorting the list of related items caused the list to be corrupted.
96969: You can now sort the items in a project view that has been displayed
as a result of selecting "Open in New Window".
103936/112220: Setting the DMDB variable and then starting the desktop client by executing the pcwin executable resulted in the client
105356: You can now drag and drop a request from the pending request window onto the Build Item dialog box.
105382: In the Item Query dialog box, long item type names were hiding the adjacent check box.
106232: The Find dialog for a request was displaying all the revisions of an item, instead of only the related revision.
106405: A default working branch that was set for a project in the web client was not being
displayed in the desktop client.
106459: There were some issues with the displaying of tabs and windows in the desktop client.
106677: Requests that had been related to a project after they were created were not being displayed in the
Request catalog for the current project.
106848: The Merge Item Revisions list box now has a horizontal scrolling bar.
107790: The Print button for printing requests was printing the contents of the console window.
108076: The Delegate Request dialog now allows you to sort the users by User
108220: There was an error occurring when creating a duplicate request attachment and then attempting to delete it.
109160: An error occurred checking out an item when the user name contained an apostrophe.
109279: The desktop client was failing under certain conditions when the
Customers node was expanded in the Manage Relationships dialog.
109296: The desktop client was displaying the project in the wrong place after using the
Project Merge tool.
109348: An error was occurring when creating a request after having typed a first letter to find a value in a valid
109688: Queries created in the web client were sometimes not displaying correctly in the desktop client.
109753: Renaming a project folder to a name containing brackets was resulting in an error.
110428: When the the desktop client Preferences were set to display the
user name, the Privileges tab of the Show Users and Roles dialog did not reflect this in the drop-down list.
110678: While creating a baseline, dragging and dropping a request into the request text field did not result in the request being related.
110679: A public query created in a desktop client session was not initially being displayed in another client session; the client had to be closed and reopened.
110701: There was a problem trying to create a user profile that excluded the display of customers.
111175: Capturing build outputs from a build job from the Desktop Client to a Dimensions z/OS node, resulted in the derived target Items being created at the top level design part.
111289: Dragging and dropping items onto a project folder twice in succession was resulting in an error.
111764: In the Related Items view of requests scoped by baseline, the Status field was not being refreshed correctly after an item was actioned.
112083: It was possible to select Project Flags for more than one project, when the operation is only effective for one project.
112537: The Find in Files function was failing to find a specified project folder when it had upper-case characters in its name.
112614: The Find function was failing to find items with a specified stage ID when it was a new stage that had been added to the database.
112645: The list of user interface profiles contained duplicate entries when profiles
had been assigned both to the user and to a group to which the user belonged.
112651: Context-sensitive help topics were not being displayed when using IE 7.0.
112711: When getting a file specifying a target filename containing ".metadata" in the path,
a failure was occurring.
112782: The desktop client was terminating when displaying the pedigree for an item
when a new revision of that item was being simultaneously checked in.
112792: The order in which document windows were displayed was not being preserved correctly
after one of the windows was closed.
112847: The owning design part was not being displayed in the Relate/Unrelate dialog for an item.
113019: Switching user profiles was causing the desktop client to crash in some circumstances when the user had a number of profiles assigned.
113237: The Compare Item dialog was always selecting the previous revision to compare with the selected one regardless of which revisions had been selected by the user.
113808: In the Customize Views dialog for projects, the user-defined attributes were not available for the primary view.
113831: An error was occurring when right-clicking a request in the request catalog under certain conditions.
113878: It was not possible to cut and paste text containing line breaks into a character type attribute.
113882: After performing a request query and saving the list, the request inbox display was subsequently corrupted.
114081: The files and folders in a deployment area are now sorted when displayed in the desktop client.
114185: Selecting the navigation pane as floating and selecting Folders and Items was causing the project to reset to $GLOBAL.
114320: The results tab of the Create Query dialog can now be resized vertically and at the corners.
114507: The Delegate Request dialog was not displaying all the existing role assignments when the request was related to multiple design parts.
114685: There was a performance problem when getting the items in a baseline.
114828: The "Start build after deployment" check box was not enabled when deploying a request related to a project that had a build configuration.
114956: In the Query Builder for requests, if a request type had more than 10 characters in it's name it covered the adjacent request type selection box.
115328: A UI profile that had options selected in the My Current Project view was not displaying that view at
115621: It was possible for a user to action an item from its initial state to the next state although no one held a role on the second state.
116018: The performance when removing items from projects has been improved.
123054: The incorrect server version was being displayed when clicking on the server icon in the
About dialog box.
123164: Attempting to relate a request to a project using drag and drop was resulting in an error.
123305: After opening an item in its own window, using PF5 was corrupting the item names in the Folders and Items view.
123315: Performing a multi-item get when one of the files in the folder had the same name as the item file, did not
result in a warning message saying that Dimensions had not overwritten the file.
123980: After changing an item's type the change did not take effect until the client was restarted.
124096: When a request had "Affected" and "In-response-to" revisions of the same item, the related items view was showing the earlier
"Affected ones" when the view was unexpanded (to show only latest revisions).
124288: Attempting to move, rename, or delete a project directory for a second time
in the same session was resulting in an error.
127555: There was an error when displaying the Properties dialog box for a release when the Description attribute had been selected for display in the Customize Views dialog.
77965: When using custom tools, the
$(Part) and $SpecUid(Part) arguments were not returning an empty string if the design part view
had not been opened with a design part selected.
99700: In the Project Merge tool, with the fields
"Created" and "Revised" displayed, right-clicking on a line where there was no difference was causing a memory error.
106292: When changing the item type for multiple items, it was necessary to log out and log in again for the new lifecycle to apply to the items
106826: The desktop client was terminating when a large number of windows were opened.
107027: Changing the name of a toolbar icon in the Preferences menu was causing the desktop client to automatically log the user out.
109492: The default colors for
Context and View Header are now based on the Windows Active Title Bar colors
109507: In the Customize Menus/Toolbar dialog, there were two entries for Item in the popup menu list.
109661: Standard Windows Ctl shortcut keys were not working in the Find in Files dialog.
109850: Creating a filter name containing a comma in the Find dialogs resulted in two filters being created, and an error
occurred when trying to run either of them.
111567: The Print option in the context menu
for a request was printing the contents of the console instead of the request. The popup menu Print option now prints the request.
111573: The Query Builder for requests was not finding any requests when related baselines were specified in the query.
112107: When exporting a request as a CSV file, quotes in a text field were not escaped correctly.
114033: Using a filter that contained wildcard selections
that resulted in no items being found was causing the desktop client to terminate.
114271: Changing a project ID resulted in an error when the user subsequently attempted to browse one of its items.
114507: If a change request was related to two or more design parts and had a user role assigned at only one of those design parts, the Users and Roles tab of the Delegate dialog and the Delegate to Other Users page in the Action wizard
both showed that role as having no users to delegate.
114890: In the Customize Views dialog for Items, System Defined attributes contained two entries for "Full Filename".
114960: When renaming a project folder, copying and pasting the text did not work.
115015: Block attributes were displaying in the wrong order within the desktop client compared with how they had been entered in the Administration Console.
115493: There were problems logging in to the desktop client after the session had expired. Under certain circumstances, the login attempt would fail with a Microsoft memory error.
115566: The catalog in the "My Current Project" tree was not being displayed in certain circumstances when the UI profile set in the Administration Console should have allowed the user access.
115670: Users could not browse items using Textpad by setting this as the default editor for a specific item format in the Preferences dialog Editors tab. It would only work if set as the editor for all relevant Item formats.
123674: When a baseline was attached to a project as a sub-project of that project, performing a get on an item within that baseline did not include the folder offset in the the 'Copy Item To' folder.
124093: Baselines with a user-defined attribute of date format were being sorted in alphanumeric
order In the baseline display.
124982: Performing a delegation with more than 5 delegation users selected failed with an error displaying a corrupted username.
127568: The Inbox for requests in the
"My Current Project" folder was displaying some request that were not actually pending for the user.
127773: When selecting a project from the
cross-project catalog, and attempting to sort the related items, the message
"the view has been created from some or all of the content...." was displayed and the sort was not performed.
127990: The Inbox for requests in the
"My Current Project" folder was displaying some requests that did not belong to the current project.
128828: Attempting to configure the desktop client to work with the Diffmerge tool from Telelogic did not result in the parameters being passed correctly.
128865: There was a problem under certain conditions where updating item attributes was causing the desktop client to fail.
128969: The Merge Item Revisions dialog window was too small to display long item specifications, and could not be resized.
129440: There were performance problems when
selecting on a request to display its related objects.
- 55045: There has been an improvement to the error message that occurrs when you attempt to merge files without having installed the native code
- 55399: There were problems with the description field when priming a request under certain circumstances.
- 55720: The Upload Items dialog in the web client was not working when using
<server>::/<dir> notation to reference files on a remote node.
- 79922: You can now define a filter for releases in the Manage Releases dialog.
- 83293: There was a failure creating a request with a relationship type of
"Info" under certain circumstances.
- 88731: When adding a block attribute for a request that exceeded the maximum length, an error message was not always displayed, even though the request had not actually been created.
- 102653: The web client was creating initial revision numbers of 1 instead of 1.0 for standard level numbering.
- 104066: The web client was not creating the metadata for the working location root folder
after getting an item.
- 109859: The form controls for read-only attributes were difficult to identify (on IE) and difficult to read (on Firefox). Changes to the stylesheet have now made the text and background color more
- 110242: Web client was enforcing mandatory attribute values on the Open Request dialog in some circumstances when they were not mandatory.
- 111230/115207: Valid sets with a single row did not auto-populate as expected in web client.
- 113494: If the user's password contained a '%' character, and the login page was submitted by pressing the Enter key (rather than the Log in form-button) then the web client failed to log in and showed an error message.
- 114373: When selecting a request in the Build Project dialog, running the build was failing because the request contained quotes.
- 114825: When priming a request with multi-valued attributes that contained some empty values, the empty rows were being corrupted in the new request.
- 115318: The Add Item dialog was showing incorrect text for users with their browser set to the Italian locale.
- 115446: Clicking the Save button in the Open Item dialog was causing a design part usage relationship to
- 115712: An error "There are no targets to build for this build configuration."
could incorrectly occur when attempting to build a baseline in the web client.
- 116051: In the Update Item dialog, an attribute was displaying the value of the previous
revision under some circumstances, when it should have displayed as
blank because the “Stored per revision, default as specified” option had been set.
- 122970: The Item Revision History dialog now additionally displays the current status of each revision.
- 123066: The title and detailed description of a request were not marked with a red exclamation mark even though the attributes had been defined as mandatory.
- 126867: The web client was always showing the Revision Generation setting of a project as Optional regardless of how it had actually been set.
- 125495: A UI profile that specified just "All Requests" with the associated
Inbox, and having the Catalog option deselected, was resulting in the web client for that user displaying the Catalog.
- 128978: After customizing the displayed columns in the web client
using Mozilla 1.7, the main display could be corrupted until you refreshed the page.
- 86517: The interface between Remedy HelpDesk and Dimensions was not closing Dimensions requests when the corresponding incidents in Remedy were closed.
- 93605: The VM migration was not producing a descriptive error message when there was a product name that was too long.
- 98588: It is now possible to specify an owning design part when adding a file using the Eclipse integration.
- 99180: In the New Request wizard in the VS .Net integration, the Next button was
disabled but no message was displayed when a mandatory attribute was
- 112152: There was a problem when checking out an item from RAD and subsequently checking it in from the desktop client. The checked out
Status did not refresh on returning to RAD.
- 112469: When importing a project into Eclipse after upgrading to Dimensions 10 an error was occurring when attempting to synchronize.
- 114678: The Dimensions TeamTrack Synchronizer now synchronizes historical events from
- 116248: The list of products in Visual Studio was not sorted in order.
- 123548: There was a problem where requests in Dimensions CM were being actioned through multiple state transitions when
an issue had only been actioned to the next state.
- 125235: The VM to Dimensions migration was failing under certain conditions without producing an error message.
- 122586: In Dimensions Connect for TeamTrack
the "Delegate_$Originator" role was not being mapped to TeamTrack
- 123550: Changes made in Dimensions CM were not always being transferred to TeamTrack at the time the synchronization was run because of a delay in the event timestamps being written into the database.
- 126578: Synchronizing files with "ñ" or "Ñ" in the filenames was corrupting the filenames and resulting in an error.
- 126880: A null pointer exception was occurring when reconnecting to Dimensions CM after modifying a checked out file in the Eclipse integration.
- 127143: There were performance problems with the Eclipse integration under some conditions.
- 127600: Performing a Synchronize in Eclipse with override and commit was not
overwriting changes made by another user.
- 128890: The TeamTrack to Dimensions
synchronization was failing because it was attempting to create TeamTrack issues with missing mandatory fields from Dimensions CM requests.
- 130029: When successively adding a number of projects via Visual Studio 2005 an error "DBIO: Too many open cursors ..." was occurring.
4.6 Dimensions Build
- 113727: Secondary targets were not having their design part relationships created correctly.
- 116307: The PBEM process was not running a process in a work area with the correct permissions for the user's group.
- 122946: There is now an option in the Build Baseline command to apply the system date and time to files that are downloaded to a build area.
- 123930: When executing a build on a remote AIX system, the job was failing to find the build logs.
- 112697: When performing a build with one or more items to build (for which targets have been defined), the Targets tab always shows all targets as selected. A warning dialog is now displayed to inform the user to view the Targets tab and select the required targets.
- 122509: When running a build via
the desktop client in 10.1.1, the user needed to select both the Target and Options tabs to ensure that the target and options were set up correctly in the resulting BLD command.
- 128069: The area scan functionality on the Dimensions CM server was causing incorrect target preservation.
- 128503: The Build Baseline function with the parameter
DMXFERSOURCE=YES was not transferring the sources.
- 130932: A build configuration on a HP-UX remote node build location was performing very slowly.
- 107068: Dimensions Build was not creating a target when the name of the file differed in case from the target definition.
- 107252: Attempting to access the help topic for Build Manager - Scheduler was resulting in a Http status 404 error.
4.7 Dimensions for z/OS
- 109120: z/OS templating now supports temporary data sets.
- 115616: When starting the ISPF client an error: "CEE3204S The system detected a protection exception" was occurring in certain circumstances.
- 122610: A communications error was occurring when issuing a CC command to the Dimensions
z/OS Batch Interface program.
4.8 Synchronize Wizard
- 106366/107061: The hover text in the Synchronize Wizard file display was not being refreshed correctly under certain conditions.
- 112191: An exception was occurring in the Synchronize Wizard when accessing an item
that had previously been edited in the desktop client.
- 102533: Closing the Synchronize
wiizard when the synchronization was still processing resulted in the desktop client subsequently failing or being unstable.
- 123541: When maximizing the Dimensions Synchronize Wizard window the Resolutions/Options/Details pane
became grayed out.
- 126848: An error: "Caught a DmException with a code of: MDHASM6901204E" was sometimes occurring when using the browse button in the Synchronize Wizard.
- 126829: When performing a synchronization for a work area on a UNIX platform, the design part for new items was not being set correctly according to the upload rules.
4.9 Privileges and Roles
- 105214: The Action to any state privilege is, by default,
only enabled for the Admin group
- 106227: The relevant users were not able to browse items when the rule "User holds any role on the design part owning the object"
was set for that privilege.
- 109189: There was a problem whereby a delegation candidate for an item, who was able to check the item out, was not subsequently able to check the item back in.
- 114092: The "Assign Request to Project" privilege is no longer being used and has been removed.
- 116473: It was possible to action an item to the next state without requiring a role, and the item was not in anyone's
- 123590: The "Override Process Checks" privilege is no longer enabled by default for the "User is the originator of the object" rule.
- 123806: A user with the WORKSET-MANAGER role did not have the privilege to export an item from one project to another.
- 123977: Role allocations were not being correctly updated when a user had been deleted and then recreated.
- 124952: Users were able to create project directories when creating items without having the
- 126433: It was possible for a user to action an item to a certain state because the item was in their inbox,
even though they did not have a role on that transition.
- 127145: Exporting an item revision from one project to another in Dimensions 10.1.1 required the Workset/Project Manager role on the exporting project rather than the receiving project.
- 127701: The roles of Workset Manager/Project Manager were not allowing the appropriate operations for creating, deleting, and renaming project folders
- 128024: The privilege rules OBJ_PEND and ORIGINATOR_OBJ were not working correctly for a user attempting to build from a baseline they had created.
- 123202: The DMMAKE installation on the server was overwriting the make_sql_uk.msb with an older version, causing an "Add To Workspace" operation from the Serena Explorer in Eclipse to fail.
- 73988: The dm_shutdown command was not always stopping dimensions processes.
- 113698: After installing the native components on a UNIX system, the diff tool was not working on the web client.
- 113771: After installing on a Windows 2000 platform, the desktop client was failing under certain circumstances.
- 108324: In the patch installer, a silent install was not placing the files correctly on a client system.
- 114200: The patch installation for the listener only on Solaris
failed to copy all the required files, without reporting any error, resulting in errors after starting the listener.
- 125417: The Dimensions CM agent installer for the 10.1.1.1 patch was not correctly copying the files on certain UNIX agent platforms.
4.11 Server Issues
- 76120: The refreshpoolconfig command was not working when there were several dimensions servers running on the same
- 101348: The Listener on HPUX platforms did not work unless the tracing was switched on.
- 112660: There were problems creating item directories on a Windows machine after using the Windows version of the UNIX "tar" utility. This was because of a missing file
cygintl-8.dll. The correct instructions are now contained in Updrading to Dimensions CM 10.1.2.
- 115253: There were problems when using delta libraries on a HP-UX 64 bit platform.
- 122716: There was a problem where dmappsrv was terminating when using the desktop client under certain conditions.
- 124638: There was a failure using the Java API when processing umlauts when connecting to a Oracle DB which used a character set different to AL32UTF8.
- 124701: The dmpool process was disconnecting when an item was being actioned in the web client in certain circumstances.
- 127546: It was not possible to use an item library on a remote node
where the directories were owned by a specified user.
- 128979: There were performance
problems when selecting certain projects in the Folders and Items view in the web and desktop clients
4.12 Other Defects Fixed or Enhancements Made
- 55577: An SQL error occurred when exporting a process model if a request relationship existed across products.
- 71574: The PEND command was failing without indicating the reason under certain circumstances.
- 74055: The regdeploy command was failing with an "invalid URL" message in some previous releases of Dimensions.
- 99409: When exporting a database and specifying products, the data formats and
MIME types were not being exported to the new database.
- 102523: dmpmcli was producing an error when querying baseline templates.
- 106800: There were some situations where a deployment area was not being populated correctly.
- 107333: Pending users have now been added to the text for request e-mail notification messages.
- 110028: The e-mail template for delegated item notifications now allows system-defined attributes.
- 112595: The wrong project file path was being used when uploading items from a UNIX work area.
- 114884: Passing parameters using localized characters with the REXEC command was resulting in incorrect values.
- 115669: Adding new item from a remote AIX agent node was giving a permissions error even though the user had the required permission.
- 115789: There was a failure to check out and overwrite an item on a remote AIX node.
- 116321: Directory items were not being created and fetched correctly on Solaris platforms.
- 116472: The CMP command, when used to compare two baselines, was producing incorrect results.
- 116479: The CMP command to compare baselines has been enhanced to function more usefully.
- 123367: Running a dm_make containing an undefined variable was causing a core dump.
- 123471: When viewing RM Requirements in CM clients, some blank lines and corrupted data were being displayed.
- 125674: Multiple Get operations to a library cache area were not populating the area.
- 125980: The TeamTrack to Dimensions integration was not working when TeamTrack database was using a US7ASCII character set.
- 127134: When an HP-UX system was set up to use shadow password files, Dimensions was failing to authenticate any users.
- 127256: DMAPPSRV was intermittently hanging during baseline deployment on a remote node.
- 127561: There was a problem on Suse Linux platforms where Dmappsrv processes were not being closed down after logging
out of the client.
- 122518: The performance has been enhanced when creating a baseline using a template that
selects items by their specific status using an SQL Server.
- 115287:The function PCMS_FULL_QUERY was returning a "DB ReadStart Failed" error on a HPUX platform.
- 122778: Using dmpmcli to replicate attributes between different products was resulting in an exception.
- 55446: The %PIRIF% and
%PIRIT% parameters for displaying parent and child items in item templates were not working.
- 82164: The pcmsmail function was not sending emails to all the specified users when the
-t parameter was used.
- 99316: The Java API does not currently support the UPLOAD and DOWNLOAD commands, which is now documented.
- 124016: Deploying a baseline was sometimes failing with an error.
- 126135: A baseline using a template specifying items at the Unit
Tested state was also including items at other states.
- 131082: The pdiff
dump file created for a request with an attachment incorrectly set the value of
.DATE to be the same as .USER, thus preventing the request being loaded via PDIFF because
of the date format being incorrect.
Return to Contents
5.0 What Was Fixed in Dimensions CM 10.1.1.1
5.1 Desktop Client
- 112747: There was a problem entering multi-column block attributes in the desktop client under certain conditions.
- 112750: The pedigree display was being unnecessarily refreshed when changing focus from and to the desktop client.
- 112851: Attempting to relate a request by dragging it onto a design part
resulted in a "part does not exist" error.
- 113530: If multiple items were opened in an Items window, using f5 to refresh caused an incorrect filename to appear for the items in that window.
- 113848: There was an error in the desktop client when items had the same library filename which differed only by case.
- 114096: When using a non-English Windows OS with Dimensions, a recursive get would result in each file being fetched individually instead of using the new downloaded method.
5.2 Web Client
- 112618: The web client was unable to display lists of requirements if there were too many requests in a collection.
- 113001: The baseline selector interface between Dimensions CM and Mover did not work the first time it was invoked.
- 111697: When a project name contained Korean characters in Eclipse 3.2, the name became corrupted in Dimensions CM after a synchronization.
- 112106: Checking in via the Eclipse integration was failing and causing corruption when a file or folder name contained Korean characters.
- 112342: On Korean Windows Platforms, the Eclipse Show History dialog was only displaying the current revision of an item and not previous revisions.
- 111925: Visual Studio would hang if a warning dialog was not immediately closed from Dimensions in the Visual Studio interface.
- 112600: There is better support for loss of Dimensions connection during synchronization.
5.4 Dimensions Build
- 111785: A Dimensions Build job was failing because of refused connections with a build having a large number of compiles and links.
- 111796: A Dimensions Build job taking more than one hour was being cancelled after the job completed.
- 111872: A Dimensions Build job was taking a long time to complete because the collection was processing slowly.
- 113310: The export of build configurations in the ChangeMan DS Migration did not contain design part information.
- 113525: Korean characters were being corrupted when used in build scripts.
5.5 Other Defects Fixed
- 112108: The Dimensions TeamTrack synchronization did not fail cleanly when there was an invalid connection.
- 111905: The performance of the Dimensions TeamTrack synchronization has been improved.
- 107837: After a VM migration to Dimensions CM, double-byte character comments were not being displayed in the History dialog.
- 112449: When attempting to action a request under certain conditions, users with a role on the correct design part were told they did not have the 'Action to Next State' privilege.
- 112835: A user belonging to the ADMIN group, but with no role on the product, was unable to view the detailed description for a
request belonging to that product.
- 110815: The dmpmcli function AttributeDefinition.getValidSet() was not working in Dimensions 10.1.0.
- 113122: If a Dimensions CM database had more than one product using the same library filename it was possible for the
latest tip revision to have invalid data.
- 114005: The Close button is now grayed out in the Synchronize Wizard
during the processing of the updates.
- There is a more accurate return code from the pcmsmail executable (specifically when failing to connect to the SMTP server).
Return to Contents
6.0 Copyrights, Trademarks, and Acknowledgements
Copyright © 1988-2007 Serena Software, Inc. All rights reserved.
This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Serena. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification.
This document contains proprietary and confidential information, and no reproduction or dissemination of any information contained herein is allowed without the express permission of Serena Software.
The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Serena. Serena assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Serena, TeamTrack, StarTool, PVCS, Collage, Comparex, Dimensions, RTM, Change Governance, and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Dimensions, Professional, Version Manager, Builder, Meritage, Command Center, Composer, Reviewer, Mariner, and Mover are trademarks of Serena Software, Inc.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
U.S. Government Rights
Any Software product acquired by Licensee under this Agreement for or on behalf of the U.S. Government, its agencies and instrumentalities is "commercial software" as defined by the FAR. Use, duplication, and disclosure by the U.S. Government is subject to the restrictions set forth in the license under which the Software was acquired. The manufacturer is Serena Software, Inc., 2755 Campus Drive, San Mateo, CA 94403.
This product includes software developed by The Apache Software Foundation
This product includes software developed by Computing Services at Carnegie
Mellon University (http://www.cmu.edu/computing/).
This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/)
CONTAINS IBM(R) 32-bit Runtime Environment for AIX(TM), Java(TM) 2 Technology
Edition, Version 1.4 Modules
© Copyright IBM Corporation 1999, 2002. All Rights Reserved
Copyright © 1998, 1999, 2000 Thai Open Source Software Center Ltd and
Copyright © 2001, 2002, 2003 Expat maintainers.
Copyright 1998-2006 The OpenLDAP Foundation.
Portions of this Software are derived from IBM Corporation Sample Programs. Copyright © IBM Corp., 2002, 2006. All rights reserved.
Optional Oracle components embedded in Dimensions are also subject to the following Copyright Notices:
Copyright © 2003-2006 Oracle Corporation. All rights reserved.
NOTICE OF RESTRICTED RIGHTS
Programs delivered subject to the DOD FAR supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
Return to Contents
End of Release Notes