LiveCycle
ES2.5 supports processes that use QPACs in LiveCycle ES2.5 environments
that were upgraded from LiveCycle 7.x to LiveCycle ES, and then
to LiveCycle ES2.5 using LiveCycle Configuration Manager. New installations
of LiveCycle ES2.5 can also support processes that use QPACs if
the LiveCycle 7.x compatibility layer is also installed. In these
environments, the following support is provided for the processes
that are based on LiveCycle 7.x workflows and QPACs:
-
The processes continue to include the actions that are
based on LiveCycle 7.x QPACs.
-
The processes and QPACs execute and function as they did
in the LiveCycle 7.x environment.
-
The run-time state of process instances is preserved. Instances
of long-lived processes that were not yet complete when the environment
was upgraded can continue to execute in the LiveCycle ES2.5 environment.
-
Run-time data is persisted and remains available to client
software. For example, existing task history remains available to
LiveCycle Workspace 9 users, and process instance data continues
to be available for LiveCycle Business Activity Monitoring ES2.
-
When editing operation properties for a 7.x process in Workbench
9.x if an incorrect value is entered, an error message appears.
However, because this error message is displayed behind the Workbench
window, Workbench appears to be frozen. To alleviate this issue,
pressing Alt+Tab to move the error message to the front and click
OK.
Because processes that are based on LiveCycle 7.x workflows continue
to function in the upgraded LiveCycle ES2.5 environment, you can
upgrade them to LiveCycle ES-equivalent processes at any time.
Important:
LiveCycle ES2.5 is the last release to
support QPACs. To ensure future compatibility, processes using QPACs
must be upgraded using the Process Upgrade Tool that is available
in Workbench 9.5.
For information about any problems that may be caused due to
changes in functionality in LiveCycle ES, see
Handling upgrade problems
.
Using Avoka QPACs
If you are using processes that use QPACs
provided by Avoka, it is recommended that you obtain the latest
version of these QPACs from Avoka to ensure that upgraded processes
work correctly.
QPACs and LCA files
When you create an LCA file to move a process
to a different environment, QPACs are not included in the LCA. If
the target environment does not include the QPACs that the processes
in the LCA file use, you need to deploy the QPACs in the target environment.
Escalating tasks with the User service
The User QPAC that was used
with LiveCycle 7.x included the Escalate Tasks Which Have Been Previously
Saved Or Reassigned option. Tasks that were saved or reassigned
were escalated only when this option was selected.
The User
service for LiveCycle ES does not provide this feature. Tasks are escalated
regardless of whether they have been worked on (they have been saved)
or reassigned to another user since the task was initially created.
