Bug 1132885

Created attachment 929478 [details]
corrupted gdt

Description of problem:
My enumeration contains this line:
'EnumFact.fieldString4[fieldString1, fieldString2]' : '(new test.Helper()).getFieldString4("@{fieldString1}", "@{fieldString2}")'

In a guided decision table, I have condition columns for fieldString1 and fieldString2 already. When trying to add another for fieldString4, I can select the fact pattern, calculation type and field. When I try to select the operator, the pop-up for operators does not close (unless you choose 'no operator', 'is null', 'is not null'). A line is added for the default value, but the input element is missing.
If you close the operator pop-up yourself, add a header for the column and click Apply changes, the column seems to be created, even though the new column pop-up stays present as well.
Existing rows will get some value for the new cell, new rows are corrupted. Cells for the new column are not editable.
The column is not visible in the table definition part, the condition is not in the source either. Since it is not in the table definition part of the editor, the column cannot be removed.

Same thing happens for action columns.


Version-Release number of selected component (if applicable):
BPMS 6.1 DR1


Steps to Reproduce:
1. Create a dynamically loaded dependent enumeration.
2. Create a guided dt, optionally, add conditions for fields depended upon. Add some action columns. Add a row.
3. Start creating condition column for the depending field, choose fact pattern, field.
4. Try to choose 'equal to' operator.
5. Close the operator pop-up, set a header, click Apply changes.
6. Open the definition part of the editor, toggle open the condition columns.
7. Add another row.


Actual results:
In step 4, the pop-up remains present.
In step 5, no operator seems to be selected, new column pop-up stays present as well, but in the data table, new column appears.
In step 6, the new column is not visible in the definition part.
In step 7, the new row is corrupted beyond the new condition column.
Cells are not editable for this column, the column cannot be removed.


Expected results:
In step 4, the pop-up closes.
In step 5, operator is selected, no need to close the operator pop-up, new column pop-up closes as well.
In step 6, the new column is visible in the definition part.
In step 7, the new row is working.
Cells are editable, column can be removed.


Additional info:
For fields using dynamically loaded dependent enumeration, the default value does not make much sense anyway.