![]() Users are encouraged to use ClearQuest 7.1.x because expanded date ranges are allowed.Īvailable starting in ClearQuest Version 7.1.0.0 Change Request type ![]() This behavior is corrected in ClearQuest 7.0.1.11 by displaying a more descriptive error message. On clients that run on platforms other than UNIX, an error message displays indicating that the record cannot be found. ClearQuest 7.0.1 clients cannot display dates outside this range. The valid date ranges for ClearQuest 7.0.x clients is to. In ClearQuest 7.1.x, you can set date values outside the valid range supported in ClearQuest 7.0.x. This behavior change does not apply to reference list fields.Īvailable starting in ClearQuest Versions 7.0.1.11 and 7.1.0.0 Change Request type If this behavior is not desired, it can be customized by using a choice list hook. To prevent this common issue, values in reference fields are not hidden, and the default reference field choice list includes all possible values, unless the field in question is a security context field. As a result of these changes, if a mandatory reference field is set to a hidden record, it appears to be unset if the user is not allowed to see the relevant hidden records for the reference field. ![]() In ClearQuest 7.0.0.4 and 7.0.1.3, changes are implemented to improve record security. However, it does list some changes that occurred in 7.0.0.x, 7.0.1.x, and 7.1.0 that were identified as causing issues for some customers.Īvailable starting in ClearQuest Versions 7.0.0.4 and 7.0.1.3 It does not contain a comprehensive list of changes that occurred in ClearQuest 7.1.0.A large number of RFEs were addressed, and Web 2.0 technologies were implemented. In ClearQuest 7.1.0, the web client and web server were redesigned to provide enhanced experiences over the ClearQuest 7.0.1 web client. It does not list the ClearQuest Web behavioral changes that occurred in ClearQuest 7.1.0.Instead, it lists defect corrections and RFEs that might cause more noticeable changes, or changes for which a schema designer might want to assess the impact on your schema customization. It does not list all defect corrections or RFEs from earlier versions of Rational ClearQuest.This technote does not cover the following information: The technote also describes scenarios in which a schema designer might need to adjust your schema customization to account for the defect fix or RFE changes. This technote describes defect corrections and RFEs that might have a noticeable impact on how you interact with Rational ClearQuest. Defect corrections fix incorrect behavior, and RFEs implement new behavior. ![]() To ensure a consistent experience across tree views contributed by different Remote extension, we may want to use the same set of icons ( icons repo) and actions when appropriate.Defect corrections and RFEs change Rational ClearQuest behavior.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |