|
In LiveCycle, you use applications for implementing a solution.
Use applications as a container for assets such as form designs,
fragments, images, processes, event types, DDX files, Guides, HTML
pages, and SWF files. Applications serve two purposes:
-
As a container for the related assets that are required
for managing an application life cycle. For example, you have a
Loan Approval application that contains a form design, a company
logo, fragments that the form design uses, and the loan-approval
process.
-
As a container for unrelated assets that are used in different
applications and by various developers. For example, you have a
project that contains the different form designs your organization
uses and the images these form designs use.
Additionally,
several features are now applied at the application level, for easier
management, rather than on a resource or process:
-
Versioning
-
Deployment to the LiveCycle server (development environment)
-
LiveCycle archive files
New work patterns
The introduction of the Applications view
changes how you accomplish many tasks in Workbench 9. Many commands
and features have been moved from other views to the Applications
view. For example, you no longer create process categories or process
versions. Applications provide the organization and versioning of
assets.
The following table lists the commands that have
not changed since LiveCycle ES Update 1. Commands that are not listed
are either moved to the Applications view or are removed.
|
Location
|
Command
|
|
Processes view (right-click a process version)
|
-
Activate/Deactivate
-
Export Process
-
Properties
-
Upgrade to LiveCycle ES
|
|
Events view
|
Display by group
|
|
Events view (right-click an event type)
|
-
Activate/Deactivate
-
Export
-
Properties
|
|
Resources view
|
|
|
Resource view (right-click a folder)
|
Access Control
|
|
Resource view (right-click a resource)
|
-
Relationships
-
Access Control
-
History
|
LiveCycle archive files and custom components
LiveCycle archive
files no longer automatically include custom components that your
processes use. Instead, indicate that you want to include the component. Otherwise,
the component is not included in the archive. (See
Creating archive files
.)
|
|
|
