ACLs to control 3 cascading dropdowns

[jlima]

Hi
I need to have a 3 level category hierarchy (Cat - SubCat - SubSubCat) and I'm using dropdowns to store all this data

I'm using ACLs to limit the items in the subCat according to the selected Cat
And also ACLs to limit the SubSubCats according to the selected SubCat

Everything is OK if the user selects:
1) a Cat
2) then a SubCat
3) and then a SubSubCat.

My problem:
in step 2) he can change the Cat without any problem and
in step 3) he can change the SubCat without any problem. But if he changes the Cat, the SubCat list gets updated BUT the SubSubCat DOESN'T (and still lists the items of the previous Cat/SubCat)

I've been trying to fix this by rearranging the ACLs order - No success;
and by placing the following ACL with an order lower to the above mentioned ACL's in an attempt to reset the 3rd level dropdown to an empty list prior to the evaluation of the ACLs that select the items for the 2nd level and the 3rd level - no success either

Code: Select all

$Self->{TicketAcl}->{'099-Clear_3rdLevel'} = {
    Properties => {  },
    Possible => { Ticket => { DynamicField_dfLevel3 => [''], }, },
};

Can anyone help me undestanding how ACLs are evaluated and why isn't this working?
thanks
jorge

[crythias]

This really goes against user experience. One level might make sense. MAYBE. but at some point you may want to consider whether a fuzzy search implementation may be a better tactic than click, scroll, click; click, scroll, click; click, scroll, click.

[jlima]

Hi Crythias
what do you mean by "fuzzy search implementation"?

[crythias]

fuzzy search = autocomplete

I realize need for labeling and organization, and it may not be able to be avoided. Consider how many places you've been asked to use dependent drop down fields *ever* and especially 3 layers deep. Consider also the click count necessary to complete your request and whether searching is possibly better than clicking from a list.

[jlima]

does OTRS supports autocomplete?
how can it be implemented?