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: |
Dependencies |
|
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 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. |
Description | Contains a data instance for a form template. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies |
|
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. |
Description | A form-enabled extension of the Workplace Entry Template. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies |
|
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 |
|
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: |
Dependencies |
|
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 | 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. |
Description | Describes the appearance and behavior of a form. |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
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:
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. |