Overview of E-form Environment Configuration
The e-form templates and instances you create are used by the webMethods product suite in the following ways:
During design time, you use
Software AG Designer to locate and select an e-form template for importation as an IS document type or as business data for a task.
During run time, the
Process Engine continuously monitors an instances folder for the arrival of new instances of an e-form to start a new business process.
Also during run time, if you implement the ability to download an e-form from an e-form enabled task instance interface running in
My webMethods, the
Task Engine formats the e-form business data for downloading using the associated template, and, after uploading, modifies and saves the task business data with the modified data from the uploaded e-form.
When you are working with My webMethods Server configured as a JSR-170 content repository, you must inform these components of the correct e-form repository folders to use by defining an e-form environment in My webMethods, and then deploying that environment to the Integration Server(s) where e-form enabled processes will be running.
In other words, by deploying the e-form environment, you are specifying the repository location of your e-form templates and e-form instances to the various components, so they can be retrieved as needed during design-time and run-time activities.
You must maintain your e-form instances in
My webMethods Server configured as a JSR-170 repository; however, you can locate your e-form templates elsewhere if you so choose. For more information, see
Other E-form Template Storage Options.
