General Concepts
The webMethods Content Service Platform (CSP) supports BPM suite integration for e‑forms created with the following applications:
Adobe LiveCycle
Microsoft Office InfoPath
Each of these applications enables you to create the following objects:
An e-form
template—one or more files that describe the form structure, appearance, and behavior. A template carries no user-entered form data (although sample data may be present).
An e-form
instance—a published version of the template, containing specific form data in a single file.
For more information about templates and instances, see the documentation for your e‑form application.
Supported e-form templates can be imported into Software AG Designer where they are converted to a standard IS document type. You can use the IS document type to describe the input for a business process, as the business data for a task that expects an e-form document, or for any other supported IS document type use. Software AG Designer must have network access to the webMethods Content Service Platform repository at design time.
webMethods Content Service Platform also provides the ability to define filtered views of a CSP repository, enabling you to provide custom repository views to your users. For more information, see
Creating a Content Filter.
E-form templates and instances are also accessed at run time by the webMethods run-time components (Process Engine and Task Engine). During run time, the template and instance location must be available to the Task Engine if you have implemented the ability for a user to download an e-form from an e-form enabled task instance running in My webMethods.
If Integration Server is connected to a webMethods Broker at the time you create an IS document type from an e-form template, the resulting IS document type will be publishable to the webMethods Broker and will have an associated webMethods Broker document type.
