| |
Results |
|
Dim10: When creating a new release, an error of 2384-Error: The specified item is not in the project $GENERIC:$GLOBAL occurs
|
When creating a new release, an error of 2384-Error: The specified item is not in the project $GENERIC:$GLOBAL occurs. The following error shows in the console window of the Desktop Client: FI "<Prod>:<Item Spec>;<Rev>"/NOEXPAND/OVERWRITE/NOMETADATA/USER_FILE="<User filename>" /WORKSET="$GENERIC:$GLOBAL"
|
|
|
|
KM-Dim7: Error: "No configuration search path specified"
|
This error occurs when the workset is set to the global workset. The user needs run the SCWS command and change the workset to another valid workset.
|
|
|
|
Upload specifies the incorrect revision when latest rev not in current workset
|
Currently upload -n generates an incorrect script in certain instances. This causes the UI command to specify the latest revision of the item in the global workset and not the latest revision in the current workset. This can be a problem if this revision does not exist in the workset we are currently uploading to, as the upload will then fail complaining that the revision does not exist in the workset.
|
|
|
|
IOO311: Offsets incorrect for DDM settings after re-assembling Global Table
|
takes effect below 16M (for instance, if the job specifies a REGION greater than REGNHWM). Unfortunately, I think I have inadvertently increased the confusion
|
|
|
|
DIM10: DM_DISABLE_BRANCH_CHECKINS causes merges to fail with error messages
|
COR2800037E Error: Item "TEST1:CDRTOOLS_2.00.3/ABOUT-SRC" has multiple leaf revisions in Project "$GENERIC:$GLOBAL" and the corresponding File "C:\Temp\pt5b8c.tmp" has no metadata. 2384- Error : The specified item revision is not in the project $GENERIC:$ GLOBAL - No new revisions are created, or relationships changed and the same conflict remains after the error window is closed.
|
|
|
|
Fixed in TeamTrack 6.3
|
8. Values are no longer cleared for all Mass Transitioned items when Numeric fields are placed on Mass Transition report forms but users do not provide a value for these field types when executing the report. 9. When using the Search or Global Search features, users who specify Active, Inactive, or Either Choice no longer see incorrect results when modifying these search criteria using the Back to Search link.
|
|
|
|
Known Problems - TeamTrack 6.2
|
15. When using the Search or Global Search features, users who specify Active, Inactive, or Either Choice may see incorrect results when modifying these search criteria using the Back to Search link. To work around this problem, users should modify Active, Inactive, or Either Choice options after clicking the Search or Global Search options on the toolbar rather than the Back to Search link.
|
|
|
Serena TeamTrack 6.3 Readme
|
4.0 Fixed in TeamTrack 6.3, Build 63016 (Windows and Solaris versions) Values are no longer cleared for all Mass Transitioned items when Numeric fields are placed on Mass Transition report forms but users do not provide a value for these field types when executing the report. When using the Search or Global Search features, users who specify Active, Inactive, or Either Choice no longer see incorrect results when modifying these search criteria using the Back to Search link. In systems that use an Oracle database, you are no longer able to select the Use the CLOB Data Type option for Text fields that you are modifying.
|
|
|
|
TeamTrack 63029 Chinese Patch
|
4.2 Fixed in Build 63016 Values are no longer cleared for all Mass Transitioned items when Numeric fields are placed on Mass Transition report forms but users do not provide a value for these field types when executing the report. When using the Search or Global Search features, users who specify Active, Inactive, or Either Choice no longer see incorrect results when modifying these search criteria using the Back to Search link. In systems that use an Oracle database, you are no longer able to select the Use the CLOB Data Type option for Text fields that you are modifying.
|
|
|
Microsoft Word - Serena MLA WW clickwrap 041405.doc
|
10.2 Support Coordinators. M&E shall consist of support provided by Serena to one (1) designated Support Coordinator of Licensee (and one backup Coordinator) per licensed Software Product and Server by telephone, facsimile, email and World Wide Web site, regarding the use and operation of the current version of the Software, and the immediately preceding version of the Software as specified in Section 10.5, in accordance with the user documentation, error investigation and updates.
|
|
|
