Troubleshooting
Problem
After applying the ALMWork package to the ALM schema, a choice list value for a GUI element definition is YES and NO (in all capitals). However, the checkbox values associated with this field in the form are Yes and No (in mixed case).
Symptom
After applying the ALMWork package to the ALM schema, submit a new record with some specific record types in the ClearQuest client, an error message similar to the following will result:
CRMUD0065E The field "Doc_Related" has values not permitted by its choice list:
"YES"
The use of inconsistent letter case for these values (YES/NO versus Yes/No) in choice lists breaks almost all actions on ALM records due to invalid field values.
Cause
Starting in IBM Rational ClearQuest versions 7.1.2.07 and later and in 8.0.0.03 and later, fields defined with choice lists that include the 'Limit to list' option are case sensitive.
Resolving The Problem
To resolve the issue, the ClearQuest administrator should modify the constant list values in the "Choice List" hooks of the specific fields. Because the fields are added by the ALMWork package, the fields cannot be modified in the CQ Designer unless package editing has been enabled in the schema. These are the steps to enable package editing and to modify the SubscriberList so it limits the allowed values to those only in the choice list.
1. Run the packageutil command to enable package editing in the schema, substituting appropriate values for dbset, username, and password.
packageutil enablepackageediting -dbset <dbset> <username> <password> -enable <username>
2. Check-out the schema.
3. Find the Doc_Related field in "ALMActivity" record type, remove the "Yes" and "No" options and add the "YES" and "NO" options in its "Choice List" hook on Eclipse designer. If using Windows CQ Designer, right click on its "Choice List" hook and choose "Edit Constant List", then remove the "Yes" and "No" options and add the "YES" and "NO" options.
4. Find the Rejected_Requests_Project field in "ALMProject" record type, repeat the removing and adding operations in step 3.
5. Find the ALMObsolete field in "BTBuild" record type, repeat the removing and adding operations in step 3.
6. Find the Obsolete field in "ALMAdmin" record type, repeat the removing and adding operations in step 3.
7. Find the Obsolete field in "ALMResolutionCodeLabel" record type, repeat the removing and adding operations in step 3.
8. Find the Obsolete field in "ALMType" record type, repeat the removing and adding operations in step 3.
9. Find the Obsolete field in "ALMWorkConfiguration" record type, repeat the removing and adding operations in step 3.
10. Check-in the schema and upgrade user database.
11. Disable package editing to prevent future unintentional changes to the packages.
packageutil enablepackageediting -dbset <dbset> <username> <password> -disable <username>
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21693713