You are on page 1of 10

Product #1

Product #2

Product #3

Product #4

CMS Features List

Ability to author content from Microsoft Word using Web Uses existing or new Word templates Derives document structure from the Word document basedtemplate on: Word definition Word formatting (e.g., bold, italics, etc.) Enables document to be reused in whole or in part Allows CMS-managed images to be inserted into document by non-technical users while in Microsoft Word Allows non-technical users to create in-line links to other CMS content Links created to other CMS content are created as dependencies in the CMS. Allows document properties (e.g., author, date, etc.) to be mapped to meta-data fields in the CMS. Provides the ability to search for content in the repository from within Microsoft Word, eliminating the need to use two different user interfaces. Enables check-in and check-out for a document as it is edited and saved. Can open existing documents under content management directly from within Microsoft Word. Allows document to be saved to different communities (content groupings) set up by the administrator. Enforces user authentication through the same mechanism set up for the CMS. Ability to author content from within browser-based forms Content input forms are completely configurable based on customer requirements. Forms support standard form controls: Drop downs, text areas, WYSIWYG HTML formatting, radio buttons, check boxes, calendar pop-ups, etc. Forms are accessible from anywhere depending on security/firewalls, etc. Forms are restricted based on users access rights. Forms are configurable based on workflow state of content being edited: Restrict editing of content on a field-by-field basis by workflow state Restrict viewing of content on a field-by-field basis by workflow state WYSIWYG editor is customizable based on branding standards (e.g., fonts, colors, etc.). WYSIWYG editor supports the creation of in-line links to other content. WYSIWYG editor supports the insertion of in-line images. Links created to other CMS content should be created as dependencies in the CMS. Forms are supported on latest Internet Explorer and Netscape browser versions.

Product #1

Product #2

Product #3

Product #4

CMS Features List

Ability to author content Microsoft Word using Web Forms support the from creation and use of related content (i.e., content stored in related tables). General (applies to all content) Maintains revisions of all content items. Allows rollback of revisions. Provides reporting of revision history. Allows for comparison of two revisions of content. Allows versions of content items to be created. Provides reporting of version history. Allows for comparison of two versions of content. Supports check-in and check-out of content items. Allows all content (regardless of entry point to the CMS) to be automatically allocated to a workflow step. When items are checked-out, other users can see and use, but not edit, content. Ability to migrate content from existing Web sites Existing Web sites can be crawled and content extracted from pages. Site crawling is configurable based on: Domains Page depth from specified URLs Exclusion of URLs Crawled results are viewable prior to content loading. Crawled results are modifiable prior to content loading. Content extracted from pages are definable based on: Type of content (e.g., image, PDF, text, etc.) Style used to define content (e.g., CSS, HTML format, etc.) Selected content can be mapped to customer content types. All interdependencies are mapped and maintained by the CMS such as: Links to images Links to binaries (e.g., PDFs, Flash, etc.) Links to other pages CMS can report on all content dependencies after site migration. Migrated site can be published in its pre-migration state. Content migration is repeatable and schedulable. Content migration tool can continually synchronize content between the source pages and the CMS.

Product #1

Product #2

Product #3

Product #4

Common CMS Questions

Assembly Can producers make layout changes through a browser interface? Can producers leverage content from across various communities to construct a composite page and apply a standard look and feel? Can producers access multiple workflow options for each item (e.g., reject back to contributor, advance to next level, direct publishing, etc.)? Can producers relate content to other content based on rules set up by the implementers? Can producers: Move content from one area of a page to another? Change the look/feel of individual content items in a page? Include any relevant content items on a page to increase its value to the viewer? Resort order in which content appears on the page? Remove areas of content from the page? Can producers navigate a virtual copy of the site and: Remove links to other pages? Edit content directly within the page? Content Organization Can content be organized visually in the CMS using a familiar paradigm such as folders? Can users drag and drop content between folders? Can content exist in more than one folder without requiring copies to be made?

