|
Data models can be configured so that when they are deployed,
the data types that they define are available to processes. These
custom data types simplify the integration of applications built
using Flex technology (SWF files) and LiveCycle applications:
Processes can include model-based variables as input
or output data.
Flex applications can provide values for the input variables
when invoking processes.
Flex applications can save the values that processes produce
when completed.
Data models simplify the integration because
their data types can comprise subtypes. For example, a custom data
type is comprised of five string values. In the process, only one
variable is required to store data of that type. Without the custom
data type, five string variables are required.
After the data
is passed to the process, the process can use the data to populate
forms or Guides, or for any other purpose. (See Using data models with form and Guide data.)
Note: Use
XML variables to populate forms and Guides. Variables that store
values of model-provided data types cannot be used to populate forms
and Guides that are based on the same model.
Data types
that contain subtypes behave in Workbench in the same way as other
complex data types. Use XPath expressions to access data that the variables
contain.
To enable Flex applications to invoke a process,
enable one or more programmatic end points for the Default start
point. For example, to use the process web service to invoke the
process, enable the SOAP end point.
|
|
|
