LiveCycle ES provides a means to purge process data by using the LiveCycle ES Java API and web service API. Process data that is generated when a long-lived process is invoked can become too large, resulting in lower LiveCycle ES performance and the use of unnecessary disk space. It is good practice to purge process data when records are no longer necessary. For information about long-lived processes, see
Understanding processes.
When purging process data, you can purge a specific process or all processes that belong to a category defined in LiveCycle Workbench ES. For example, consider the processes shown in the following illustration.
If you purge process data that corresponds to processes under the Samples - LiveCycle ES category, then all process data that belongs to the MortgageLoan - Prebuilt and SecureDocument processes is deleted. To purge data that belongs to a specific process, specify the name of the process. For example, you can purge process data that corresponds to the SecureDocument process (shown in the previous illustration). Optionally, when purging process data, you can define a filter expression that only purges data that conforms to the filter.
When purging data, it is possible to purge just that process or the process and its child processes. A child process is a process that was instantiated as part of another process execution (for example, the parent process).
Include necessary files in your development project. If you are creating a client application by using Java, include the necessary JAR files. If you are using web services, make sure that you include the proxy files.
To programmatically purge process data, you create a Process Management ES client object to use the Process Manager Service API.
Condition filters can be combined using logical filters (AndFilter and
OrFilter) to build complex expressions. For example:
Using complex expressions is the only way to specify multiple process variables in one filter expression. The logical filters are created by using the
AndFilter (PurgeFilter left, PurgeFilter right) or
OrFilter (PurgeFilter left, PurgeFilter right) constructors, where left and right are other instances of a condition or logical filter.
After you include required library files, create a ProcessManager Client API object, and optionally define a filter, you can purge process data. When purging process data, you can specify the minor and major version of the process and specify whether child process data should also purged.