My environments: Alfresco 5.2.x and above community edition, Alfresco Maven SDK 3.x, custom modeling
Say, I have employees list from which we choose to set for a property value
I am putting this in the model as a constraint
<constraints>
<constraint name="mcus:employeeNamesList" type="LIST">
<parameter name="allowedValues">
<list>
<value></value>
<value>Alen Blafer</value>
<value>Alexandel Rebok</value>
<value>Syriax Publit</value>
<value>Hraser Havier</value>
<value>Zmboe Vonatoo</value>
</list>
</parameter>
</constraint>And then later, I use this in a property definition
<property name=mcus:Employee_Name">
<title>Employee Name</title>
<type>d:text</type>
<mandatory>false</mandatory>
<index enabled="true">
<tokenised>false</tokenised>
<facetable>true</facetable>
</index>
<constraints>
<constraint ref="mcus:employeeNamesList" />
</constraints>
</property>The constraint is defined in the model itself. Now, tomorrow, the employee list changes for obvious reasons, I must redo the model. In which case, generating the AMP files again, uninstalling the old ones, and install the new ones.
Would this minimal change be good and not affect the internal working of this custom model?
Alternatively, can we give this kind of ("often-changing") dropdown constraints, only for the share UI tier, and not in the repository model?