Designer 10.7 | webMethods BPM Task Development Help | Configuring Tasks | Adding E-form Support to a Task | Adding E-forms Stored in a My webMethods Server Folder Location
 
Adding E-forms Stored in a My webMethods Server Folder Location
 
Adding an E-form User Interface to the Task Details View with Snippets
Adding an E-form Download Link to the Inbox Results View with Snippets
Customizing Task E-form Behavior
You integrate e-forms with your tasks using e-forms stored in a My webMethods Server folder location. Before adding e-form support to a task, you must create an IS document type by importing an e-form template. For more information, see About Business Data and E-forms.
*To add e-form support to a task
1. In the Solutions view, open the task in the task editor by double-clicking the task name.
2. Add an e-form-sourced IS document type to the task's business data, as described in Adding an Integration Server Document Type as Business Data, or create a new task from an e-form-sourced IS document type, as described in Creating a New Task from an Integration Server Document Type.
3. On the Overview tab, expand the User Interfaces area if it is not already visible.
4. Click the Default view for the Task Details portlet.
5. Click the Update button in the User Interfaces area.
6. In the Task UI Update wizard, do one of the following:
*Click the Add E-form support to the selected task UI page option. Use this option if you want to add e-form support to the task, but you do not want to add any of the business data in the e-form-based document to the task interface. Click Next and proceed to step 7.
*Click the Add task business data field(s) and E-form support to the selected task UI page option. Use this option if you want to add e-form support to the task, and you want to add some or all of the business data in the e-form-based document to the task interface. If you choose this option, you must then:
1. Click Next.
2. On the Add Task Business Data page, expand the table entries to locate and click the business data fields you want to add.
3. If you want to open the page or view in the view editor after applying the business data changes, select the Open updated page in Editor check box.
4. Click Finish. The business data fields are added to the view.
7. On the Add E-form Support dialog box, select the e-form-sourced IS document type in the Document Name list.
Note:
All IS document types added to the task appear in the Document Name list; be sure that the IS document type you select is one that was created from an e-form template.
8. In the Template Type list, select the e-form application that was used to create the e-form template that the IS document type was created from (for example, InfoPath or LiveCycle).
9. Click Browse to specify a value for the Template Location box. In this procedure, you are specifying the location of the e-form template that you imported to create the IS document type added to the task in step 2.
10. On the Select Source dialog box, do one the following:
*Click From File System and click Browse to select a template file located in a file system folder.
Click Next if you want to specify an optional name for the e-form template; otherwise, click Finish to return to the Add E-form Support dialog box.
*Click From Repository to select from a list of available repository definitions.
Note:
This list will be empty if no webMethods e-form environments have been deployed to the connected Integration Server. For information about creating and deploying e-form environments, see Implementing E-form Support for BPM.
Click Next.
On the resulting page, locate and click the appropriate template.
Click Next if you want to specify an optional name for the e-form template; otherwise, click Finish to return to the Add E-form Support dialog box.
11. Click Next.
12. On the Task Client Options panel, select or clear the check boxes for the following options as required.
Option
Description
Add a copy of the e-form template to the task
Select this check box to keep a copy of the e-form template in the task application. When a task user downloads the e-form information from the task, the embedded template is used to format the business data in the IS document type to its e-form format. If this option is not selected, the task application connects to the specified template location and downloads the template each time the e-form data is downloaded from the task.
Consider the following reasons to decide if you want to store a copy of the template in the task application:
*The original template may not be available to the task application at run time. This is particularly true for a template file stored in a local file system, but can be true for any location (repository, URL, or file system).
*Performance or security reasons that may prevent the task application from accessing the template at run time.
*You do not want the task application to automatically pick up any changes made to the template in the public repository.
The decision should be based on the above considerations, but generally, if the repository is available at run time and any expected template changes will be fully backward compatible, you are advised to avoid using a local copy of the template.
Add download capability to the task Inbox
Select this check box to add a download link to the task inbox results list. This enables the user to download the e-form directly from the inbox, without having to open the task.
Open updated page in Editor when finished
Select this check box if you want to open the page in the task editor after enabling e-form support.
13. Click Finish. The changes to the task are saved automatically.
14. If you want to customize the e-form interface, you can edit the page view in the task editor.
Related Topics