Search results for author “Rich Hart”
Alfresco Online Data RoomsOur online data room solution came about from requirements gathered from past and present customer engagements.
- Alfresco Transfer Service 3.3.3 - Getting Started
As part of a customer requirement to expose publications to multiple Alfresco repositories, along with a recent version upgrade to Alfresco 3.3.3, we decided to implement and extend the Alfresco Transfer service. Initial findings found it very easy to get going, and soon had an out of the box transfer service between two Alfresco instances configured with one class - the custom action, and a couple of spring context file changes to wire up the beans. What is particularly nice is that no configuration is required to turn on the transfer service at either the source or target end.
- Externalising Alfresco Configuration – One Step further
It is good practice to externalise configuration, to allow for changes to be more flexible, and remove the requirement of code changes, compile and redeploy.For example it’s not good practice to have a hard coded batch size which determines the size of batches of transfers between two Alfresco instances. Also, how often does it happen where a customer states they’d like everything to be batched in groups of x, to then, later down the line say they would now like it to be y.
- TinyMCE Extension for Alfresco
A recent customer requirement was identified in the Document Management side of Alfresco (as opposed to the WCM side). The requirement I refer to; was to embed content from the DM repository directly into new content being created via the WYSIWYG editor. After thinking about it for a little, I went about producing a solution that was based on the WCM version.
