IBM FileNet P8, Version 5.2.1            

Forms assets (eForms and IBM Forms)

Document policy

Description Contains the information that is needed to present a form in Workplace. This information identifies the form template and form data entry template that is used for the policy, how mapping is configured between form template fields and document class properties, and any special property settings or security features.
Deployment Mechanism FileNet® Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • The form template that is referenced in the FormTemplate property
  • The form template that is referenced in the <form template> element of the Document policy content
  • The form data entry template that is referenced in the <entry template> element of the Document policy content

See Common dependencies between objects.

Environment-specific data
  • The name of the object store that contains the form template that is referenced in the <objectstore> element beneath the <formtemplate> element in the Document policy content
  • The name of the object store that contains the entry template that is referenced in the <objectstore> element beneath the <entrytemplate> element in the Document policy content

Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifiies users and groups. For more information, see Permission.

Notes If an existing document policy is referenced by individual form data documents, you cannot delete the existing policy without removing all referencing data documents. When you import document policies, do not update a policy that is in use. Instead, create a new version of the policy.

Form data

Description Contains a data instance for a form template.
Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • The document policy that is referenced in the FormPolicy property
  • The form template that is referenced in the ITXFormTemplate property

See Common dependencies between objects.

Environment-specific data Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission.
Notes In some source environments, there might be an accumulation of test form data documents. If these test data documents are not explicitly deleted, then depending on which export manifest include options are selected, the documents can be automatically exported by FileNet Deployment Manager because of the object property relationships. If you do no want the documents to automatically export, delete the test form data documents before you run the export.

Form data entry template

Description A form-enabled extension of the Workplace Entry Template.
Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • The class definitions and property definitions of the form data class that is specified by the TargetObjectClassId property
  • The folder that is referenced by the form data entry template
  • The security policy that is referenced by the form data entry template
  • The workflow that is referenced by the form data entry template

See Common dependencies between objects.

Environment-specific data
  • The object store that is referenced by the TargetObjectStoreName property
  • The object store that is referenced in the <objectstore> element beneath the <entrytemplate> element in the Form data entry template content
  • The name of the object store that contains the workflow definition that is referenced in the <objectstore> element beneath the <workflow> element in the Document policy content

Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission.

Notes
  • Do not modify the GUID when you import a form template as subsequent document types rely on this file.

Workflow policy

Description Provides the links between a workflow definition and the form template and the entry template that is associated with each of the workflow definition's steps. This document identifies which form template and entry template are to be used for each workflow step, and which pages are to be displayed for that form template.
Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • The workflow that is referenced in the <workflow> element of the workflow policy content
    Tip: The dependencies might be repeated for each step of the workflow.
  • The form template that is referenced in each <formtemplate> element of the workflow policy content
  • The form data entry template that is referenced in the <entrytemplate> element of the workflow policy content.
  • The entry template that is referenced in each <attachment> element of the workflow policy content

See Common dependencies between objects.

Environment-specific data
  • The object store that contains the workflow definition, in the FormPolicyWorkflowObjectStore property.
  • The name of the object store, in the <objectstore> element beneath the <workflowpolicy> element in the workflow policy's content.
  • The name of the object store, in the <objectstore> element beneath each <formtemplate> element in the workflow policy's content.
  • The name of the object store, in the <objectstore> element beneath each <entrytemplate> element in the workflow policy's content.

Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission.

Notes If an existing workflow policy is referenced by individual form data documents, the workflow policy cannot be deleted without first removing all referencing data documents. To update an in-use workflow policy by using the import operation, you must create a new version of the policy instead of updating the existing version.

Form template (eforms and IBM forms)

Description Describes the appearance and behavior of a form.
Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies Not applicable
Environment-specific data Optionally, the form template content can contain connection settings for auto-increment, lookup, or data submission data sources. The FileNet Deployment Manager Editor can be used to enter new connection settings to be mapped during conversion.
The following Service Types are supported:
  • EFormHTTP - The URL field provides the URL of the HTTP data source.
  • EFormODBC - The Server field provides the DSN of the ODBC data source.
  • IBMForms - External references such as web services URLs or endpoints that you can extract for the Service Data half map. After the external reference are extracted you can process them.
  • IBM Forms service types
  • EFormJDBC - The Server, UserID, Password, and Driver fields provide the connection settings of the JDBC data source.
    Note: To edit the Password field with the FileNet Deployment Manager Editor, the FIPS 140-ready mode must be disabled.

If the connection settings include calculations, FileNet Deployment Manager cannot convert this information. Instead, you must manually convert the information before you import.

Any object that is exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information that identifies users and groups. For more information, see Permission.

Notes

Form templates are created in either IBM® FileNet P8 eForms Designer or IBM Forms, and are added into FileNet P8 to be used with the FileNet P8 eForms feature.

Restriction: To import IBM Forms into FileNet P8, the forms must have an .xfdd extension.

If an existing form template is referenced by a policy or by individual form data documents, the form template cannot be deleted without first removing all referencing objects. To update an in-use template by using the import operation, you must create a new version of the form template instead of updating the existing version.



Last updated: March 2016
roadmap_eforms.htm

© Copyright IBM Corporation 2016.