How FileNet P8 eForms Integrates with Workplace

The overall process of creating form policies, and how they fit in with Workplace, is outlined below. Use this list as a guide to help ensure that all prerequisites are fulfilled before you create a policy. For an explanation of what form policies are and how they're used in Workplace, see Get started with form policies.

NOTES  

1. Create an ITX form template and save it to Workplace

A form template contains the framework, the intelligence, and the graphic elements of a form. Users fill out a form by entering values in the fields (cells) on the form.

Before an ITX form template can be assigned to a form policy, the form author must

  1. Complete the form design and intelligence required for the ITX form template in eForms Designer.
  2. (optional) Publish the necessary cells for future property and/or step data field mapping in the form policy wizards. For more information, see field mapping overview.
  3. Add the template to Workplace and set the Document Class to ITX Form Template.

2. Create a Workflow Definition (workflow policy only)

If your form template is part of a multi-step process, create a workflow definition with steps, routing, and notification. You can create workflow data fields with default values for each step that correspond with published form template cells and form data subclass properties.

NOTE   Values in the workflow data fields can overwrite the values in the form template cells.

Before a workflow definition can be assigned to a workflow policy, the workflow author must

  1. Complete a workflow definition and use a form-based step processor (Form Launch HTML and Form HTML) for the launch step and subsequent steps from Process Designer on the Author > Advanced Tools page.
  2. Check in the workflow to an Object Store in Workplace.
  3. Transfer the workflow definition from the File > Transfer menu in Process Designer or by browsing to the information for the workflow in Workplace and choosing Transfer. Note that if you don't transfer the workflow, you are given the opportunity to transfer it during the policy creation process.

3. Create a Custom Form Data Document Class (Optional)

Workplace comes with a built-in document class that includes existing properties that are available for mapping. However, you may want to create custom document classes. Custom document classes must be created on the content Engine before you create a form data entry template. The custom document class must contain custom document properties that correspond to ITX form template fields for a custom form data document class. This class must be a subclass of the base form data document class.

4. Create an Entry Template

Entry templates contain information required to add the form data instance to an object store in Workplace. Depending on which settings you choose, the entry template can automate some of the steps required to add a form data document to an object store.

Before you create a document policy or workflow policy that requires property mapping, you must complete a form data entry template

Create a Document Policy

See Create a Document Policy for step-by-step policy creation instructions.

NOTES  

Create a Workflow Policy

See Create a Workflow Policy for step-by-step policy creation instructions.

NOTES  

Versioning



Feedback

© Copyright IBM Corporation 2013.
This information center is powered by Eclipse technology. (http://www.eclipse.org)