When you deploy an application that
contains a process, the process becomes a run time service that
is active and ready to be used with client applications such as
Workspace or other processes. (See
Deploying applications
.)
A process can have multiple active process versions associated
with the deployed versions of the application. If you activate a
more recent process version, subsequent new process instances will
use the most recent version. For example, if you activate process
version 1.0 and then activate 2.0, version 2.0 will be used to create
new process instances. However, if you activate process version 2.0
and then activate 1.0, process version 2.0 will still be used to
create new process instances.
You can invoke specific process versions only by using the LiveCycle
ES2.5 SDK. For information about invoking services using the LiveCycle
ES2.5 SDK or LiveCycle Remoting, see
LiveCycle ES2.5 SDK Help
.
Although you can modify an active process, remember that changes
can cause running process instances to stall. You must restart the
process instances by using LiveCycle Process Management 9 from LiveCycle
Administration Console. (See
LiveCycle
ES2.5 Administration Help
.)
Deactivate processes to make them unavailable to other processes
and client applications for invoking new process instances.
Important:
Deactivating a process that has outstanding
process instances causes the process instances to stall.
Deactivate a process:
In the Processes view, right-click
the process version and select Deactivate.
Activate a process:
In the Processes view, right-click
the process version and select Activate.
