If you install the WorkFlow SDK, there is a document under Documentation that explains all the settings. This is a subset:
To add the Form Server Render Form component to your workflow:
1. Drag the Form Server Render Form component from the Components palette to your workflow.
2. Click the General tab. In the Name box, type a name to identify this component in your workflow.
3. (Optional) In the Description box, type the description of the component.
4. Click the Input tab. In the Form Query box, type the Uniform Resource Identifier (URI) component (no
protocol or schema) of the form to be rendered. This URI is appended to the Content Root URI value to
form an absolute reference to the form. For example, type:
Forms/myForm.xdp
Forms/myForm.pdf
5. (Optional) In the Form Preference box, type the output format of the form. The default value is AUTO.
For details about form preferences, see Selecting a form preference on page 11.
6. (Optional) In the Options box, type the rendering options, such as locale or character set. Use an &
(ampersand) to separate the options. For example, type:
{$ TaggedPDF=false&PDFVersion=1.6&CharSet=UTF-8 $}
For details about rendering options, see Selecting rendering options on page 12.
7. (Optional) In the User Agent box, type the user agent that identifies the application that will be used to
display the form. The default value is Mozilla/3.x. This property specifies the HTTP header
User-Agent that provides information about the target device. A target device is a client application,
such as a web browser. This value takes precedence over what may exist in environment variables.
You can retrieve this value from the JSP/ASP environment.
8. If you have an application server that will incorporate services from LiveCycle Forms, in the
Application Web Root box, type the servers root location. This root location is combined with the
Target URL to form an absolute URL to access application-specific web content.
9. (Optional) In the Input XML Data box, type the location of the XML file that contains the information to
use to prepopulate the form. This data will be merged with the form during rendering. For example,
type:
C:\input.xml
Alternatively, you can use a form variable to retrieve data from a previous step in your workflow. Form
variables are primarily used to store the data from the forms submitted to LiveCycle Workflow Server.
The data can then be accessed at run time. For example, type the following expression:
serialize(/process_data/formVar/form-data/data/*,false)
The serialize function takes the data from the form variable. In this example, the formVar process
variable represents the Form data type. The false parameter encodes the data in UTF-8 in the XML
code. You can optionally set this value to true if you do not want UTF-8 encoding. For more
information about the Form data type, how it works with Adobe LiveCycle Form Manager, and its use in
a workflow process, see the Configuring Human Interaction chapter in Creating Workflows.
10. (Optional) In the TargetURL box, type the URL of the target device that will receive the posts from this
form. The target URL is inserted into the transformed output invoked during a Submit operation. For
example, type:
http://servername:8080/fm/processFormServlet?action=011. In the Content Root URI box, type the URI of the AppStore to specify the absolute reference to a
physical repository from which the content (forms, images, or scripts) will be retrieved. For example,
type:
file:///c:/forms
xappstore://hostname
This value is combined with the Form Query value to form the absolute path to the form to be
rendered.
Note: The Content Root URI is often constant across many user applications and can be set
administratively to a persistent value.
12. If you are using relative paths (such as ../images/graphic.jpg), in the Base URL box, type a base
URL to identify the HTTP equivalent of the Content Root URI. This URL is required for transformations
that include HREF references to external dependencies such as images or scripts. When a dependency
path is absolute, this parameter is ignored; otherwise, the dependency path is combined with the Base
URL. For example, type:
http://hostname/forms13. If required by the server on which LiveCycle Forms is installed, in the User Name box, type a user name,
and, in the Password box, type a password. If the password is encrypted, it must be Base64 encrypted.
For more information, see Encrypting passwords on page 6.
14. Click the Output tab. In the Output Document box, click the ellipsis button, and then select the
variable that will receive the new document. The data type for this variable must be document.
15. In the Page Count box, click the ellipsis button, and then select the variable that will receive the page
count. The data type for this variable must be integer.
16. In the Page Number box, click the ellipsis button, and then select the variable that will receive the
page number. The data type for this variable must be integer.
17. Click OK.
Jasmin
