It's all about the answers!

Ask a question

Problem with dependent enumeration in web browser


Luiz Almeida (23014674) | asked Apr 01 '14, 9:38 a.m.
Hello guys,

I have the following problem:

I created two enumeration attributes in a workitem: Area and Subarea.
In "Subarea" attribute I created a set value based on dependent enumeration.
In RTC client, when I change the value in "Area" combobox, an error notification is showed in "Subarea" combobox when the value selected is not applicable. This behaviour does not occur in web browser.

I'd like to know if this behaviour is possible in web browser and how I do it.

Also, I'd like to know if is possible a refresh in combobox "Subareas" when I change the "Area" combobox, so that combobox "Subareas" shows only the applicable values. (now, if i select a value in Subareas combobox and then change de Area combobox, the value I selected in Subarea remains the same)

Version of RTC is 4.0.3

Comments
sam detweiler commented Apr 01 '14, 10:00 a.m. | edited Apr 01 '14, 10:21 a.m.

 yes, this should work (sub refresh to selected list)..


to make this work, you must also set the sub attribute to be dependent on the Area attribute
here is how they do that for Category  --- see the dependencies box



2 answers



permanent link
Luiz Almeida (23014674) | answered Apr 01 '14, 4:24 p.m.
Sam,
I did this configuration. The problem occurs when i follow the steps:

1. I set a value in Area combobox
2. The Subarea combobox is updated
3. I select a valid value in Subarea combox
4. Then I change the value in Area combobx. In this moment, the Subarea combobox remains with the value I selected in step 3. In fact, the combobox has the content updated, but at the UI, the value selected is invalid.

The subarea apresentation is not refreshed when I set the value at the Area combobox.

Sorry my english...I am brazilian and I don't speak fluently.

Comments
sam detweiler commented Apr 01 '14, 4:32 p.m.

Very good explanation. I have seen this problem too.  since 3.0.1 on the web UI. 

it works the first time, not the second and on.  


Kristina Florea commented Dec 11 '14, 5:34 a.m.

I experience the same with 5.0.1. The dependent enumeration is not refreshed ... there is a little red x and the message is that the value is not valid. If is not valid, why show it?
Is there a fix for this available? a workaround? does it work as designed or is there a defect open?


sam detweiler commented Dec 11 '14, 7:31 a.m.

this is working as designed. the dependent enumeration does NOT create javascript to CHANGE the downstream UI selections..


permanent link
josue oropeza (1) | answered Jan 16 '15, 6:46 p.m.
 Hi, I hope the following tips can help you
1. Add a default element to the dependent enumeration, for example <Select a value>.
2. Get the id from "process configuration source" for this new value, in this case  "com.xxx.process.enum.literal.l25".
3. Add a calculated value on workitem/Attribute Customization.
add de next lines to the script 
//////////////////////////////
dojo.provide("com.workitem.custom.getValue.xxxxx");
dojo.require("com.ibm.team.workitem.api.common.WorkItemAttributes");

(function() {
    var WorkItemAttributes = com.ibm.team.workitem.api.common.WorkItemAttributes;

    dojo.declare("com.workitem.custom.getValue.xxxxx", null, {

        getValue: function(attribute, workItem, configuration) {
return "com.xxx.process.enum.literal.l25"
        }
    });
})();

////////////

4. in the type and attribute section of the workitem type, edit the dependent enumeration, on the field calculated value by selecting the recently created script 

Your answer


Register or to post your answer.