|
Easy content contribution and collaboration.
Non-technical business users can collaborate and contribute content,
all through an easy, browser-based interface.
- MS Word to XML / HTML - Non-technical users can write
documents using MS Word, and Engenda XMLCE can then convert that
to high-quality XML when the document is saved. This process is
transparent to the document author, who, on later revisions, continues
to edit the Word document. Unlike other conversions, the generated
XML can be targeted at any given DTD.
- In-Browser HTML Editing - Engenda includes a powerful,
but easy to use WYSIWYG HTML editor that let's non-technical users
edit the HTML content directly within the browser.
- XML / HTML Editing via forms - Engenda include a browser-based
XML editor that uses HTML forms to edit the content. This allows
non-technical users to enter in structured data without having
to know the syntax of XML.
- Open Authoring - In addition to the above methods, Engenda
allows HTML and XML content to be edited in any third party editing
tool.
Browser-based Application. The
Engenda client application is entirely browser-based, meaning that
it is accessible from any desktop, anywhere in the organization.
No client-side plug-ins are used.
Flexible workflow engine. Workflow
is at the heart of any good content management of document management
solution. Engenda is unique in taking a task-based, process-driven
workflow model that encompasses the best aspects of business process
automation workflow system and collaborative systems. Combined with
the content repository, the workflow engine in Engenda provides
unparalleled content management capabilities. Some key features
are:
- Personalized workspaces - Each user gets a workspace
with tasks that they are actively working on, and tasks they can
work on. The actions they can perform is dependent both upon the
user, and the workflow state the task is in.
- Flexible routing - In addition to supporting arbitrarily
complex workflows, Engenda allows users to route tasks between
users and groups. This combines the rigor of business process
automation, with loose collaboration. People can collaborate efficiently,
and work in parallel.
- Workflow actions - Workflow states, and task attachments
can have any number of actions associated with them. These actions
provide the means for editing, and integration with other systems.
- Open, extensible architecture - The workflow engine is
100% Java, and has an extensive API for integrating custom actions.
- Simple to design - Workflow processes can be designed
using the Engenda stencil for Microsoft Visio.
- XML everywhere - The workflow process definitions, and
the task themselves, are stored as XML content within the system.
|
Content Repository - the heart of content
management. Engenda features a centralized content repository
built on our proven DynaBase technology, the result of 9 years of
R&D. Some key features include:
- Flexible metadata management - Metadata schemas can be
associated with any given data type. The schemas are used for
validation, and also for generating metadata editing forms.
- Indexing like no other - The Engenda content repository
features incremental, version-sensitive indexing of structured
text types such as XML and HTML. All content is indexed to the
tag level.
- Zero-admin - The database is embedded into the Engenda
application, and is for all purposes transparent to both the users
and the systems administrators. No extra licensing fees are required
for the database, nor personnel with specialized database administrator
skills..
- Sophisticated versioning - Differential versioning of
structured text types, along with the notion of "editions" makes
the content repository second to none in management services.
Edition and version changes propagate in real-time.
- Administrative tools - Tools for managing the repository
directly, and a full audit trail make the repository easy to manage.
- Integrated scripting - The repository features a built-in,
Visual-Basic compatible scripting language that can be used during
content delivery.
Templates - The key to re-use.
One of the largest problems with managing web sites is that the
look and feel changes over time, and that as new devices appear;
the number of media that needs to be supported grows. Engenda has
a sophisticated page composition and templating model that allows
content to be managed in a media-independent manner, and to be reused
at a very fine level of granularity. Engenda was the first content
management system to take such an object-oriented approach to site
construction.
The Engenda page composition model is built around three core components:
Re-usable Information Objects (RIOs), Templates, and Page Definitions.
RIO's are the smallest unit of manageable content in the Engenda
system. A RIO can be an object of any type representing some data
to be reused within the system. Typical RIO types are HTML fragments,
Images, and other HTML page components. RIO's can also represent
some code that is executed, such as code to invoke a Web Service,
or code to pull in data from an RDBMS.
In addition to promoting the re-use of content and separating content
from presentation, the Engenda template model is perfect for building
highly personalized sites, multilingual sites, or for building pages
and managing content that are to be hosted within a portal.
Comprehensive reporting. Track
efficiency of workflow processes, users, project teams, and more.
Access control. Flexible control
over security, content access rights, division of labor, etc.
Comprehensive media support.
Store and manage any file type within Engenda.
WYSIWYG real-time preview.See
what a dynamically assembled page will look like before it's published.
Standards-based extensibility.
Using Java and XML, all the major functional areas of Engenda can
be extended using Engenda's standards-based API.
|
|
