|
LiveCycle 7.x workflows used Init-Form variables to identify
the forms that initiate the workflow. LiveCycle ES processes, however,
did not use Init-Form variables; instead, a form variable was defined
as the input variable and specifies the form to be used.
When a LiveCycle 7.x workflow is upgraded to a LiveCycle ES-equivalent
process, the functionality of the Init-Form variable is converted
to an input form variable. (You must manually delete the Init-Form
variables from the process, as described in
Configuring invocation endpoints
.) The corresponding TaskManager endpoints
that you create are used to initiate the process and call the form
that is defined in the form variable. However, if the original LiveCycle
7.x workflow used multiple init-forms, multiple form variables are
created in the upgraded process. TaskManager endpoints can recognize
only one form to start a process and cannot differentiate which
input form variable in the process to use if multiple input form
variables are defined. By default, the endpoint will call the first
input form variable defined, and the resulting process may not run
as expected when it is invoked by using different forms.
To ensure that the correct input form is used, modify the process
so that an input form variable exists for each form that you will
use to invoke the process. The preferred way to do this is to do
these tasks:
-
Create a copy of the upgraded process so that you have
multiple identical processes (one for each of the input forms required).
-
Ensure that you have deleted the Init-Form variables and
created a TaskManager endpoint for each process.
-
Modify the input form variable in each of the processes to
reference the different form required.
|
|
|
