The Alfresco Community 3.4.c release includes language packs for French, German, Japanese, Italian, and Spanish. The language packs included with this version have been through an engineering QA cycle, but are still under linguistic testing.
Please note that the source localized files are encoded in ASCII and the special and accented characters are displayed using escape sequences. The source files have been renamed using the corresponding locale for each language. If components such as RM, WCM, etc. are installed with the language packs, strings coming from these components will appear in English because these components have not been localized for this version.
The following files containing error messages have been left in English for this release:
The DocLib Portlet surfaces DM capabilities in portals via a Share based Document Library Portlet.
Web Quick Start
The Web Quick Start is a sample application built on the Alfresco platform. It provides an end-to-end WCM example with an authoring and publishing environment using Alfresco Share and a web application built using Spring MVC, Spring Surf, and OpenCMIS. The web site is delivered dynamically using Alfresco as a CMIS runtime.
The primary design goals of the Web Quick Start are to illustrate the power of the Alfresco platform in an easy-to-install package and to provide developers with a strong starting point for their Alfresco implementations. Both of these goals are fundamentally aimed at getting both business people and developers up and running with the Alfresco WCM platform in as short a time as possible. The Alfresco core product has not been changed in any way, just extended by plugging in content model, behaviours, and workflows using the many standard hooks provided by the Alfresco product.
3.4.c adds the following additional features to the Web Quick Start:
Apache License â€“ The Alfresco Web Quick Start is now licensed under the Apache License Version 2.0. Please see Web-Quick-Start-License.txt located within the web application META-INF directory for further information.
Share Dashlet Enhancements â€“ The Web Quick Start Share dashlet now provides the ability to choose which sample content to import. Currently two samples are available for Government and Finance. Currently both samples are identical in functionality however differ with regards to images and section headings. This provides an example of how developers can package and import their own sample site data.
Asset-by-asset template override - 3.4.c includes ability to specify the template to be used for an individual asset. This is useful when you would like most assets in a particular section to be rendered in a particular way but need one or two to look different. See Web Quick Start Enhancements for further details.
HTML Rendering Engine â€“ 3.4.c now includes an HTML rendering engine that will extract the contents of Word (.docx) files and produce HTML. Supported features include:
Normal header styles are mapped to HTML h# tags
Custom header styles are mapped to HTML h# tags, and a class of the style name is applied
Custom paragraph styles are mapped to a class applied to the paragraph
Bold and Italic
Tables (including nested tables)
Page Headers and Footers as paragraphs with an appropriate style
Alfresco Web Editor (AWE) Enhancements
Content creation and deletion
Additions to the AWE allow for new content to be created and for current content items to be deleted. The create process provides an additional marker icon that allows the user to effectivley 'create another piece of content like this one'. This provides a simple mechanism for non-technical users to create new content without the complexity of setting an attach point and content type.
AWE Freemarker support
The Web Quick Start provides an example of using the AWE with FreeMarker templates.
Redesigned and Extensible Header
The Share header bar has been redesigned to provide improved usability, better localization support and configuration based customization.
New simple search capabilities allow searching of the entire Repository from within Share. Sorting is configurable and there are also related improvements to searching within the People Finder component.
New advanced search capabilities offer search forms for end users and extensive customization options for developers.
End users can search based on custom document types, aspects, and their properties.
Developers can define custom search screens for application-specfic searching using Forms
Comprehensive workflow capabilities including:
Start workflows with/without attachments
Multiple task attachments
New Inbox Dashlet
Start Workflow, filter tasks by priority, due dates, personal & pooled tasks, and view & edit tasks actions
My Tasks Page Component
Filter tasks based on due dates, priorities, or assignee
Edit, view task, and workflow actions
View/Edit Tasks Details Pages
Workflow Details Page
Current task owner, due date, and status
Actioned by, outcome, event date/times, and comment history
Workflow Management - Workflows I've Started
Filter tasks based on due dates, when started, priorities, and workflow type
Share your status with other users....what are you working on now?
User status information viewable by other users via users profile, site members lists and more.
Improved Options for Site Visibility
You can control which users can see public Sites to support an Extranet use case. For example, allowing public sites to be visible to employees but not external users. Refer to Site_Service_3.4 for more details.
Site create permissions
By default, any user can create Share Sites. It is possible to control who has permission to create sites by changing the permissions applied to the sites folder. Refer to Limiting site creation permissions for more detail
Replication Job Management
A new Share administration console component for creating and managing replication jobs including the transfer payload (folders and documents to transfer), repository server to transfer to (transfer target) and replication schedule.
Several enhancements have been made to the Forms Engine, including new controls, an enhanced association picker and new set templates. Refer to the Forms What's New section for more details.
Since the first version of Alfresco, Hibernate has been used to provide the object-relational mapping and data access layer against the underlying relational database. Hibernate proved invaluable in enabling us to rapidly build the early versions of Alfresco.
As the size of Alfresco deployments has grown, it has become more important for Alfresco to control the interaction between the application and the underlying database to ensure this is optimized for our use cases. Alfresco started making use of Apache iBatis in 2008 and has gradually moved away from using Hibernate; in 3.4 the change has been completed. The approach provides us with a much greater level of control over the data access layer so we can ensure it continues to scale and support the very large repositories and enterprise deployments that Alfresco is increasingly seeing.
Developers are isolated from the implementation details of the data access layer. These changes do not affect the existing APIs, query capabilities or other features. There is no need to migrate existing customizations or extensions that use public Alfresco APIs.
The Replication Service is a new service introduced into Alfresco 3.4 to control Replication Jobs. Replication Jobs determine what needs to be replicated and when and then calls the Transfer Service introduced in Alfresco 3.3 to allow spaces (folders) and content to be automatically copied between distinct Alfresco repositories. Replication Jobs can be triggered according to a schedule, on-demand, or by actions.
Content replication is designed to assist geographically distributed deployments where performance may be affected by network latency or bandwidth limitations.
For content consumers replication provides:
Fast access by serving content from local servers
High availability - removes the single point of failure
For network administrators replication provides:
Reduced network overhead
By default, replicated content is read-only on the target repository. This ensures the integrity of the content is not compromised by uncontrolled updates. A option is --draft, created from copy of 3.4b, need validation from Mike and Ben.
provided in the Alfresco Share user interface for users to navigate to the content's source repository to make any updates.