Using E-forms in a Process
Designer supports the use of Microsoft InfoPath and Adobe LiveCycle e-forms in processes. Both receive tasks that start processes and those that do not start processes can use e-forms. Message and signal start events can use e-forms to start processes. Message and signal intermediate events -- boundary and top-level -- can also use e-forms.
Important:
User tasks can also use e-forms. E-form support in a user task must be added in the task editor, even if the process is e-form driven. For information about e-form support to a task, see in webMethods BPM Task Development Help. For more information about using e-forms, see the PDF publication Implementing E-form Support for BPM.
E-forms are created from templates; those templates contain information required by the process using the e-form. When an e-form is used in a process, it is an instance of that e-form. E-form templates and e-form instances both need to be accessible to the process, and it is important that each has a separate location.
To use an e-form in a process
In Designer, do one of the following:
Drag and drop an existing e-form sourced IS document from the Package Navigator view onto the process editor to create a message start event pre-configured to use an e-form. The
E-form (For E-form Triggered Processes) check box is automatically selected, and the
E-form Template Name field is automatically populated. You must select the
E-form Content Repository location.
OR
Drag and drop an existing e-form sourced IS document from the Package Navigator view onto an existing receive task, message / signal start event, or message / signal intermediate event (including boundary events) to configure it to use an e-form. The
E-form (For E-form Triggered Processes) check box is automatically selected, and the
E-form Template Name field is automatically populated. You must select the
E-form Content Repository location.
OR
Manually configure an existing receive task, message / signal start event, or message / signal intermediate event (including boundary events) to configure it to use an e-form. You must select the
E-form (For E-form Triggered Processes) check box. The
E-form Template Name field is automatically populated when you select an e-form sourced IS document as the step's
Receive Document. You must select the
E-form Content Repository location.