Extending ACS 6 docker images After you have your ACS 6 local environment running, you’re probably thinking, this is nice, but I want to deploy my favorite amps, like JS console, Alfresco Governance Services (AGS), or even custom developed amps developed with Alfresco SDK.

Get ACS 6 EA on your local environment and start exploring new features, functionalities, and services.

By default Alfresco Content Services sets a default search limit, based on ACL checks to 1000 items. In order to search for more than 1000 items, you will need to do one of two things: However, before you make these changes, you should consider the use case behind your search requirement as a global change will allow users to run some very long accidental wildcard queries. If search is to

Loop through a result set, and execute an action on the objects. This example uses

Audit Replication of Alfresco Content Services (ACS) to Elastic Search using Spring Boot and Apache Camel. This project uses a Pull/Push integration model, where the ACS audit stream is pulled from the Rest API, and pushed over to Elastic Search. Once audit data is in Elastic Search, the Kibana UI can plug in to generate dashboards and charts based on audit actions inside of Alfresco Content Services.

Issue: Default Administrators identified in Alfresco does not give the user Administrative privileges Troubleshooting: Check that there isn’t any space in your comma delimited list of names. Recommendations: If you are using LDAP sync to synchronize users, an LDAP admin group should be defined, and this group should be nested under the ALFRESCO_ADMINISTRATORS group.

This post allows the user to override the Alfresco Solr configurations in the Alfresco SDK 3.0 TL;DR Override Tomcat’s Solr context configuration to point to custom Solr4 config dir. Copy default Solr configurations into this directory. Override new configurations as needed. Override Solr Context Configurations First we will add a config element in our main pom.xml that carries the property of our Solr configurations. <solr.config.home>${basedir}/src/test/resources/solr4</solr.config.home> Next we will edit the

Why upgrade SDK 3.0? Support for RAD (Rapid Application Development) and TDD (Test Driven Development) via HotswapAgent and JRebel Simpler SDK layout Jar packaging by default Support for Alfresco version 4.2 to 5.2 Integration testing webscripts TL;DR Update your pom.xml Remove all SDK modules, except for your jar/amp project modules. Update your Integration tests. Add integration-tests project module, and copy src directory. Re-organize your Integration tests into the integration-tests project module, and rename to

Using Alfresco One, it is very simple to extend the document structure that is deployed upon a Site creation. An automatic structure deployment can allow for a group of rules, folder structure and documents and other functionalities to be created within a site, when the site is instantiated. The nice thing about this functionality, is that it can be implemented from the GUI with the use of Rules, Scripts and Space Templates.

Sometimes you may want a work space or directory to be deleted when it becomes empty. For instance, you may have a temporary directory to share files for review or collaboration. The workspace or folder will remain available until the reviews and collaborations have been completed and the documents filed or moved into their designated spaces. Once the documents are moved out of the workspace, it would be best practice

Alfresco Activiti workflow form control override with upload functionality that makes use of the following concepts: Custom Action Executer Space Templates Modified / Extended Server side javascript webscript OnBootstrap Initializer Surf widget extension Surf components override Surf components widget reuse Alfresco Form Controls Dependencies Alfresco Enterprise 4.2.2 Maven 3.x JDK 7.x Installation git clone alfresco-workflow-upload cd alfresco-workflow-upload mvn install -Prun Usage Log into Alfresco Share with username admin:admin Start a new