eForms assets

Document policy

Description

Contains the information needed to present a form in Workplace. This information identifies the form template and form data entry template 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
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies
  • The ITX form template referenced in the FormTemplate property
  • The ITX form template referenced in the <form template> element of the Document policy content
  • The form data entry template 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 containing the form template that is referenced in the <object store> element beneath the <form template> element in the Document policy content
  • The name of the object store containing the entry template that is referenced in the <object store> element beneath the <entry template> element in the Document policy content

Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying 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 importing document policies, do not update a policy that is in use. Instead, create a new version of the policy.

Form data (.ifx)

Description

Contains a data instance for a given form template.

Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies
  • The document policy referenced in the FormPolicy property
  • The ITX form template referenced in the ITXFormTemplate property

See Common dependencies between objects.

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

Form data entry template

Description A form-enabled extension of the Workplace Entry Template.
Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies
  • The class definitions and property definitions of the form data class specified by the Target Object Class Id property
  • The workflow referenced by the form data entry template

See Common dependencies between objects.

Environment-specific data
  • The object store referenced by the Form Data Template Object Store Name property
  • The object store referenced by the Target Object Store Name property

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

Notes
  • The form data entry template contains a property called ITXFormTemplate that is a reference to the form template. This property is not used and can be ignored.
  • Do not modify the GUID when you import a form template as subsequent document types rely on this file.

 

Form workflow policy

Description Provides the links between a workflow definition, a form template, an entry template, and a Form Data Document. This document identifies which template is to be used for each workflow step and which pages are to be displayed for that template.
Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies
  • The ITX form template referenced in the FormTemplate property
  • The ITX form template referenced in the <form template> element of the workflow policy content

    NOTE This dependency might be repeated for each step of the workflow.
  • The form data entry template referenced in the <entry template> element of the workflow policy content.

See Common dependencies between objects.

Environment-specific data
  • The object store containing the workflow definition, in the FormPolicyWorkflowObjectStore property.
  • The name of the object store, in the <object store> element beneath the <workflow policy> element in the workflow policy’s content.

Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying 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 using the import operation, you must create a new version of the policy instead of updating the existing version.

ITX form template (.itx)

Description Describes the appearance and behavior of a form.
Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies

See Common dependencies between objects.

Environment-specific data

Optionally, the form template content can contain the following connection information:

  • Information that is used to connect to a Microsoft SQL Server database. This information is located in the <server>, <userid>, <password> and <driver> elements beneath the <SQLConnect> element.
  • Information that is used to connect to a URL. This information is located in the <URL> element.
  • Information that is used to connect to a database. This information is located in the <server> element beneath the <connection> element.

FileNet Deployment Manager does not convert this information. If the connection information is present, you must either manually converted the information before import or modify the content of the imported form template before it is used.

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

Notes 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 using the import operation, you must create a new version of the form template instead of updating the existing version.