This file contains information about new features in Serena Dimensions CM 10.1.1 and 10.1.0. It also contains important information about defects corrected in these versions of Dimensions CM. See the relevant sections below.
This release includes all the fixes that were present in 10.1.0, and in patch 1 (10.1.0.1 release), patch 2 (10.1.0.2 release), and patch 3 (10.1.0.3 release) to Serena Dimensions CM 10.1.0.
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.
The following startup documents are available from the product DVD:
Return to Contents
The Merge Item Revisions functions have been enhanced in the desktop client to enable local work files to be included in the merge, and to be selected as the ancestor or target for the merge.
Both the web client and desktop client now enable an existing item revision to be selected as the target for the merge. This allows conflicting revisions of a file to be logically merged without invoking the PVCS Merge tool, and without creating a new revision. This updates the pedigree of the item to mark an existing revision as being the result of the merge without changing its contents.
You can now select any baseline for deployment. You could previously only deploy baselines that were attached as sub-projects to your current project. In the web client, the Deploy option is available for a selected baseline from the Baselines tab. In the desktop client, the Deploy option is generally available from the pull-down or popup menu for a selected baseline in the catalog.
It is now possible to select requirements from baselines as well as collections in the My Current Project view. Expanding the Requirements node shows requirement baselines as well as collections. These are distinguished by having a different icon from a collection. Selecting the baseline displays the requirements belonging to that baseline.
There is now the option to have item files copied to the new deployment area when they are deployed. This can be set for a specific project. The Options tab of the New Project and Edit Project dialog box now has a Deployment Areas option. When set to "Copy files on deploy", item files are copied to the new deployment area when they are deployed to a new stage but they are not removed from their current area. If this is set to "Move files on deploy", item files are removed from their current deployment area when they are deployed to a new area. There is also an additional option, "Copy files on deployment", that can be set for a project type in the Administration Console. Selecting this checkbox results in new projects of that type defaulting to "Copy files on deploy".
The Query Builder dialogs in the Web client and desktop client have been enhanced so that a Null comparison can be made based on whether or not an attribute has been filled in. Search criteria can be added specifying an attribute value of "Is Null" or "Is not Null".
The Query Builder feature in the web client has also been enhanced to include search criteria that were previously only available in the desktop client.
You can now override the owning design part for new items when using the Windows Explorer Plug-in and the Synchronize Wizard. By default, the owning design part for a new item is determined from the upload rules but it can now be overridden at various levels. It can be set in the "Set as Working Location" dialog box for the root folder of a working location in the Windows Explorer. It can also be set in the Properties tab for an individual file.
The Synchronize Wizard will use any such settings that have been made in the working location and also allow the user to enter an owning design part at the root, folder, or file level when performing a synchronization.
The following server platforms are now supported:
The following integrations are now supported:
The following browsers are now supported for the Dimensions CM Administration Console and Web client:
The following enhancements have been added to the Version Manager Migration Console:
You can now synchronize the Action Description to and from Dimensions, but not to the same field in TeamTrack.
TeamTrack to Dimensions: You can map a TeamTrack Journal or Memo field to the Dimensions Action Description field. The name of the Dimensions attribute that you need to map is ’--> ACTION_DESCRIPTION’. This mapping takes the text from TeamTrack and adds a new Dimensions Action Description with that text. The following comment is then written back to the mapped TeamTrack field:
***Serena Connect for TT Synchronized***
Dimensions to TeamTrack: You can map a TeamTrack Memo field to the Dimensions Action Description field. The name of the Dimensions attribute that you need to map is ’<-- ACTION_DESCRIPTION’. This mapping takes all the action descriptions from the Dimensions request that were not entered by the user running Dimensions CM Connect for TeamTrack (that is, not action descriptions that originated in TeamTrack), and replaces the text in the TeamTrack field with the new text
You can now map a TeamTrack single selection field to a Dimensions project (use the Dimensions attribute DIMENSIONS_PROJECT). If the field is set in TeamTrack, the Dimensions request will be related to the given project. If the field is unset, the Dimensions request will be unrelated from any project. If a Dimensions request is related to a project, the value will be set on that TeamTrack field. To map a TeamTrack project to a Dimensions project, set the default value for the TeamTrack single selection field that is mapped to the Dimensions project to the appropriate value.
File attachments, notes, and URLs are now synchronized in both directions, though you can only create notes and URLs in TeamTrack. Notes are named TTNotexxxx.txt where xxxx is the internal note ID in TeamTrack. This ensures that notes with the same title can be synchronized.
You can now map the Elapsed Time field and/or Time of Day field to a character or number attribute. The mapping takes the display value of the TeamTrack field and tries to set it on the Dimensions attribute. In the other direction (Dimensions to TeamTrack), to ensure that the TeamTrack field can accept that value, check that the value in Dimensions is entered in the correct format. If it is not, the synchronization of that field will fail. For date fields the TeamTrack value is read as the display value (Dimensions CM Connect for TeamTrack takes the time zone setting of the user running the integration in TeamTrack). This is the value that is entered into Dimensions. To avoid confusion, the time zone setting of the user running Dimensions CM Connect for TeamTrack should be the same as the setting on the Dimensions server.
The Dimensions rich integration to Visual Studio has been enhanced to include the following:
The Dimensions rich integration to Eclipse now allows you to store multiple Eclipse projects within a common Dimensions CM project.
E-mail templates have been enhanced to support a number of new variable and format changes. These new variables are detailed below:
The parameters that can be entered in the dmemail configuration file can now also be specified in the command line. In this case they will take precedence over those options in the configuration file.
The treatment of temporary files has changed. They are no longer accumulated for sending later. They are now created, used, and then deleted for each email. During a long run of dmemail, only a handlful of temporary files should exist.
The following parameters have been added:
There are two new Build template variables:
This enables you to change the address of the build server that is defined in the BRD file, typically the server from where the build is launched, and specify the address of an alternative build server.
Usage scenario: When you launch a build from a virtual machine, and are building on a remote node, the address of the build server in the BRD file on the remote node may be the physical machine hosting the virtual machine, and not the actual virtual machine. You can use DMALTSERVER to change the address to that of the virtual machine.
Must be in the following format:
http://<IP address of the machine hosting the build server>:<Tomcat port number>/bws/services/monitor
To transfers sources automatically to work areas, set the variable DMXFERSOURCE to YES. By default Dimensions, does not transfer sources to work areas.
Item Libraries can now be hosted on Network Attached Storage (NAS) using UNC paths.
WebSphere Application Server 6.0 support has been added.
The upgrade from Dimensions 9 now upgrades all build projects to convert them into configurations in Dimensions Build.
The Impacted Targets dialog box, and the Targets field in the Run Build dialog boxes, have been enhanced to display detailed build dependency information.
Additional template variables have been added to assist build template writers.
The Build Progress display has been improved to show pending messages from the Build Agent which are waiting to be processed.
General enhancements have been made for better logging and saving of dependency information from each build execution.
The desktop client now uses Download for multiple get operations, significantly improving performance.
(ENH103807: DMROLLOUT: Desktop Client needs to have same WAN performance as Eclipse)
The Pedigree display now shows which item revisions are checked out
(ENH110840 When users had files checked out the Pedigree display did not show them any differently)
The desktop client can now compare files on a remote node
(ENH107600 Unable to compare files from web client or desktop client with remote nodes)
The web client now uses Download for multiple get operations significantly improving performance.
(ENH105786 Performance difference between using Get from Web Client and Download via dmcli)
The web client login page can now be accessed via a link from another page
(ENH103405 Request for the web tools login page be accessed from a link on another web page)
The web client can now compare files on a remote node
(ENH107600 Unable to compare files from web client or desktop client with remote nodes)
When creating a new project, the stage of all items can optionally be reset to the initial stage.
(ENH109636 When creating a new project need an option to reset stage to initial stage)
Deployment now delivers files in a single download command and runs scripts only once, significantly improving performance.
(ENH109691 Deployment is very slow since it runs scripts once per file)
Return to Contents
Beginning with Dimensions CM 10.1, product name changes took place and terminology changes were also introduced. The following table details the product rebranding:
|Current product name||Legacy product name|
|Serena Command Center*||n/a|
|Serena Dimensions Build*||n/a|
|Serena Dimensions CM||Serena ChangeMan Dimensions|
|Serena Dimensions RM||Serena RTM|
|Serena Mover||Serena ChangeMan Mover|
|Serena PVCS Version Manager||Serena ChangeMan Version Manager|
* New product
** Encompasses all Dimensions components
The above product name changes have also led to changes in the Dimensions documentation set. Refer to the Introduction to Dimensions CM manual for a comprehensive list of the Dimensions documentation set.
The following table details the terminology changes:
|Current terminology||Legacy terminology|
|custom list/request list||user list*|
|custom list/request list||custom list**|
|deployment area||build area|
|deployment stage||build stage|
|library cache area***||n/a|
|project working area||workset root directory|
|user interface profile***||n/a|
* Desktop client
** Web client and Visual Studio .NET Add In
*** New term. See the User's Guide and Process Modeling User's Guide for details of these new terms.
The latest Dimensions 10.1 documentation reflects the new terms, so if you are using a new Dimensions 10.1 component with a component from an earlier release of Dimensions (for example, the Migration Console in conjunction with Dimensions 9.1), you must bear in mind the terminology changes when working with the older components.
NOTE: Certain specialized features will continue to use legacy terminology, but the new terminology will be used when describing these features in the documentation. These features comprise:
For the developer, this release offers productivity and usability improvements in the following key areas.
Dimensions 10.1 replaces "worksets" with a more powerful capability called "projects". Projects are fully supported Dimensions objects with customizable lifecycles, user-definable attributes, and granular security options supported by the new Dimensions privileges model.
Requests (change documents) can now be related to projects. This enables you to easily determine which requests you should be working on for a specific project.
Optimistic locking, also called "pragmatic locking" or "merge on check in", is now supported. Optimistic locking enables you to check a file in without first having checked it out. The file metadata stored in your work area is used to ensure that the correct version is updated.
The Synchronize Wizard compares a set of folders and files located in a work area with the item revisions in a Dimensions CM project and determines the changes that have occurred between them. It provides a graphical display containing icons and text descriptions. Based on this comparison, the Synchronize Wizard can make updates to the work area and the Dimensions CM project as necessary.
Dimensions integrates the request management functionality of Dimensions CM directly into the Visual Studio environment. This allows you to simplify and automate the identification, management, and processing of change requests while working within Microsoft Visual Studio.
Dimensions integrates the request and version management functionality of Dimensions CM directly into the Eclipse environment. The new integration simplifies and automates the identification, management, and processing of requests within the Eclipse design environment. It also includes improved source control functionality, including support for optimistic locking and project baseline creation. The integration is supported on Eclipse 3.0 and 3.1.
Dimensions provides an integration with Microsoft Windows Explorer that allows you to:
Key enhancements in the desktop client and web client include:
Project view: The client tools include a tree structure that shows the objects that are related to your current project. You can expand and select the various nodes to display objects in the content area. The nodes correspond to the aspects of the project that you can work with, including folders, design parts, work areas, deployment areas, inbox, catalog, and sub-projects. This view provides fast access to all of your project artifacts from one view. Additionally, the desktop client includes a cross-project catalog and inbox, allowing you to view the objects for the current product.
Queries: The client tools include a query builder that lets you select lists of objects according to selected criteria. Unlike filters, queries enable you to specify sophisticated filtering conditions that can be combined using Boolean operators. You can also specify which columns in the list are displayed and the sort order. You can make a query public, so that it is available to other users.
Pending requests: The client tools enable you to view the current role assignments for a selected request, and view the users who currently have that request in their inboxes. You can also view the privileges for a user for the request.
Web client customization: You can now customize which columns are displayed in the web client, as well as other display settings.
The dmclient Java API provides full, programmatic access to the features of Dimensions CM. The API allows you to create and manipulate versioning, change management, and process modeling data while under the control of the permissions of Dimensions CM and the change management rules framework. The API is compatible with JDK 1.4.2 and later and all Dimensions CM supported platforms.
When working at the Dimensions command line, you can invoke text-based help for any Dimensions command. The help returns the full name and complete syntax of the command. To invoke help for a command, type: help <command-name>
This release introduces the concept of areas. A project can typically have areas associated with it to which Dimensions CM will automatically copy versions of item files when you perform certain operations. There are three types of area:
Work Area: An area associated with a project for a particular user or number of users, so that their file operations such as check in, check out, and so on, take place in the context of that area. Multiple developers can also share the same work area, to facilitate collaboration on shared files.
Deployment Area: An area associated with a stage in the lifecycle for a product such that item files are moved to that area when the item revisions reach a particular stage in the Global Stage Lifecycle.
Library Cache: An area that contains copies of item files for a project to improve the efficiency of Dimensions item operations when users access a database over a remote network. When a user needs to access an item file, Dimensions looks in the library cache area first to see whether the file is already there before attempting to retrieve it from the remote server.
As businesses become increasingly subject to the global economy, participants and contributors to the application lifecycle may span multiple geographies, languages, and locations. Native Unicode supports local character-set input and maintains consistency and integrity across the CM repository, regardless of location.
In Dimensions 10.1, Replicator can now be configured to support "Air-Gap" replication, which is replication between Dimensions servers that are not connected via the network. This is particularly applicable to multi-level security environments or when direct network access across sites is not permitted.
In this scenario, the replication process consists of 3 phases:
Replicator copies data from Dimensions to a physical media. The transferred files are secured using timestamps and a comprehensive audit trail.
Data from the physical media may then be transported to a subordinate site and loaded.
Logs generated on the loading phase are then synchronized with the master to ensure a complete audit trail, including timestamps and any changes.
Air-Gap replication is the recommended solution for customers currently using TBO/TBI.
For this administrator, this release offers the following key improvements and features.
Improvements to the installation include:
A common installation into a single database for Dimensions CM and Dimensions RM.
The ability to install the Administration Command-Line Interface (dmpmcli) on a Dimensions client machine.
The ability to install client components to a directory path that contains spaces.
For the Dimensions for z/OS installation, the ability to customize Dimensions variables via a configuration file.
This release introduces the concepts of privileges and groups. A privilege is either a particular operation that can be performed on a class of object, or an administrative function. You can assign privileges to specific users, groups, or roles, or apply them generally to any user or under particular rules.
Examples of privileges include:
A group is a set of users to which you can assign a privilege, which assigns that privilege to all the users that belong to that group. Groups provide a manageable way of granting and denying privileges to large numbers of users.
With an Oracle database, you can now define up to 996 user-defined attributes.
You can set up user interface profiles that determine which functions are accessible in the client tools, and assign them to particular users or groups. For example, you could set up a profile to display functions related to change control or version control only. UI profiles do not necessarily relate to privileges.
You can subscribe users or groups to certain events (for example, an item or request arrives in a user's inbox, or an item is added or removed from a project) so that the users will receive an e-mail notification when the event occurs. You can also specify that multiple notifications are to be consolidated into an e-mail digest to reduce the number of e-mail messages sent.
On Windows, it is now possible for users to change their OS password from within the Dimensions CM clients. Frequently users connect to a Dimensions Server on UNIX where the authentication is processed, but those users don't have the knowledge or access to log into the UNIX system to update passwords. By making this capability available within the clients, users can perform their own password management without calling on their system administrators.
Serena Command Center 1.1 provides the executive and development manager with the ability to visualize the current state of projects within their portfolio. As a central point of interaction, the Command Center provides graphical reporting on key project indicators with the ability to drill into details, enabling better monitoring and visibility of the project state as well as analysis of root cause.
In its first release, the product provides insight into the portfolio of projects, including related baseline, build, and requirements information. The tool provides for role-based information security with the ability to filter and tailor its reports on an individual basis.
The new Dimensions Build component, a standard part of Dimensions CM, extends the capabilities introduced in the integration of ChangeMan Builder with Dimensions. Dimensions Build adds these benefits:
Supported platforms are identical to the platforms supported by the Administration Console.
If you are an existing user of ChangeMan Builder, the integration with Dimensions Build enables you to import Openmake targets into Dimensions Build, manage your build configurations, and compile your targets using the Openmake engine. For details, see the Dimensions Build User's and Administrator's Guide.
NOTE: Builds are synchronous and you must wait for the builds to complete before the desktop client can display feedback.
This release provides extended migration tools that allow you to easily upgrade from PVCS Version Manager to Dimensions CM. You can migrate all or part of your Version Manager project structure to specific Dimensions design parts, projects, and item types. You can also migrate Version Manager labels and promotion groups to Dimensions multi-valued attributes, projects, and baselines.
This release introduces the Qlarius sample database. Qlarius provides a rich overview of the application development lifecycle, from requirement definition to product release. Qlarius demonstrates integration to Dimensions RM, supplies sample development projects in Eclipse and Visual Studio, and supports a number of sample reports in Command Center.
Return to Contents
55757. 55589, 103287: There was a problem assigning roles to a design part if the design part ID contained a ".".
55903: The About dialog in the Administration Console was displaying a blank database field when the database was DB2.
76451: When exporting a template in the Administration Console, and entering a directory path without a filename in the dialog box, the file path was subsequently being corrupted.
82717: When the Data Format list in the main window exceeded one page of entries, errors were occurring when trying to assign and unassign object types.
83314: There were performance problems when modifying a large valid set in the Administration Console.
88148: Following a Dimensions upgrade, existing request templates were not visible in the Administration Console if they contained a hyphen in the revision field.
93204: A Microsoft update to Internet Explorer meant that it was necessary to click on certain pages before they were activated.
96168: There was a problem updating request type options in the Administration Console using an SQL Server in some previous releases of Dimensions CM.
103540: Clicking the Add Role (+) button when editing a transition in the Edit Global Lifecycle dialog box was displaying a 404 error.
103632: There was a problem in the Administration Console where a group subsection was not displayed correctly when there was a large number of user groups.
104481: Setting the privilege to rename item filenames did not actually enable users to perform that operation.
104844: Project privileges that had been set for users with certain roles were not actually allowing them to perform the tasks.
106607: There was a problem configuring priming rules for attributes with wildcard characters in their IDs.
55757: Periods were removed from product names when adding users to products. This resulted in a failure to add users, because the product name was truncated.
55935: The text field for an attribute definition's help message allowed entries that were too long and got truncated. It now no longer allows entries beyond the maximum length.
73201: The text field for the user prompt allowed entries that were too long and got truncated. It now no longer allows entries beyond the maximum length
77757: The upload rules display could get confused when connected to an SQL Server database.
103597: After assigning a filter to a deployment area it was not possible to subsequently update the area to have no filters.
105629: There was a problem whereby, when selecting from the list of users to assign to an area, the owner of the area was not being retained in the list.
105892: When assigning attributes to a project type, the drop down list of defined attributes was not available as it was for other object types.
107325: Editing multiple users at the same time could reset the users' department fields.
109262: When displaying attributes for request types, in the Valid Set column the validation group name was displayed and not the valid set name.
71142: There was a problem where revising a baseline sometimes resulted in some incorrect item revisions being included.
100131: First deployment stage not displayed on item check in
When checking in an item at the first stage of the Global Stage Lifecycle the deployment stage for the item was not being displayed.
100526: Release of Baseline not downloading expected items
There was a problem where, under certain circumstances, performing a release was not including all the item files that would be expected from the baseline.
103440, 106893: It was not possible to use the Mgdiff compare/merge tool from the Synchronize Wizard.
104777, 105493: The General Grant Rules for "User has any role on object lifecycle" and "User holds any role on the design part owning the object" were not allowing users to update a request even though they satisfied the conditions of the rule.
51224, 80494: When an item revision was related to two requests and a revised baseline created that specified both requests, only the first request would subsequently be related to the baseline.
109775: Baselines excluded version history for items included in the baseline. When creating a baseline from change requests, only specific revisions of items that are in response to those requests were included in the baseline. To ensure that complete revision history information is included in the baselines, the baselines should also include any change documents to which previous versions of the items are related.
110145: If you chose to assign attributes when checking in a new revision of a file using the RI command from the command-line interface, the attributes were not updated on the new revision if those same attributes were already assigned to a previous revision.
55870: When you created a revised baseline based on one type of baseline and then chose to change the baseline type, the attributes available for the revised baseline were derived from your initial choice of type, not the new choice.
92383: When you merged an empty workset with a large workset, merge performance was very slow.
95807: When you renamed an item filename, the item history displayed a new revision creation date.
102816: The dmcli client was displaying the wrong version number
103553: The dmpmcli script roleAssignmentsDemo was failing with an error when tying to add a new role assignment.
104075: It was not possible to browse some requests after certain attributes had been added to the process model.
105028: The dmcli command DNP (Define new Product) was failing when specifying a valid attribute.
105073: The privileges definitions could not be set up to prevent a developer from actioning a request to a Closed state.
105241: Actioning items in a baseline resulted in an error for items that were already at the state to which they were being actioned.
105558: An error was occurring when merging two baselines containing different revisions of the same item.
105997: A user group could be added using dmcli with a name of greater than the maximum length, causing subsequent problems displaying it in the Administration Console.
106213: There was a problem running RPT when specifying /ATTRIBUTES
106285: It was not possible to use deployment areas for a project that had same name as previously deleted project.
106437: Performing a recursive get of a project was much slower for a user with the developer role that it was for dmsys
106467: Under certain conditions, using the option "Don't force new revision number on check in" was causing an error when trying to override the revision number on check out.
106556, 110900: It was possible to create new items at the top design part, even if no user had the correct role to transition items from this design part. As a result, these new items do not end up in anyone's pending list.
106509: It was not possible to modify the user comment on a previous revision of an item.
106780: The Dimensions CM for Visual Studio log in dialog box did not display all defined connections.
106825: There was an invalid value in the New revision field when checking out the current revision of an item file whose branch name was locked.
107167: Creating a baseline with a template was taking much longer to complete than in Dimensions 9.x.
107248: When renaming an item, the change was not logged in the item history.
107315: Populating an area could fail if the project contained checked out files.
107390: Korean project directory names were corrupted.
107436: It was not possible to use wildcards for related parts in queries.
108253: When an attribute was required and writeable for a transition, and another attribute rule existed to make the attribute writeable but not required for all transitions, the second rule overrode the first. This was contrary to the behavior in earlier Dimensions releases.
108314: Upload rules were not working properly in desktop client and web client.
108692: The Rename and Relate privileges for part management were not working correctly.
108778: When target preservation was enabled for z/OS builds, a pop up error message was received for every item that Dimensions tried to preserve.
108798: It was not possible to generate a full control plan using RPCP.
108999: The pm_label_branch command would not create a named branch.
109022: Running the Dimensions 10.1.0.5 upgrade script on a database removed the UI profiles.
109113: There were problems loading valid sets using a pdiff load script.
109388: Baseline replication was not deleting the temp project.
83933: Dimensions now only supports writing to z/OS containers (PDS and PDS/E) with RECFM=U if they also have LRECL=0.
109263: The flag -replicate_remote_branches was not valid.
109391: A normal user could not relate an existing item revision with the relationship ‘in-response-to’.
109390: Under certain circumstances, when change requests were related to a baseline, these would fail to be replicated and reported the following error: "Error: Baseline <spec> does not exist".
109618: There were problems with the stability of the listener.
109695: If you enabled the Forced Revision flag on a project you could still set the revision number.
107951: On a Solaris UNIX system, entering a date attribute in the format mm/dd/yy displayed the year as ‘19nn’. For example, if you entered ‘02/29/08’ the date was displayed as 29-FEB-1908.
104561: There was a problem when relating a request to a design part and unrelating it from another one in the same dialog. An error message stating "You cannot unrelate the last design part from request .." even though it had first been related to another one.
104602: Moving from tabbed panes to split panes in a desktop client content window was causing a memory error under certain conditions.
105954: When a user had the PRODUCT-MANAGER role for a product they were displayed in the desktop client Users Roles and Privileges dialog as having the same privileges in the other products in the database, even though this was not so.
55579: If the user was displaying the item pedigree window, and they deleted the last item revision, the desktop client would crash.
79793: It was not possible to view attached files or other related objects for requests in the secondary catalog.
80487: It was difficult to select items to unrelate because the only visible information was the item specification, revision number, and description.
81216: The "Find in Files" function was failing to fine any items in a project directory if there was one upper-case letter in the name of the directory.
96879: There was an application error that sometimes occurred when the user clicked on the catalog in a project.
106622: In the desktop client the Stage ID field was not displaying any value after having been added to the item properties.
107426: The error "CLN0005167E Error: Inconsistent data set for image browser" was occurring when performing a merge/compare on an item after having browsed for the lifecycle image.
109777: A Build Monitor page appeared when you started a build from the desktop client. If you displayed the HTML source for this page, the user password was visible in clear text.
110274: On Windows 2000, you could not edit the Actual Effort in Hours attribute when actioning requests.
110661: When you executed a build by request from the desktop client, the correct target was not built. The first source item in the project tree was built instead of the target related in-response-to the request. Furthermore the Run Build for Request screen did not display any targets.
110840: The Pedigree view did not indicate whether files are currently checked out.
110919: If a user did not enter the correct password when attempting to log back in to Dimensions after the session timed out, the desktop client attempted to authenticate ten times before prompting for a new password. As a result, if the limit on failed login attempts was set to less than ten, the user's account was locked.
111076: When you attempted to sort baselines by type or stage ID, the following
InternalSuperQuery::addOrder failed to find attribute map entry in admschema.xml for Class:4 attr_no:-301 scope:merant.adm.dimensions.objects.WorkSet scopeUid:4307403
111381: The desktop client crashed when you chose either the Move to splitters or Move to tabs view options.
55579: The desktop client crashed when you deleted the last revision of an item from the pedigree view.
78389: When multiple items were selected, it was not possible to drag and drop a request into the relate / unrelate screen.
78815: When unrelating items from requests, Dimensions displayed the item specifications in the Unrelate dialog box instead of the item filenames. This was difficult to use.
79793: It was not possible to display attachments or relationships for requests in the secondary catalog.
81176: When you clicked on a design part, the entire specification appeared editable. However, if you then edited only the design part name, an error message incorrectly appeared stating that you could not include the @ sign in design part names.
81216: When executing a search against files in a project, the following
error appeared if the project directory name included upper case letters:
Find in Files :- Error : <name> Directory does not exist.
96879: The following error appeared when attempting to open the Dimensions
catalog in the desktop client:
dmappsrv.exe - Unable to Locate Component
102820: An exception was occurring in the manage Relationships dialog under certain circumstances when expanding the Customer node.
103751: The customization of colors for requests in the desktop client was not being applied correctly.
105033: Performing an item merge when the server connection timed out was causing the changes to be lost.
105998: It was not possible to restore the "General" toolbar in the desktop client after having removed it using the View menu.
106064: A query specifying date ranges created in the web client was not displaying any results when run in the desktop client.
106305: Items in Baselines were displaying the current status in the status field and not the status when added to the baseline.
106795, 106281: When a file was selected in the Work Areas view, the browse function was displaying the item in the repository and not the file in the working location. Also it was not possible to browse files in the working location that did not have a corresponding item.
106854: No results were returned when querying requests from items.
107123: If the profile definition All Releases/Customers was not enabled, in the Cross-Project Catalog the views All Customers and All Releases were still displayed.
107063: You could not browse GIF items or lifecycle pictures using the Windows Picture and Fax Viewer.
107566: The message ‘No Request Found’ was displayed multiple times.
107609: In a window that was created by a Find query, for example Requests (Find Results), you received an error when trying to sort by column.
107957: The desktop client crashed when trying to create a new item in a product that is used for request management only and has no item types.
108104: If you customized the Initial Views tab on the Customize dialog box and set the ‘Requests Inbox’ to be the ‘topmost’ view, the desktop client failed to open projects.
108492: The desktop client sometimes hung when you clicked the Privileges tab on the Show User Roles and Privileges dialog box.
108659: If you were working in a project that was not the default and the desktop client timed out, after you logged back in the default project working location was used and not the working location of the active project.
108711: Valid set performance for block attributes was very slow.
108713: You could not assign deployment areas to stages in the Global Stage Lifecycle that did not have a description.
108726: An error message dialog box was leaving a ‘shadow’ of itself after it was closed.
108800: Project defaults set in the Administration Console were not used when creating new projects.
109034: When customizing views, duplicate tabs could be created.
109056: When using a third party merge and compare tool, the tool crashed if used to compare files without extensions, for example, Makefiles.
109057: The desktop client crashed when using a third party merge tool to compare files in a project compare results window.
76655, 102192: There was a problem with the release command when run from a UNIX server via the web client on a Windows platform such that some text files might not have had end-of-line character translated appropriately.
104061: When a user interface profile was created to hide build management functions, the web client still showed them.
104631: When accessing remote files on a Dimensions Agent on a UNIX platform via the web client accessed via a Windows web browser, file path separators of "/" and "\" could get confused.
75527: There was an error when the user tried to display an item history after a particular revision had been deleted and then recreated.
77625: Get Copy or Check Out from the Revision History dialog took user privileges from the global project, not the current project.
81627: The text field for the Release Subdirectory allowed entries that were too long and got truncated. It now no longer allows entries beyond the maximum length.
82957: Under certain very specific circumstances, doing Get Copy, it was possible that some of the files could be fetched to the wrong directory on disk.
85818: Creating a delta release from the web client was fetching all the files in the release instead of only those that had changed.
98543: In a particular complicated set of attribute update rules, the web client was not showing the same set of mandatory attributes as the desktop client.
105786: Get Copy to a remote node has been enhanced to improve performance.
106286: Check In from a z/OS PDSM failed with some combinations of options.
106685: Merge/compare from remote file nodes was not supported in the web client.
107822, 108273: If you sorted available delegates alphabetically by first name, the delegation of requests was sometimes incorrect.
110306: When you selected a project folder that included the word "Other" in it, all toolbar buttons disappeared.
55833: If you navigated relationships for a request, opened a related request, and then chose to navigate relationships for the related request, attempts to Save and Action failed.
88560, 102921, 107131: Performance was slow when large item listings in a
baseline or project directory and when filtering for only latest revisions.
Note: Increasing the page size beyond 50 in the User Preferences will adversely affect performance even with this fix installed.
92245: Because Microsoft modified the implementation of Active X support in Internet Explorer, it was necessary to repeatedly press the space bar or Enter key when using the Web client.
98517, 105782: When uploading files, the Web client used to include files in the .metadata folder.
102395: The Mgdiff compare/merge tool was crashing when used from the web client using Firefox on Red Hat Enterprise Linux 4.0.
103405: If the Login page was launched from another web page, it could cause some functions to work oddly.
103421: When creating a release baseline and selecting change documents to relate, the resulting dialog box did not allow you to select multiple requests.
103639: The web client was producing HTTP error 500 when selecting the Requirements option if Dimensions CM had been installed without RM
104657: It was not possible to query properly by date in the web client query builder.
105782: The web client Upload function was also uploading existing metadata files and directories into Dimensions
106008: Design parts containing spaces in their names are now correctly quoted when selected from the design part selection dialog on the New Baseline dialogs.
108028: There was an error when priming a request without specifying a relationship.
108051: If you tried to change the name of a project, the name did not change and no error message was displayed.
108165, 108924, 109627: Checking out an item from the Revisions History dialog box checked the revision out to the Global project instead of the current one.
108885: Release to a remote node in the web client ignored the overwrite option.
109609: Some users were seeing an HTTP 500 error on login under very specific customization scenarios.
109610: There were very rare database upgrade circumstances where fetching a project folder recursively from a project created by an earlier release of Dimensions (and where the base database was since upgraded to 9 or 10, but where the project had never been viewed in the desktop client) would not fetch all of the files from web client.
71483: Base DBs based on the INTERMEDIATE product included far fewer pre-defined file formats / MIME types than base DBs based on the GENERIC product.
101484: There was an error "DBIO: Too many open cursors" that occurred when issuing multiple DUSR commands.
104126: An error was occurring when attempting to delete a group when it had a role assigned to it, but did not have any privileges assigned directly.
104481: Setting the privilege to rename item filenames did not actually enable users to perform that operation.
104844: Project privileges that had been set for users with certain roles were not actually allowing them to perform the tasks.
111171: The following privileges did not work:
User has any role on object lifecycle
User holds any role on the design part owning the project.
101594: When creating a new base database via the dmdba tools crdb command, the new base database did not contain any information in the dropdown lists 'Platform' and 'Type' when creating a build configuration.
105488: With certain language configurations, the dmemail system did not work correctly when a request contained an umlaut.
106658: dmemail did not deliver e-mails where the subject line included double quotes.
106923: There was a problem where, after an upgrade under certain conditions, users were not able to check out items unless they belonged to the Admin group.
107127: The defect deals with the privilege,'Action to Next State'
For the privilege Action to Next State, the General Grant rule "Object is in the user's inbox or user has current role" will now check if the user has a role on the transition to next state and/or whether the item is present in the user's inbox (if role is "pending") in the lifecycle transition.
107839: Creating a baseline with selection criteria based on build stages did not result in the baseline being created.
106681: It was not possible to define the role PCMS-ROLE-MANAGER at the design part level. The ROLES_PART rule has now been added to the PRODUCT_ROLE_ASSIGN privilege.
106686: If a user had a role with an Optional rather than a Pending flag, Dimensions ignored the user and they could not transition items.
106782: When deleting roles that had a privilege, the privilege was not deleted in the product, prohibiting the product from being used as base for a new product.
112414, 112449: Users actioning requests received an error: "You do not have the 'Action to Next State' (REQUEST_ACTION_NEXTSTATE) privilege" when the option "Take roles from all affected design parts" was not set.
109178: Using the merge functionality from the pedigree display within Visual Studio .NET 2005 was not producing the expected results when not using standard revision numbering.
109200: When Source controlling a .NET 2003/5 solution there was no easy method to allow all projects in the solution to remain under a root directory on the file system and a base working directory in a Dimensions project.
110220: When merging files in Microsoft Visual Studio 2005, the display of conflicts was not automatically refreshed.
110221: In Visual Studio 2005, files that were checked out did not correctly display the file status in the pedigree display.
110222: In Visual Studio 2005, when a conflict occurred while merging automatically, the merge tool windows appeared minimized.
110227: The requirement to reserve new revision numbers when checking files out was confusing. It is simpler to allow users to merge their changes into new revisions at check-in. Using the Synchronize Wizard and offline mode in Visual Studio, you can now do this with Dimensions 10.1.1.
110229: Performance using the SCC integration to Visual Studio needed improvement.
111627: When overwriting the baseline ID for a baseline created from the Eclipse integrating, Dimensions used the auto-generated ID instead of the user-created ID.
51653: When you delegated a request to the user DMSYS, additional assigned users were not displayed in the Delegate dialog box.
80185: Users who did not have administrative rights on their Windows system could not run the Dimensions Visual Studio integration.
93978: In Visual Studio, the following error appeared when priming requests:
"Attribute name has not been defined"
101360: It was not possible to relate an item in an Eclipse project with another item from a different project except by selecting it in the Global project.
103078: The plug-in for Eclipse 3.2 was not supported in Dimensions CM
103128: Dimensions CM did not support integration with Mercury Quality Center V9.1
104274: Creating a new project using the Eclipse plug-in was failing with an error under certain circumstances.
107780: In Eclipse, files with international characters in the filename were not added to the workspace.
108178: In Eclipse, merging a main baseline with a branch baseline into the main project failed during synchronization.
108644: In Eclipse, the message ‘No details available’ was displayed when checking in files that were migrated from Version Manager.
110223: You can now use a third-party merge/compare tool to merge XML content in Visual Studio.
101342: Impacted targets were not being successfully generated for mainframe platforms.
102677: The Impacted Targets panel was not showing affected targets effectively for certain types of file such as header files and copybooks.
104063: The target files preserved in Dimensions were being related to the root design part for the product and not the same design part as the TGT file that created them.
110521: The following build error message occurred with Dimensions for z/OS:
MDHD048E SVC99 on OSJOB (dd name) returned RC 104
91858: If you attempted to browse PDS while Dimensions Build for z/OS was
populating a build area, the build population process stopped and the following
fopen(DD:DMINF2,wb,type=record,recfm=*): EDC50921 An I/O abend was trapped.
Error:access is denied to file <file>
99962: When undoing check-out of a build configuration, an error appeared
that stated the following:
Internal SPI error: Error: failed to update database.
103925: There was a problem creating build configurations in a base database that had been created via the crdb command based on another database
104325: Importing build configurations was failing under certain conditions.
105325: Using a mainframe work area as a root was producing non-functional FI commands.
106004: There was a problem where not all derived COBOL items were displaying in a BOM.
106517: The transfer of source files to a build location was failing if the password to the area was not set.
107906: Building a large number of targets in one step caused the build to hang.
108661: There was an ‘upload failed’ error if a work area's logical node was related to a mainframe IP address.
108705: Problems with the logic relating to work areas caused baseline builds to fail.
108979: The PBEM was getting errors when searching for templates because the data set names were incorrect.
109344: Baseline builds on Windows caused the desktop client to crash.
109503: In the z/OS SBEM, insufficient storage was available when executing complex build steps.
86241: When invoking a build on an item at a state not mapped to any build stage, the Build Item dialog box defaulted to the initial lifecycle stage, and no other stage could be selected.
109556: When building a COBOL CICS program the CICS pre-processor step failed because the '$' was dropped from the program name.
111470: When attempting to build a baseline, an error occurred saying that the user did not have the 'Build from a Baseline' (BASELINE_BUILD) privilege even though it had been assigned.
110216: The following error appeared when you attempted to compare or merge
files on z/OS:
Error: Unable to access the following file for reading: <file>
111305: After setting the no-more-data flag, when fetching an MVS item larger than one block to an ASCII platform, the file was truncated, losing the contents of any trailing partial block.
55911: You could not edit an item from the ISPF client if CM Rules were active, even if you specified a valid request when attempting to edit the item.
96676: On installing the ALM suite, there was no menu item in the program group for launching the RM web client
97109: During a server upgrade from Dimensions 9 to 10.1 the destination folder for the Dimensions root directory was blank when the Installation directory page was displayed.
96921: The Qlarius demo database has been enhanced with more relevant data that demonstrates the new features of Dimensions.
97109: When upgrading Dimensions 9 to Dimensions 10, by default the destination folder location was blank.
103517: An error occurred when upgrading a base database to Dimensions 10.1 if there was an attribute with the same name as an Oracle reserved word.
103634: Running a documentation-only installation was not fully installing the documentation.
103647: The privilege ACTION_ANYSTATE was enabled in a new installation for the "object in user's inbox" rule.
104576: The version numbers and copyright dates displayed in some clients were inconsistent.
105947: Valid relationships between requests and items were lost on upgrading from Dimensions 9 to 10.1
106098: The explorer plug-in for Dimensions CM was not working work after installing on a system under certain circumstances.
106115: The upgrade from Dimensions 8 to 10 was not updating the schema correctly.
106185: If a Dimensions 9 web query contained an affected design-part, then the query could not be modified after upgrading to Dimensions 10.
106205: It was sometimes not possible to browse some requests after upgrading from a previous release if assigned attributes had been removed for that request type.
106245: Fetching items to a work area when also using a library cache area was not copying the files under certain circumstances.
106281: There was a problem authenticating on a remote node authentication after upgrading Dimensions on Windows
106431: Registry settings were causing installation problems when the DM_ROOT path contained spaces.
107394: Silent installation did not install the Serena Merge tool.
108954: On UNIX, symbolic links were not being created correctly by the installation script.
93687: The following error appeared when you try to run the dmimport portion
of the migration, when you migrated on a Korean language system:
Warning: Archive <archive name> will not be transferred
94584: VM users that included multi-byte characters in their names were not migrated.
93945: When you resized the Synchronize Wizard, the Resolution / Options / Details pane was grayed out.
105260: Local file exclusions were being ignored in the Synchronize Wizard when synchronizing to a Dimensions Agent on a remote node.
105624: The synchronize Wizard was failing to use the default request for the project when merging items under certain conditions.
94584: VM users with DBCS names were not being translated properly by the VM Migration.
55911: When editing an item in the ISPF client and entering a valid request ID, the edit was not working.
103777: Dimensions was not handling an attribute of type DATE correctly when using a DB2 database.
103496: Item Libraries can now be hosted on Network Attached Storage (NAS) using UNC paths.
90639: The event triggers for action baseline do not provide information about both the previous and current action state.
92245: There were problems in Dimensions in Microsoft Internet Explorer due to an MS update to ActiveX behavior.
71142: When you created a revised baseline, the baseline included revisions that were related as "Affected" to requests that were related to revisions in the original baseline. This is incorrect. Revisions related as "In response to" should be included in the revised baseline.
87245: With LDAP, when the LDAP base was set to the root of the network domain, users were unable to log in to Dimensions.
94561: Request update and action dates were not updated when the requests were delegated. As a result, the delegations were not picked up by the Synch API.
102955: When using pcmsmail, specifying the -a flag (i.e. adding an attachment) prevented the header information that the -i flag normally creates from being added to the e-mail.
103793: There was a situation where baseline replication resulted in a corrupt baseline if some aspects of the process model were set differently on the master site compared with the subordinate site.
104241: Connect for TeamTrack on Oracle was not recognizing certain TeamTrack updates
105937: PDIFF failed if a description of the file contained ‘line break’ 0x0D
106551: The pcmsmail utility was issuing the SMTP command with a space, which was causing the command to fail when the email was sent in certain mail servers to more than one user.
107059: The Merge tool could not handle more than 160,000 items.
107497: PowerBuilder crashed when trying to add a project to source control.
107598: Merging a project and branch project in Eclipse that contained a file that had been renamed or deleted caused the Serena Merge tool to report an internal error.
108095: There was a minor error in the ide_setup.sql script. The file extension pattern should have been '%.mdf' instead of '.mdf'.
112404: There was a situation where the Dimensions listener failed to start under certain circumstances with the -trace and the -dont_use_proxy flags both enabled.
Return to Contents
51355: Umlaut characters (¨) are translated when used in role definitions.
80966: When you select a baseline template, the Administration Console automatically shows all baselines that use that template. Now the list of related baselines is displayed only if you click the Show Baselines Using This Baseline Template link.
90865: Users should not be allowed to delete a group with any privileges explicitly set (either grant or deny).
85231: Would like actioning to be disallowed if there are no users holding a role that has been designated as not optional.
85295: On UNIX, if you specify the item library path as a relative path rather than an absolute one, the library is created in a /tmp directory. Now you will receive an error message if you attempt to use a relative path.
98421: If you create a lifecycle state that has a space in the name, and do not select a role, the name includes the characters "%20".
79343: Would like to be able to change the name of build stages and add more stages. Fixed build stages are now replaced by the new Global Stage Lifecycle.
55800: The Administration Console should not allow you to suspend a design part that is related to an open request.
87559: A create baseline error occurs when you attempt to create a baseline with two requests (change documents) related as In Response To different revisions of an item.
84238: Right-clicking a baseline with certain menu sets selected causes a general protection fault.
78459: When you add multiple objects in the Relate dialog box, it is unclear whether the relationships are created.
78535: On the Check Out or Get Copy dialog box, if you click the browse button to change the directory, the entry for the filename changes to *.*. Now the filename is retained.
87696: When you view a request, all revisions of a related item are available, even though not all revisions are actually related to the request.
89427: When you update an item, the file browser does not show any files for Name of File to Update Item From if you select the All Files (*.*) option.
87137: The desktop client should have the console window hidden by default.
91173: Drop-down lists should adjust to the width of valid set value entries.
91450: The desktop client crashes if a valid set value contains a single quote (').
91504: Revision numbering is no longer automatic when Use standard level numbering scheme for revisioning (option 11) is selected. When you try to edit an existing item, the value in the revision field does not increment.
91864: Would like to be able to customize how users are displayed in the main grids. Now you can set a preference that determines if users are displayed by full name or user ID.
80183: In item lists, you should be able to type the initial letter of the item to jump to the first item in the list with that letter.
81179: It is unclear whether the file name or the item ID gets renamed when you right-click an item and select Rename. Now the file name of an item can be renamed by right-clicking the item and selecting Rename. To change the item ID, select Change ID from the Item menu.
82719: The value of Display field length is ignored when set for attributes in an attribute block.
83527: The desktop client is limited to displaying relationships in three panes on the right side of an open window. Now related objects are grouped within a tabbed view, which allows more types of relationship information to be displayed while conserving space.
84903: You cannot relate a design part by dragging and dropping it into the Multiple Item Relationship dialog box.
84908: You cannot unrelate multiple objects in the Multiple Item/Request Relationship dialog box.
72325: Moving items to another project within a product can fail with this error: "ORA-02291: integrity constraint (PAI_PROD.WS_FILES_K3)".
72809: The desktop client crashes when you switch between projects with long IDs. Now the desktop client can handle project IDs with up to 128 characters.
91813: Would like previous version of desktop client to be compatible with the current version. Now you can install and use versions 10.1 and 9.x of the desktop client on the same machine.
87140: Pedigree shows duplicate item revisions after a merge if Use standard level numbering scheme for revisioning (option 11) is set.
71567: If you disable pooling using the -dont_use_proxy option, a communications error occurs when you attempt to log into the desktop client or dmcli.
92415: In the desktop client and web client, multi-column valid sets do not work properly with double-byte characters.
89332: The user interfaces should support localized date/time formats.
85502: Would like to use third-party merge tool in the desktop and web clients.
55455: On Solaris, the installation always installs Oracle database files into $ORACLE_HOME/dbs. The installation now creates a dbs subdirectory in the directory that you specify.
75997: The latest Windows XP updates cause a log in check error during installation of the server.
80398: The create_ora_inst script for AIX 64-bit searches for the file pw_syscall instead of pw_syscall64, which causes the script to fail. The call to this file is no longer required for the supported AIX platforms and has been removed.
88748: Dimensions allows you to specify only a single license server in dm.cfg, which prevents you from using redundant license servers. Now you can list multiple license servers using a comma (,) or semicolon (;) to separate them.
75286: On UNIX, running the dmlogin or dmprofile scripts overwrites the existing value of LD_LIBRARY_PATH.
89148: The installation should comply with MSI best practices.
87535: When you run upgradedb_8000.sql, the upgrade fails with this error: "ORA-01630: max # extents (99) reached in temp segment in tablespace PCMS_IDX".
91338: The integration with Mercury Quality Center is missing a file, ChangeAdmin.bat, which would allow you to set the administrative user name and password.
91730: Updates to request attributes in Dimensions do not get passed to Mercury TestDirector during a synchronization.
88409: After you have mapped all of your statuses in TestDirector, they are displayed in descending alphabetical order (Z–A) instead of ascending (A–Z).
70998: Attachments in TestDirector get transferred only during the initial synchronization. Any modifications to existing attachments or newly added attachments do not get synchronized. Now updated and new attachments get synchronized, except for deleted attachments, which require manual removal.
81433: Description field updates, action descriptions, and comments should get synchronized between TestDirector and Dimensions.
95728: Files added to Dimensions through Eclipse 3.x are added to the root of the project, using the Eclipse project directory name, instead of the expected project subdirectory.
71473: With the Eclipse 2.x integration, the ignore pattern works only at the file level, not the folder level. Now the ignore pattern at the folder level is implemented with the rich Eclipse 3.x integration.
88066: Would like support for linked resources with the Eclipse 3.x integration. You can now create linked resources that are files or folders stored outside of the project. The integration supports version control only for the files within the project.
71985: After you open, modify, save, and close a file from a shared WebDAV folder, the file does not automatically get checked into Dimensions.
92065: The rich integration with Visual Studio crashes if a job name contains an apostrophe (').
90901: Attempting to use .NET 2003 to bind a .NET project uploaded to Dimensions returns an "Unspecified Error".
90554: Would like change to script to increase DOORS performance.
86887: Would like support for DOORS 8.0. The integration is now supported on DOORS 8.0/7.1.
90557: Upgrading to 9.1.3 (from 9.1.0) causes the Powerbuilder SCC integration to stop working. The Powerbuilder console shows the error "Unable to load SCC Provider DLL: C:\Serena\Changeman\Dimensions\9.1\prog\sccpcms.dll".
86297: Would like support for JBuilder 2005/2006. The integration is now supported on JBuilder 2005/2006 Developer/Enterprise Edition.
92301: Would like to be able to perform a project comparison with a tertiary node. Now you can use workspace synchronization with node:: syntax to accomplish this.
89370: The Merge Tool does not work if the default working directory is set to a UNIX directory such as <node>::/<path>.
92383: Merging two projects with very different structures takes too long.
91580: When CM rules are turned on, there is no method for linking an item that is to be created to a request. Now you can specify a default request for a project.
89703: The Merge tool crashes when you try to resolve item conflicts.
90517: A general protection fault occurs when you try to resolve baseline conflicts.
49558: If an object in a pdiff dump file contains attribute update history with duplicate times, the load fails.
71271: If multi-value attributes do not have a display order set, the attribute values are incorrectly formatted in the pdiff file, and the import fails.
89839: An error occurs when you try to load requests using the -d option in PDIFF.
92115: The migration needs to support the following special characters in user names: number sign (#), dollar sign ($), and exclamation point (!).
92709, 93668, 92919, 93454, 91367: The migration needs to support the following special characters in paths and file names: ampersand (&), number sign (#), dollar sign ($), at sign (@), and exclamation point (!).
91960: Migrations fail when project databases and access control databases are mapped to UNC paths.
91961: You cannot add a project database in the Migration Designer if the project database is mapped to a UNC path.
92058: The Migration Console does not generate the correct VM user and password in the vmexport.cfg file, which causes the migration to fail.
92389: Subprojects are not migrated when the project recursive attribute is set to "True" instead of "true". This value is now case insensitive.
94586: Participants in each promotion level should automatically be migrated to a baseline with the same name as the promotion level.
90320: When you specify that the migration should create baselines from version labels, you receive an error that you do not have the role to create baselines.
93604: Change-description text for Version Manager items that exceeds the limit for Dimensions is captured in a new request, and related to the imported item. The migration audit report should state that requests have been created.
94583: The migration creates duplicate items when it encounters shared versioned files. Now the migration detects and reports any occurrence of shared versioned files.
91328: A memory error occurs when a request is related to an item revision that:
74498: Using the -dont_update_chdocs command causes a database I/O error during replication.
84239: If two requests are related as dependent, the relationship is not created in the subordinate site. The requests are copied to the site, but an error message is logged on the relationship.
72387: Any metadata updates made to an already replicated baseline should also be replicated to the subordinates.
72389: Baseline replication doesn't work if the name contains a space or a colon (:).
82789: When you create a new project, the Revision generation option should default to Optional instead of Forced.
73760: On Korean Windows, you cannot upload multiple items if there are matching characters in the Korean file names, particularly if the first 10 characters match.
81153: Queries fail if the name of a request type contains Korean characters.
81815: When creating a new item, if you select an owning design part that contains a space, you receive an error that you can't enter multiple design parts.
80372: When you add a new item with a design part selected, no item attributes are available. The item attributes are available when a project is selected.
91147: On UNIX, when you create new items and item revisions in the web client, the files are given permissions of 400. Now the files are given permissions of 444.
87880: Creating a new item causes the Item and Request tabs to stop displaying objects.
92293: Creating new items does not work when you try to add them to directories and multi-level subdirectories with long names.
91291: The option Display in: Edit Attributes dialogs for attributes does not prevent the specified attribute from being displayed when you edit the attributes of an existing request.
85198: When you delegate a role to a user, the dialog box should show both the user ID and full name.
86692: The Apache error_log file shows the error "dim_images/favicon.ico file not found", which is generated each time when Apache calls optional features that are not in use.
86703: When you check out a item that includes a value of FF (in hex) in the file, the file is checked out but the size is 1 KB and is corrupted.
89215: When you check in an item, the web client uses the server time instead of the revised UTC time, resulting in an incorrect timestamp.
94680: API: The API does not support triggers on project operations. Projects are now full standard objects with API support.
91812: Dimensions for z/OS: The -host parameter is limited to 20 characters. The limit is now 40 characters.
78185: Dimensions for z/OS: Would like the temporary dataset name to be configurable. There is a new REXX script called MDFRTMP that allows you to configure the dataset name used for a temporary dataset operation.
96401: ChangeMan Builder: On z/OS, the build sequence number is not incremented.
87782: ChangeMan Builder: Would like to have TGT files in more than the four build stages allowed. You can now define as many build stages as needed.
96591: DMCLI: Creating a baseline from a request with the option /INCLUDE_INFO causes the baseline to leave out any related requests except for the first related request.
81620: EXPM: If a process model contains Korean characters in a lifecycle name or request, the EXPM creates the export file with corrupted characters. When you attempt to create a base database using the export file, a DBS error occurs.
95193: Project Merge: Build areas not updated when you merge projects.
83678: Published Views: There is no view that shows the related request types on a replication configuration.
49191: Published Views: Would like a published view PCMS_BASELINE_TYPES that contains the user-defined baseline type information. Also, there should be a column containing the user-defined baseline type in the published view PCMS_BASELINE_INFO.
88376: The certificate generated by Dimensions when a build executes uses the sequence from the base database, instead of the sequence in the pcms_sys schema. This causes constraint violations because the certificates are never considered to be unique.
79465: The standalone download utility should include an option to overwrite copies of writeable files, rather than stopping with an error. This is now available with the new dmcli DOWNLOAD command that includes an /OVERWRITE option.
70700: The upload and download utilities should allow you to specify database parameters so that you can run without being prompted. This is now available with the new dmcli DOWNLOAD and UPLOAD commands.
74637: Adding a unique index would optimize read performance for queries on table release_items.
93456: Would like Mozilla 1.7 to be supported on UNIX.
90941: Would like support for Solaris 10. Solaris 10 (32 bit and 64 bit) is now supported.
83457: Releases to a net node creates directories with 777 permissions. The permissions have been changed to 755.
89906: A cryptic error message, "Create Release -", appears when Dimensions fails to create a release from an existing baseline. The error message is now more informative.
Return to Contents
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 (http://www.apache.org/).
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 Clark Cooper
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