Is it possible to create folder hierarchies that simultaneously (i.e., not limited to just one hierarchy for all content): Reflect site structure? Reflect physical folder structures? Represent different views of content (e.g., based on metadata)? Can content of folders be secured based on: Community? Role? User? Custom properties? Are standard views of content available, including: Current Inbox content? Current Outbox content? Content currently checked out to a user? Content viewed in the current session? Content recently viewed based on date? Is it possible to create custom views of content (virtual folders) driven by meta-data? Relationship Management Can all relationships (i.e., dependencies) among content in the CMS be managed and maintained by the CMS? Can managed relationships be created automatically by the CMS when content is: Copied? Versioned? Translated? Assembled (related to other content)? Moved/copied into folders? Related through in-line links when editing content? Are relationships viewable to assess the impact of changes to content? Can the CMS support the creation of new relationship types to meet custom requirements? Can the CMS use relationships to enforce:

No broken links across all channels? No redundant copies of content? No redundant translations of content? Custom policy rules (e.g., all content related to a page goes live at once)? Are relationships definable as strong or weak, invoking appropriate email, workflow, or delivery actions? When relationships among content are changed can the CMS invoke appropriate delivery actions such as: Republish changed content Republish all related content Unpublish deleted/expired content

Product #1

Product #2

Product #3

Product #4

User Management and Security

Users and Roles Allows users to be added at any time. Allows user names to be changed at any time. Allows roles to be added at any time. Allows role names to be easily changed at any time. Allows users to be assigned to one or many roles. Supports access control lists. Roles and users can participate in multiple user communities (see communities section below) and maintain their standard access rights. CMS does not restrict the organization to a particular number of roles or type of roles. CMS supports distributed administration. Workflow Workflow adopts a flexible state-based model. Workflow processes are configurable based on existing business processes. CMS allows many workflow processes to be created, with no restriction on the number of states. Workflow processes can be modified after creation while content is in process. Workflow supports aging. Workflow supports ad-hoc assignment of content to users. Workflow can require a minimum number of approvers Workflow integrates with any SMTP email system for notifications. Each workflow can have a custom email message associated with it. Security

Integrates with LDAP (JNDI) connections. Integrates with standard Windows authentication mechanisms. Provides mechanisms to integrate with any backend database user authentication mechanism. Supports connection over HTTPS. Allows authentication based on IP address or IP address ranges. Communities CMS can segment content based on any organizational structure - e.g., line of business, geography, functional focus, etc. Users can be allocated to one or many communities. Community is the default basis for all searches. Users are able to save searches specific to a community. Users are able to choose whether a search is communityspecific or not. Browser interface is customizable based on community in the following ways: Access/restrict CMS functionality Define color scheme, logos, etc. Access/restrict access to content types Types of content are restricted based on community. Permissible workflows are restricted based on community. Permissible templates are restricted based on community. Permissible roles that have access to this community are restricted based on community.

Product #1

Product #2

Product #3

Product #4

Product Architecture, Standards, and Technology

Architecture CMS is able to leverage existing: Databases Application servers Dynamic delivery systems CMS integrates with existing email systems CMS does not restrict scaling process for delivery systems. What underlying databases can be used for the CMS repository? Is the repository used to store the actual content, meta-data or both? Standards CMS leverages all standard database systems used within the organization: Oracle SQL Server IBM UDB Sybase CMS provides the capability to pull content from external databases via standard JDBC / ODBC drivers. CMS does not dictate the use of proprietary adaptations of standard technologies for delivery or templating structures. The product is built on an application server platform What platforms are supported: J2EE?

.NET? Proprietary? What is the database connectivity method? UNICODE is supported. CMS is able to expose content as a Web service. CMS is able to consume Web services. Technology APIs / Web services are provided for specific applications Can other applications be launched from within the solution? If so, please list the applications. There is an import/export capability from external sources/applications for both content and meta-data. The CMS integrates with any third-party tools in the following categories: Document management Web authoring XML authoring Portal products with which the CMS can integrate: Plumtree BEA IBM SAP Other (specify) Supported Web servers: IIS iPlanet Apache

Other (specify)

Is replication and synchronization of content are possible ? How is fault tolerance achieved?

10