Comments on: Dynamic Data-Driven Drop Downs for List Properties

By: Carl Nordenfelt

Carl Nordenfelt — Tue, 25 Nov 2008 12:56:52 +0000

Hi
I think a way to avoid the static ServiceRegistry would be to inject it from the JSF component generator in the same way as the node is set for the constraint. This means that you will not have it declared in the Spring bean but dynamically set when JSF renders the component.

//Carl

By: Jean Barmash » Blog Archive » Implementing Cascading DropDowns For Editing Properties

Sun, 17 Aug 2008 13:41:29 +0000

[...] Jean Barmash Alfresco in the Real World « Dynamic Data-Driven Drop Downs for List Properties [...]

By: Peter Löfgren

Peter Löfgren — Thu, 14 Aug 2008 04:13:55 +0000

Hi Jean, and thanks for sharing.
As you mentioned, this not only makes it possible for dynamic drop-downs, but also for securing the data in them. Sometimes revealing just the existence of a property value can be to much, you may use your system so that you let subcontractors in and they should not know of each other ‘assets’. Or this new highly confidential project where you want to have the project id as one property.

I’ve added to your code so that the value property can be set dynamically
public void setListvalueProperty(String newlistvalueprop)
{
listvalueprop = QName.createQName(newlistvalueprop);
}
In your model definition then add next to the query parameter

{http://www.alfresco.org/model/content/1.0}name

Next was to make the query sort, you most likely want a list that sort in some way. I made it sort on the dynamic property above.

(in the getSearchResult() add )

SearchParameters sp = new SearchParameters();
sp.addStore(storeRef);
sp.setLanguage(SearchService.LANGUAGE_LUCENE);
sp.setQuery(finalQuery);
sp.addSort(“@”+this.listvalueprop.toString(), true);

ResultSet resultSet = getServiceRegistry().getSearchService().query(sp);
NodeService nodeSvc = getServiceRegistry().getNodeService();

List allowedValues = new ArrayList();
for (ResultSetRow row : resultSet)
{
allowedValues.add((String)nodeSvc.getProperty(row.getNodeRef(), this.listvalueprop));
}
(…)
Next is to figure out how to extend to have the description different than the stored value, let the users know what ‘XYZ’ stands for, and display ‘XYZ – Explanation’ in the dropdown but still store ‘XYZ’.

//Peter Löfgren

By: Alfresco dynamic list constraints example | ecmarchitect.com

Alfresco dynamic list constraints example | ecmarchitect.com — Wed, 13 Aug 2008 15:03:18 +0000

[...] Barmash has published an example showing how to do dynamic list constraints for Alfresco properties. His example accepts a Lucene [...]