LiveCycle ES2.5 Glossary
LiveCycle ES2.5 Glossary
This glossary contains terminology definitions that are specific to documentation for Adobe® LiveCycle® Enterprise Suite 2.5 (ES2.5). These
terms may have different meanings in other contexts but have restricted meanings in this document.
accessible form
A form that users with disabilities or vision impairment can view and fill by using screen readers and other assistive technologies. See also
“tagged Adobe PDF form” on page 12.
Acrobat form
An Adobe PDF document, created in Adobe Acrobat® Professional or Acrobat Standard, that contains one or more form fields. The PDF
document may also contain other content. See also “PDF form” on page 8 and “XML form” on page 12.
(Adobe® LiveCycle® Designer 9) A run-time operation that can be added to a form. Previously, actions were added by writing scripts (such
as for clicking a button and getting a dialog box) but can now be added without scripting. When an action is created instead of a script, the
script is automatically created.
Action Profile
A property of forms and Guides. Action Profiles specify how forms or Guides and their data are presented to users. Action Profiles also
specify how data that users submit is processed before it is stored in process variables.
A scripting language based on ECMAScript, a standardized language for scripting. It is used in Adobe Flash® authoring, Adobe Flex®, and
LiveCycle ES2.5 for run-time manipulation of data and content. ActionScript® is executed by the ActionScript Virtual Machine (AVM),
which is built in to Adobe Flash Player. Features include asynchronous functionality, callbacks, and send/receive XML.
A generic term for work performed within a process, either by a person or a system. In Adobe LiveCycle Workbench 9.5, an activity is
represented by a rounded-corner rectangle.
Adobe certified document
A document that is signed with a specific Adobe root certificate. An Adobe certified document provides a strong guarantee as to the
authenticity and immutability of the document. See also “certificate” on page 2.
Action Message Format. A binary message format used to efficiently serialize ActionScript objects. Similar to the data portion of RTMP, the
AMF binary content is delivered in the body of an HTTP (or SSL-wrapped https) POST message.
A set of interdependent files that include a self-contained application that LiveCycle ES2.5 can run. Applications may include files such as
form designs, JavaServer Pages (JSP), HTML pages, SWF files, servlets, and images.
LiveCycle ES2.5 Glossary
approval routing slip
In the Managed Review & Approval Solution Accelerator 9.5, a PDF document that tracks the approvals or digital signatures of users that
approved the review.
A fundamental concept related to content modeling. Aspects allow the addition of functionality to existing content types. Aspects can have
properties and therefore, when added, they enhance content types with their properties. Behaviors and workflows can be attached to aspects.
A Java™ class, used with the Adobe LiveCycle Data Services 3.1 Data Management service, that contains methods that accept data changes
passed from a data adapter. An Assembler class allows Java objects on the server to be synchronized with ActionScript objects in the Flex
client application.
Note: The Assembler Java class differs from the Assembler service.
In the Correspondence Management Solution Accelerator 9.5, an asset is an individual element (text, image, list, condition or layout) that
can be combined with other assets to create letter templates. An asset can be used in multiple letter templates.
(Flex) The process of tying the data in one object to another. It provides a convenient way to pass data in an application. The <mx:Binding>
MXML tag is used to tie the data in one object to another with source and destination properties.
(Designer) The process of binding objects on a form design to data sources and schemas.
Contains a set of activities that a process executes either serially or in parallel.
building block
Building blocks are solution-specific product capabilities with clear technical documentation that explains how they can be used for
production applications. Building blocks are used by solution accelerators.
CAD assembly
(Adobe LiveCycle PDF Generator 3D 9) A hierarchy of CAD files that collectively represent a 3D object. The main file in the assembly is the
root for the hierarchy. The main file provides references to other files (part files, sub-assembly files) that contain 3D objects that are used in
the collective 3D object. The referenced files can also reference other sub-assembly or part files.
An electronic file that establishes your identity by binding your identity to your public key when conducting business or other transactions
on the Internet web. A certificate (or sometimes called a digital certificate) is issued by a certificate authority (CA). See also “Adobe certified
document” on page 1 and “credential” on page 4.
LiveCycle ES2.5 Glossary
click-through electronic signature
An electronic record of a user’s interaction with Adobe LiveCycle Process Management 9 tasks. Data stored on the LiveCycle ES2.5 database
can be used to determine a user’s action, and when and where the user took that action. client
The requesting program in a client-server relationship. A web browser, a Flex RIA client application, and Adobe Reader® are examples of
client applications.
An independent unit of production that plugs into the service container for purposes of deploying, orchestrating, and executing services.
From a physical perspective, a component is similar to a Java 2 Platform, Enterprise Edition (J2EE) module in that it represents the
underlying resources, metadata, and binary implementations of one or more services packaged together as a Java archive file. A component
must be installed before the deployment of any services that depend on it.
A component is the packaged set of concrete implementations (classes), resources, and metadata that are installed into the registry for
supporting the deployment and execution of one or more services.
confidentiality settings
Settings that determine the type of access a user has to a document, including the ability to print, copy, make changes, add signatures and
comments, and view offline. Confidentiality settings that administrators can set also include the ability to revoke document access rights
and switch policies.
The Flex client component that you use to receive messages from Data Services 3.1 Message Service destinations. See also “producer” on
page 10.
content action
A unit of work that is performed on a content node. Examples include adding an aspect, copying a content node, emailing a notification. A
content action can optionally have a number of conditions; an action condition is used to indicate whether an action can be executed.
content model
A collection of related content types and aspects. A content model may refer to definitions within another model. Each content model is
described in its own XML file and is identified by its defined namespace and name.
content node
Standard repository element of a content tree. A content node has associations with other content nodes to identify content and content
spaces. A content node contains significant metadata for automated content usage, such as search and manipulation. Content nodes can be
of various types (for example, a type of folder). Each type has its own metadata and behavior. Content and folder are two out-of-the-box
types. Content nodes that can contain other content nodes are technically called spaces.
content rule
A composite content action that has a rule type. A content rule can contain any number of content actions. Any number of conditions may
be combined in a single content rule.
LiveCycle ES2.5 Glossary
content rule type
Every content rule has a content rule type, which characterizes the types of events in the repository that will cause the content rule to be
triggered. When a content rule is triggered, the composite content action it represents is executed. A content rule type consists of a number
of content rule triggers.
content rule trigger
Relates to a repository policy and transforms the information that is acquired when that policy is activated in the information that is needed
to trigger a content rule.
content store
A one-dimensional perspective of the repository, aimed for a certain automated usage. Typically, the repository contains multiple
hierarchical perspectives of stored content nodes. Each perspective serves a meaningful automated goal according to defined protocol. A
content store reference consists of a store protocol (for example, archive, workspace, or system) and a store ID (for example, SpaceStore,
Any place where content nodes can be found and, optionally, written (for example, Data Dictionary, workspace). A content store does not
necessarily have to represent a physical location; it can also be virtual.
The file that contains a private key. (The corresponding public key is contained in a certificate.) A private key is what one principal presents
to another and is used to establish identity in decryption and signing operations. A credential is issued by an authentication agent or a
certification authority, and could be a digital certificate, a name and password combination, or biometrics, such as fingerprints. See also
“certificate” on page 2.
custom SWC file
A developer-created compiled library of custom ActionScript classes and assets. To use a custom SWC file in your Flex application, add it
to the library path before compiling.
design-time repository
A content store for assets that are checked into the server. These assets are stored in a database on the server where they are protected by
server-side permission access and available for associated developers to check out.
The logical representation in of a server-side object that you call from a Flex client application. Examples of destination types include Proxy
Service, Message Service, and Data Management Service destinations.
document package
A final form document (rendered in any format), which is made up of multiple form designs (XDP), such as a welcome package that contains
a welcome letter followed by insurance details and terms. Although more than one form design may make up the document, it is one output
(either a PostScript® file or a PDF file).
LiveCycle ES2.5 Glossary
The conversion of data to a format called ciphertext that cannot be easily understood by unauthorized persons. The conversion is done using
an encryption algorithm.
The mechanism for connecting to a service over a given protocol. Specifies how a service is to be invoked.
(Workbench) An occurrence during a business process. Events affect the flow of a process and usually have a cause (trigger) or an impact
(result). The three types of events are asynchronous, timer, and exception. An event is represented by a circle.
(Designer) An occurrence or action that can change the state of a form and, when the change of state occurs, automatically invokes a calculation or script that is associated with the event.
(Adobe LiveCycle Rights Management 9) An occurrence of a policy change. The Rights Management service tracks specific actions as they
occur, such as applying a policy to a document, opening a policy-protected document, and revoking access to a document.
fixed layout
A form, form design, or document layout that remains exactly as it was designed. The layout does not change to accommodate the amount
of incoming data.
flowable layout
A form, form design, or document layout that can expand or shrink to accommodate the amount of data being merged or entered by a user.
An electronic document that captures and delivers data. A person may add data to an interactive form, or a server process may merge a form
design with data to produce a non-interactive form. See also “interactive form” on page 6 and “non-interactive form” on page 7.
A calculation language similar to that used in common spreadsheet software that facilitates form design without requiring a knowledge of
traditional scripting techniques or languages.
form design
The design-time version of a form that a form author or form developer creates using Designer.
The entity in a process diagram that contains one or more branches and is used to control the diverging and converging of sequence flow.
In Workbench, a gateway is represented by a diamond shape.
LiveCycle ES2.5 Glossary
(Formerly known as form guide) An alternative view of a form that leads users through the form-filling process by using a wizard-like
Guide layout
Consolidates all the components that make up the end-user interface of a Guide, including navigation tools (tree, top tab, button bar), panel
layouts, and custom components.
interactive form
A form that a person can interact with and complete electronically both online (for example, PDF, Guide, HTML, or Flex application) and
offline (for example, PDF). See also “non-interactive form” on page 7.
interactive statement
In the Interactive Statements Solution Accelerator 9.5, an interactive statement is a PDF that uses a PDF navigator to present its content.
Interactive statements are a way of providing monthly statements and other information-rich documents to customers.
interactive statement template
In the Interactive Statements Solution Accelerator, an interactive statement template is a PDF navigator. However, instead of navigating the
content in a PDF Portfolio, it is a Flex application that is hosted within a PDF document.
An executable object. Such objects can be chained together and are executed in the order that they are added. An interceptor requests and
performs specific tasks.
(Installation Verification Samples) Used to validate an installation and also to test forms, data, and configuration files that are submitted to
LiveCycle ES2.5 services.
In the Correspondence Management Solution Accelerator, a layout is a form created in Designer. A layout defines the graphical layout of a
letter. It can contain typical form fields such as “Address” and "Reference Number". It also contains empty subforms that denote target areas.
See also “form design” on page 5.
LCA file
A LiveCycle ES2.5 archive file that contains a file along with metadata that can be used during application deployment. This file can be any
file that is stored in the resources view in Workbench.
letter template
In the Correspondence Management Solution Accelerator, a letter template defines the appearance and behavior of a letter. It contains previously-defined assets (layout, text, images, lists, and conditions).
LiveCycle ES2.5 Glossary
LiveCycle Service Discovery
An Adobe Flash Builder™ 4 plug-in that lets you connect to a LiveCycle ES2.5 server, introspect available LiveCycle ES2.5 services, and then
generate client-side code (ActionScript). Provides you with a simpler and more powerful way to build Flex applications (SWF files) that use
LiveCycle Remoting to call LiveCycle ES2.5 services.
LiveCycle Remoting
A Data Services 3.1 feature that lets Flex applications invoke service methods.
Message Service
Provides publish-subscribe messaging functionality for Flex clients. You can also use the Message Service to interact with third-party Java
Message Service (JMS) providers.
Modules provide the functional services that are required to build customer engagement applications that can be deployed to the
LiveCycle ES2.5 server.
An Adobe XML-based markup language used to declaratively describe user interfaces. MXML includes a rich set of tags that can also be
extended to create custom components. MXML-defined user interfaces are rendered by Flash Player, which provides an engaging user
non-interactive form
A form that users can view electronically. The form must be printed and filled by hand. A non-interactive form can also be prepopulated
with data by a server process, but users cannot change the data. A non-interactive form is designed for output to the screen or printer as
PDF, HTML, PCL, or PostScript. See also “interactive form” on page 6.
(Adobe® LiveCycle® Workbench 9.5) Operations are added to process diagrams to represent activities that are performed in processes. A
service is made up of one or more operations, whereby each operation represents an interaction with its related component. An operation
can be invoked through a number of endpoints, such as web services, Java API, remoting, email, or watched folders.
LiveCycle ES2.5 Glossary
package definition
In the Interactive Statements Solution Accelerator, a package definition file contains a list of the Asset Placement components in the project
and a list of the assets that those components display in the generated interactive statement. At design time, the Asset Placement plug-in
automatically generates the package definition file and automatically keeps the component list up-to-date. At runtime, the package
definition file generated by the plug-in is a build artifact and forms the base template for generating individualized package definitions. You
may have your own process for generating the package definition with specific assets for each end user or group of end users.
page assembly
A task that the Assembler service performs when it brings together the PDF page content of multiple PDF files.
Portable Document Format. A universal file format that preserves the fonts, images, and layout of source documents that are created on a
wide range of applications and platforms.
PDF form
Any PDF file that contains one or more form fields. A PDF form can be created in Acrobat or Designer. See also “Acrobat form” on page 1
and “XML form” on page 12.
PDF navigator
A PDF navigator is a component of a PDF Portfolio. The PDF navigator is a zipped package (.NAV) file that contains a Flex module and
associated navigator configuration files. As used by the Interactive Statements Solution Accelerator, the Asset Placement plug-in for Flash
Builder outputs a PDF navigator (.NAV) file.
PDF Package
A PDF document (the cover sheet) that has attachments (component files) but with added information (such as date, author, topic) that is
used to organize the component documents. When creating a PDF Package, you can provide a cover sheet or have Acrobat provide it for
you. The files in a PDF Package can be in various formats and created by using various applications.
PDF Portfolio
A cohesive, branded package that contains several files either of the same type or of various types. It also contains a PDF Portfolio Layout
that provides a user interface for viewing the documents in the portfolio.
PDF Portfolio Layout
A user interface for browsing documents that are contained in a PDF Package. This interface consists of an ActionScript program, resources
that the program uses (such as graphics and localized strings), and an XML file. These user interface pieces are compressed by using WinZip
or a similar program.
permission group
A convenient grouping of permissions, such as Read, which consists of ReadProperties and ReadChildren. A permission group that is
assigned to an authority for a particular content node is known as an ACL (access control list). A permission group that is assigned to an
authority regardless of the content node is known as a global permission.
LiveCycle ES2.5 Glossary
(LiveCycle ES2.5) Security settings applied to a file, for example, to restrict users from opening, editing, printing, or removing encryption
from the file. Permissions cannot be changed unless the user has the Permissions password.
(Adobe LiveCycle Content Services 9) A type of security that is identified by a string. A particular permission, such as ReadChildren, can
be denied or granted to an authority, a user, a group, an administrator, an owner. The children of a node inherit permissions from their
parents. Therefore, by default, the files in a folder inherit their permissions from the folder. Permissions that are set on a content node take
precedence over permissions that are set on the parent nodes. The inheritance of permissions may be turned off for any node.
A collection of information that includes document confidentiality settings and a list of authorized users. The confidentiality settings
specified in a policy determine how a recipient can use documents to which the policy is applied. A policy is created by using
Rights Management. See also “policy set” on page 9.
policy-protected document
A PDF document that has security permissions set by applying a policy using Rights Management, or a PDF form that has security permissions set by applying a policy using Acrobat.
policy set
Represents a group of policies that have a common business purpose. See also “policy” on page 9.
In the Correspondence Management Solution Accelerator, a postprocess is a LiveCycle ES2.5 process that you bind to a letter template. The
postprocess is invoked when the final correspondence is submitted. A postprocess can perform actions such as archiving, printing, or
emailing, and it can use any of the services available in Workbench.
prepopulated form
A form that is displayed to the user with some or all fields automatically populated with data.
print template
In the Interactive Statements Solution Accelerator, a print template is the printable statement design. The print template and the XML data
are rendered into the final printable statement that is included in the interactive statement.
printable statement
In the Interactive Statements Solution Accelerator, a printable statement is a paginated, printable static representation of the interactive
statement in PDF that you can attach to an interactive statement. Including a printable statement in addition to the interactive statement
allows customers to print a copy of the statement for their records or to meet compliance requirements.
promotional assets
In the Interactive Statements Solution Accelerator, promotional assets are used in an interactive statement. For example, images, SWF files,
and PDF files.
promotional content
In the Interactive Statements Solution Accelerator, promotional content is placed in the interactive statement by the Asset Placement service
based on the assets referenced in the package.xml file.
LiveCycle ES2.5 Glossary
Represents a business process that is automated using LiveCycle ES2.5. Workbench is used to model a business process at design time. At
run time, a process is a service that runs on the LiveCycle ES2.5 server.
The Flex client component that you use to send messages to Data Services 3.1 Message Service destinations. See also “consumer” on page 3.
remote object
A Flex client object that you use to call methods on server-side objects.
An action in which a form design is merged, possibly with data, to display a form as a PDF, a Guide, an HTML, or a SWF file in a web browser
or web application.
The storage system for LiveCycle ES2.5 assets. A database that allows objects to be versioned and referred to by an ID or a URL
restricted document
A PDF document that has password security restrictions (permissions) that prevent the document from being opened, printed, or edited.
In the Managed Review & Approval Solution Accelerator, a review is an instance of a review template. The review encapsulates "review" and
"approval" stages and details of a review and approval process.
review template
In the Managed Review & Approval Solution Accelerator, a review template is a prebuilt template for carrying out the review and approval
workflows. It defines the stages of the review, users that participates in the review and also defines the meta data that facilitates the review
review tracking sheet
In the Managed Review & Approval Solution Accelerator, a review tracking sheet is a PDF document that tracks the users and decisions of
users involved in the review stage.
Rich Internet Application. A web application that has the features and functionality of a traditional desktop application. An RIA typically
transfers the processing necessary for the user interface to the web client but keeps the bulk of the data on the application server.
Rights credential
A digital certificate specific to Adobe LiveCycle Reader Extensions 9 that enables Adobe Reader usage rights to be activated in the PDF
documents produced. The Rights credential is used to extend the usage rights of each PDF file that is processed by Reader Extensions.
LiveCycle ES2.5 Glossary
rights-enabled document
A PDF document that includes security extensions that allow Adobe Reader users to perform such tasks as fill forms, add comments, and
sign documents.
RPC component
Remote Procedure Call component. In a typical Flex application, an RPC component sends data as input to one or more RPC services. When
an RPC service executes, it returns its results data to the RPC component that made the request. Flex RPC components are based on a
service-oriented architecture (SOA). Service adapters bridge Flex destinations to back-end systems.
script fragment
A piece of FormCalc or JavaScript code that can be reused across multiple XDP files.
security handler
A software module that implements various aspects of the encryption process and controls access to the contents of the encrypted
document. This module contains all security logic, such as how to sign and verify signatures.
A software application that runs on the LiveCycle ES2.5 server that executes operations upon a client’s request. See also “component” on
page 3.
service configuration
Multiple versions of a service.
solution template
A solution template is a reference implementation that highlights a business use case that is implemented by a given solution accelerator.
Used to store and organize content items and other spaces. A space can hold any type of content. A space and its contents can be moved or
copied from one location to another. Each space has an owner who can make any changes to the space or its immediate contents. A space
can have content rules defined for how the content that enters, exits, or currently resides in a space is managed. A smart space is a space that
has rules applied for automatic content actions.
space template
A template that has predefined content rules and subspaces that can be used to create a new space.
supporting documents
Documents that help the reviewer carry out the review of the document. For example, if a reviewer is to review an engineering drawing, a
supporting document could be a drawing standards document. As used by the Managed Review & Approval Solution Accelerator,
supporting documents appear as attachments to a task assigned in Adobe® LiveCycle® Workspace 9.
tagged Adobe PDF form
A form that includes a logical structure and a set of defined relationships and dependencies among the various elements, as well as additional
information that permits reflow. See also “accessible form” on page 1.
trusted identity
An identity that is recognized by the associated certificate. Only specified trusted identities can sign a form.
An installation option that automatically installs and configures the LiveCycle ES2.5 product files, an application server, and a database, and
deploys the product files to the application server. After you perform a turnkey installation, LiveCycle ES2.5 is ready to use.
usage rights
A set of rights that extend the functionality of Adobe Reader and allow users to perform such tasks as save forms with data, add comments,
and sign documents.
user story
A narrative that describes the user experience, requirements, and benefits of using a solution accelerator.
web script
Opens Content Services and makes it accessible to other tools and applications. Web scripts can generate dynamic feeds from documents
that are managed within the Content Services repository. Each web script is bound to a HTTP method and custom URL. The two types of
web scripts are data web script and user interface web script.
An HTML page that embeds the SWF file for a Flex application. Wrappers can also be responsible for express installation and browser
XDP file
XML Data Package. Designer saves a form design as an XDP file that can be rendered as a Guide, a PDF, an HTML, or a SWF file.
XML Forms Architecture
A representation of the underlying technology beneath the Adobe XML forms solution. It enables the construction of robust and flexible
form-based applications for use on either the client or the server.
XML form
A PDF form that conforms to the Adobe XML Forms Architecture. XML forms are typically created in Designer. The originating form
design can have the file name extension .xdp or .pdf. See also “Acrobat form” on page 1 and “PDF form” on page 8.
LiveCycle ES2.5 Glossary
© 2010 Adobe Systems Incorporated and its licensors. All rights reserved.
Adobe® LiveCycle® ES2.5 Glossary
October 29, 2010
This document is licensed for use under the terms of the Creative Commons Attribution Non-Commercial 3.0 License. This License allows
users to copy, distribute, and transmit the glossary for noncommercial purposes only so long as (1) proper attribution to Adobe is given as
the owner of the glossary; and (2) any reuse or distribution of the glossary contains a notice that use of the glossary is governed by these
terms. The best way to provide notice is to include the following link. To view a copy of this license, visit
Adobe, the Adobe logo, Adobe Reader, Acrobat, ActionScript, Flash, Flash Builder, Flex, Flex Builder, LiveCycle, and PostScript are either
registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Java is a trademark or
registered trademark of Sun Microsystems, Inc. in the United States and other countries. Linux is the registered trademark of Linus Torvalds
in the U.S. and other countries. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries. UNIX is a trademark in the United States and other countries, licensed exclusively through X/Open
Company, Ltd. All other trademarks are the property of their respective owners.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
LiveCycle ES2.5 Glossary
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF