Remember data list items are all Repository nodes, so you can use workflow, rules, etc. just as for normal content items.
Another question - will it be possible to automatically add entries in the data lists using Rules or Workflow? I would like to set up a list of ready made documents and would like to add entry in data list using rule from DocumentLibrary. And automatically fill out the entry form with relevant document attributes.
My responsibility is customer business needs not a programming, then sorry for questions that programmers may seem primitive.
Is it possible to create a hierarchical data list?'m not sure exactly what you mean here - could you give a concrete example please?
Preferably with the possibility of combining different data sets for the main element and next level element.
Yes, you can use a Rule that fires a script to do this. The script would create the correct type of node and populate the properties as required.Remember data list items are all Repository nodes, so you can use workflow, rules, etc. just as for normal content items.
Another question - will it be possible to automatically add entries in the data lists using Rules or Workflow? I would like to set up a list of ready made documents and would like to add entry in data list using rule from DocumentLibrary. And automatically fill out the entry form with relevant document attributes.
My responsibility is customer business needs not a programming, then sorry for questions that programmers may seem primitive.
Thanks,
Mike
Yes, although the documentation to do this isn't in place yet. It's a two-stage process…It certainly does look flexible, however I'm afraid some of your explanation has gone over my head. I'm comfortable enough working out the XML structure and I agree that it appears to be very very flexible, however no matter what I do, I can't seem to get the data lists to appear. I'm running the community version of 3.3g.
Essentially, you need to create a custom model type that represents your list. Make your your custom type is a child of dl:dataListItem. Currently the "duplicate" action only duplicates properties and associations directly applied to the custom list type, so you can't create deeply nested data structures just yet. The create form configuration to decide which type fields you want to appear in the Create, Edit and Data Grid.
It might look long-winded, but actually gives you lots of control.
I have the following two files in my extensions directory:-
membershipModel.xml
<?xml version="1.0" encoding="UTF-8"?>
<model name="scidl:memberDBModel" xmlns="http://www.alfresco.org/model/dictionary/1.0">
<description>Membership Database List Model</description>
<author>Rob Hillis</author>
<version>0.1</author>
<imports>
<!– Import Alfresco Dictionary Definitions –>
<import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d"/>
<!– Import Alfresco Content Domain Model Definitions –>
<import uri="http://www.alfresco.org/model/content/1.0" prefix="cm"/>
<import uri="http://www.alfresco.org/model/system/1.0" prefix="sys"/>
<import uri="http://www.alfresco.org/model/datalist/1.0" prefix="dl"/>
</imports>
<namespaces>
<namespace uri="http://www.yvr.org.au/model/membershipDataList/1.0" prefix="scidl">
</namespaces>
<constraints>
<constraint name="dl:memberType" type="LIST">
<parameter name="allowedValues">
<list>
<value>Single</value>
<value>Family</value>
<value>Junior</value>
<value>Complimentary</value>
<value>Life</value>
</list>
</parameter>
</constraint>
</constraints>
<type name="scidl:memberDb">
<title>Membership Database</title>
<parent>dl:dataListItem</parent>
<properties>
<property name="dl:memberNumber">
<title>Member No</title>
<type>d:int</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberSurname">
<title>Surname</title>
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberFirstName">
<title>First Name</title>
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberAddress">
<title>Address</title>
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberSuburb">
<title>Suburb</title>
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberPCode">
<title>Postcode</title>
<type>d:int</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberHomePhone">
<title>Home Phone</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberWorkPhone">
<title>Word Phone</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberFax">
<title>Fax</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberMobile">
<title>Mobile</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberEmail">
<title>eMail Address</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberType">
<title>Membership Type</title>
<type>d:text</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberDateJoined">
<title>Date Joined</title>
<type>d:date</type>
<mandatory>true</mandatory>
</property>
<property name="dl:memberDateResigned">
<title>Date Resigned</title>
<type>d:date</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberMedicareNo">
<title>Medicare No</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberMedicalConditions">
<title>Medical Conditions</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNoKSurname">
<title>Next of Kin's Surname</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNoKFirstName">
<title>Next of Kin's First Name</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNoKAddress">
<title>Next of Kin's Address</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNoKSuburb">
<title>Next of Kin's Suburb</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNoKPostcode">
<title>Next of Kin's Postcode</title>
<type>d:int</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNokPhone">
<title>Next of Kin's Phone</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
<property name="dl:memberNoKMobile">
<title>Next of Kin's Mobile</title>
<type>d:text</type>
<mandatory>false</mandatory>
</property>
</properties>
</type>
</model>share-config-custom.xml
<alfresco-config>
<config evaluator="model-type" condition="dl:memberDb">
<forms>
<form>
<field-visibility>
<show id="dl:memberNumber" />
<show id="dl:memberSurname" />
<show id="dl:memberFirstName" />
<show id="dl:memberAddress" />
<show id="dl:memberSuburb" />
<show id="dl:memberPCode" />
<show id="dl:memberHomePhone" />
<show id="dl:memberWorkPhone" />
<show id="dl:memberFax" />
<show id="dl:memberMobile" />
<show id="dl:memberEmail" />
<show id="dl:memberType" />
<show id="dl:memberDateJoined" />
<show id="dl:memberDateResigned" />
<show id="dl:memberMedicareNo" />
<show id="dl:memberMedicalConditions" />
<show id="dl:memberNoKSurname" />
<show id="dl:memberNoKFirstName" />
<show id="dl:memberNoKAddress" />
<show id="dl:memberNoKSuburb" />
<show id="dl:memberNoKPostcode" />
<show id="dl:memberNokPhone" />
<show id="dl:memberNoKMobile" />
</field-visibility>
</form>
</forms>
</config>
</alfresco-config>I've tried to extrapolate what is necessary by looking at the existing files and by watching this video, so I could very easily have gotten something wrong. I suspect I need to register the model, but I don't know exactly how to do that.
If you could give me a hint as to where I might be going wrong, I'd be most appreciative and will probably go and add a wiki page to ease things for others.
