|
Note: Adobe is migrating Adobe® LiveCycle® Content Services
ES customers to the Content Repository built on the modern, modular
CRX architecture, acquired during the Adobe acquisition of Day Software.
The Content Repository is provided with LiveCycle Foundation and
is available as of the LiveCycle ES3 release. For information about
CRX content repository, see CRX Content Repository.
Adobe LiveCycle Content Services (deprecated) is a module that
offers content management services that let users design, manage,
monitor, and optimize human-centric processes.
Content Services (deprecated) provides the following services
to address organizational needs:
Library services for checking in and out documents, versioning,
auditing, and document cross-linking.
Search services for advanced distributed searches; combined
metadata content, location, object type, and multi-category search
of content categorization.
Automatic metadata extraction and categorization.
Transformation services for transforming content from one
format to another (for example, from Word to PDF).
Records management for retention and archival policies; file
plans to automatically classify and schedule records based on preexisting
plans and standardized structures, and type-based plans that automatically
classify and schedule records based on existing plans.
Records management for automated life-cycle management; schedule, content,
and metadata change activation based on simple rules.
Automatic document numbering: DOD5015.2 Administrator Templates
to support Department of Defense records and filing requirement
for metadata definitions, file plans, and functionality.
Content
Services (deprecated) provides several interfaces so that end users can
interact with the repository:
Adobe LiveCycle Contentspace (deprecated), which provides
a web interface for shared content spaces, discussion groups, and
searches. You can use Contentspace to conduct reviews for many types
of content by making PDF documents available to others to review.
Reviewers use the commenting and markup tools to add their comments
to the PDF document. They can then publish their comments in a shared
space where they can view and reply to comments from other reviewers.
The two types of reviews you can conduct: on-demand reviews
and structured reviews.
Office plug-in for easy access to content from within Microsoft
Office. The office plug-in lets you open, save, and edit documents
that are stored in Contentspace from Word, Excel, and PowerPoint.
You can browse content spaces and documents, view document details,
start a workflow, view tasks, and search for and check out documents.
You can download the plug-in from Contentspace at Company Home >
Client Plugins > Content Services Plugins location.
Shared folders for easily dragging and dropping content.
To
help customers develop their applications, Content Services (deprecated) includes
samples that customers can use to quickly understand the component
and develop an engagement application. Samples demonstrate how to
access, render, and submit forms through Contentspace, the client
web application. Other samples demonstrate how to protect content
and invoke generic processes.
Key featuresContent Services (deprecated) offers these features to
address organizational needs:
Process automation
Information protection
Document output
Process automationContent Services (deprecated) can leverage the LiveCycle
framework for business events by invoking processes based on content
events, such as adding new documents to the repository. Or, a process
can wait for content events to occur, such as a completed document
review. For example, an insurance company can receive thousands
of claims per day. When claims are converted to PDF documents, they
are routed to a central repository and stored in folders according
to the ZIP codes in the claims. The workflow is then triggered to
route the claims to regional processing centers. In this example,
the rules store the contents, and the content metadata was used
to drive the process of sorting the claims by ZIP code.
With Content Services (deprecated), users can attach files, such
as reports to a form, and submit the form. After the form is submitted,
both the data and the attachments are saved, and can be opened and
viewed in the same form layout. For example, a loan officer just
received a credit report and employment report for a client. The
loan officer opens the case form, attaches the reports to the form, and
writes notes to indicate that the material is complete. The loan
officer then submits the form. The form and the reports are then
ready for the final approver to view in the same form layout.
You can also access different types of forms or content in the
same portal. For example, an insurance agent can access both forms
for home insurance and forms for car insurance. Because all forms
have the same attributes, such as customer name, home address, and
ZIP code, the insurance agent can search for any attribute. The
insurance agent can also search car insurance forms by manufacturer
and model. The agent can search home insurance forms by type of residence
and number of rooms.
Using Content Services (deprecated), you can also search and
browse by association between processes and documents, and by process
and document attributes. For example, a court clerk wants to find
all outstanding processes that are related to a case file.The clerk
also wants to find all documents that are related to the case and
all other cases that are pending from the same plaintiff.
Process initiationDevelopers can invoke processes from Contentspace
and leverage Workspace for reviewing and approving content.
Form renderingDevelopers can prepopulate a form by using
content or metadata. For example, car insurance buyers log into
their accounts, open their renewal forms, and see that the form
has current records, including claim history. When buyers click
the claim history, they can see claim report files for each incidence
they previously submitted.
Also, developers can render forms
with attachments from Content Services (deprecated). They can update
the form with a new version of assets referenced during run time,
and keep form template versions consistent during the life cycle of
the process. For example, a loan manager opens a case from a task
list and checks attachments in the form, including an employment
history and credit report. The loan manager also knows that the
marketing team sent a letter that morning to announce the new company
logo that is effective immediately. The manager finds the form and
sees the new logo. The manager also receives email from the business
unit management team announcing that a new form layout is available
for new application cases.
Data storageContent Services (deprecated) stores metadata
in a database and content in a file system. Using a database immediately
brings in the benefits of databases, such as transaction support,
scaling, and administration capabilities. Content is stored in the
file system to allow for large content, random access, streaming,
and options for different storage devices.
ArchivingAdministrators
can archive content from completed processes in Content Services
(deprecated). For example, an administrator can create a final package of
documents that leverage the Assembler service or store multiple
documents in the repository. In another scenario, a mortgage application
is approved, and the final record is archived in PDF/A format. The
record is then placed in a records management system with a proper
archive policy.
Information protectionContent Services (deprecated) can leverage Rights Management
to automatically apply policies to content that is stored in the
repository. Using Rights Management, you can protect PDF documents.
The policies are applied transparently to content when the following
happens:
Content is retrieved from the repository and saved on
the local file system.
Content is sent by email to someone who is external to the
organization.
Content is placed on devices such as USB keys.
Document outputContent Services (deprecated) has prebuilt actions so that
developers can automatically convert documents to other formats
(for example, from Word to PDF).
Additionally, developers can configure actions to start short-lived
processes for the following purpose:
Assembling a set of documents within a shared space into
a package
Generating PDF files from three-dimensional content
Converting content to PDF/A format for archiving.
How Content Services captures contentIn a typical process that uses Content Services (deprecated),
a developer creates a LiveCycle application so that users can fill
and submit data to a repository for another person to review.
How Content Services secures contentWhen users open downloaded documents, they are prompted
to present their credentials. The Rights Management server enforces
the latest policies associated with the document and users. For
example, an automobile manufacturer wants to protect all engineering
specifications with suppliers even when the specifications are viewed
offline. The administrator can log in to the original manufacturer
system and apply permissions and rights to the specifications. Permissions
and rights determine whether the supplier can create, update, delete,
copy, or print the documents. The permissions and rights are applied when
suppliers open the documents from inside or outside the system,
or when online or offline.
Services included with Content ServicesContent Services (deprecated) includes these services:
Document Management
Node Service for managing metadata
Search Service for performing queries
For more information
about the services included in this solution component, see.Services Reference for LiveCycle
|
|
|
