
Content Fusion, Enable’s web content management offering, is used by over 200 organisations to maintain their internal / external web content. A summary of some of the key features are as follows:
Rich set of controls, each optimised to the handling of different content types. The standard set includes:
A Workflow system that allows any number of schemas to be created, which can each have any number of steps, which can each have an 'action.'
Actions include: send alert, archive, capture version, delete, distribute content, email reminder, release ownership, remove from live, retain control, retain and capture version, return to submitter, save draft. Any workflow schema can be bound to any element within the CMS.
In addition, each user has their own task list showing them what they need to do. There is a workflow overview report detailing where each content item is in the workflow, and an audit trail showing for each step of each content item: date/time, who, description of step executed and comments.
Comprehensive permission model for elements and instances. The ability to set: no access, read and edit access for each.
Version control that can be switched on for any element. Doing so will allow the content manager to ‘capture’ a version at any point from that element down to the end of the element structure. Each version is saved with a time/date stamp, version number and name of user who captured the version. It is possible to preview any previous versions and roll back. The capture of the current version can be automated as part of the execution of a workflow step.
A preview facility to allow any content items to be previewed in the context of the website design at any point during content creation and/or editing.
Event rules - the automatic publishing, archiving and removal of content from the live website at pre-set dates. Also includes content update reminders where a date or time period can be set to review content for updates. The content manager will then be notified.
Optimised publishing engine and XML caching - generates the XML rapidly and caches it to maximise front-end stability.