|
In
LiveCycle, an application is a container for storing assets
that are required for implementing a LiveCycle solution. Examples
of assets are form designs, form fragments, images, processes, DDX
files, form guides, HTML pages, and SWF files. You can use applications
for 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 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 various form designs your organization
uses and the images these form designs use.
When you first create an application or an asset, it is stored
in a folder on your local computer. To make it available to other
application developers, check it into the LiveCycle repository.
The applications and assets that are stored in the LiveCycle repository
are available to developers on an as-needed basis. This means that
a process developer can easily access any components that are required
to develop a LiveCycle application.
When the application is completed, you can deploy it directly
from the Applications view so that it can be invoked. The deployment
process can be repeated as required to update the application in
the repository.
|
|
|
