cancel
Showing results for 
Search instead for 
Did you mean: 

Constraint - allowedValues not called each time?

matjazmuhic
Champ on-the-rise
Champ on-the-rise
I have custom constraint programmed in java that does lucene search query (lists documents in some space)  and returns its results as allowedValues. I put this constraint on some property of my aspect and it all works fine till I add new document to that space. Next time I go edit meta-data the new document is not visible in dropdown. Seems like allowed values is not called each time I edit-metadata. (It worked fine in alfresco explorer though…)

Any ideas?
1 REPLY 1

croc
Champ in-the-making
Champ in-the-making
Though i don't understand you very well. I would suggest you use a different variable, not allowedValues. because it is used all over the system, and you might find that on the edit meta-data, it is been set to null or 0, which will obviously cause it to be empty.

Secondly, i think you need to call the same function you called when you search, because when you add and go to edit meta-data, you are going to another page, where i am not sure if you have the code that execute the logic to pull those documents.