On almost every topic
Multiple Alfresco Share Configuration Files

Like you can have multiple models in your Alfresco back-end project, you can also have multiple Share configuration files in your Alfresco Share project. This makes your Share configuration more readable. You can have for example a separate Share configuration file for your workflow form configuration and one to configure your custom content model.

You only need to provide a context file that references the configuration files using Spring bean configuration, just like in your back-end project.

Let’s say I have a custom model for partner agreements in the back-end. The following example references an agreement-share-config.xml file with the Share configuration for my partner agreement content model and an agreement.properties file for the labels.

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>
<beans>
  <!-- Share Configuration -->
  <bean id="custommodel.config" class="org.springframework.extensions.config.ConfigBootstrap"
	init-method="register">
    <property name="configService" ref="web.config" />
    <property name="configs">
      <list>
	<value>classpath:alfresco/web-extension/agreement-share-config.xml</value>
      </list>
    </property>
  </bean>
  <!-- Resource bundles -->
  <bean id="example.resources"
	class="org.springframework.extensions.surf.util.ResourceBundleBootstrapComponent">
    <property name="resourceBundles">
      <list>
	<value>alfresco.web-extension.agreement</value>
      </list>
    </property>
  </bean>
</beans>

Save the file for example as agreement-share-context.xml in the Share web-extensions folder where the Share configuration and the labels file are also located in this example. If you add things like type or aspect visibility or advanced search forms do not forget to set the replace attribute to false, otherwise it might overwrite settings in other Share configuration files.

In this extensive post Mike Hatfield shares new features and changes in the design of Alfresco Share’s Document Library. I am especially happy that there are quite some features that will make customizing the Document Library easier. Currently you need to copy a lot of files and do stuff in multiple files in order to do customizations that are easy to do in the old Explorer interface.

For custom actions it looks like you still need to code the evaluator in Java. I have no problem with coding in Java, but I never understood this part. You can write custom actions in JavaScript, but in order to control when the action is active you need to write some Java. 

Share Extras provides a collection of easy-to-install add-ons for Alfresco Share 3.3 and 3.4, providing dashlets, document actions and more.