Restricted Change Request values are not working - why?Description<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms In Standard Change Properties, when a user selects various Change Request fields to be restricted from selection via the Restricted Change Request values selector, the fields selected to be restricted still display when an ITIL User selects to add a new template field under the Default Change Request values. Release London Patch 4, Hot Fix 2 Cause This was a Product Defect (PRB), and the implemented fix prevents the user from requesting approvals via the "Request Approval" UI Action. Resolution Per the above cause, if a restricted field is selected, submission of the Proposed Standard Change Template is blocked and the following error message is thrown: The following "Change Request values" are not allowed to be set in a template" The error message is followed by however many forbidden selected values there are, with each individual value labeled as "undefined".For example, if a user selected two restricted values, the error message would read, "The following 'Change Request values' are not allowed to be set in a template: undefined, undefined" Therefore, the behavior experienced is expected per the fix implemented through the PRB.