Form data document classes for eForms
Before you create a document or workflow policy, you may need to create a form data entry template. Entry templates can automate Workplace tasks for users when they fill out a form. An entry template can automate the process of entering new documents into Workplace by holding presets for the following information:
- data save location
- security settings
- properties
- form data document class
Without an entry template, users will have to enter the above information each time they save a form.
For more information on creating entry templates, See Workplace Help.
Once an association is defined between a form data document class and an ITX form template, bidirectional document-class to form-template property mapping can occur.
For example, the form author can apply the Publish cell option to all or selected ITX fields that use eForms Designer's Cell command. When you create a policy in Workplace, you can map or link these published cells from the ITX to the document properties of the form data document class that was specified in the form data entry template. When the Workplace user opens the form, the mapped fields can display pre-filled values derived from document class properties. In this case, mapping has occurred from the document class to the ITX. You can set the policy so that when the user saves and/or launches the form, the form data values are entered into the document class properties automatically. In this case, mapping has occurred from the ITX to the document properties.
NOTE When adding a document to Workplace, you can click Show Properties to view properties for the form data document class.
There are two types of form data document classes:
Form Data Document Class (built-in)
This base class is used when saving an instance of form data. The required properties are indicated:
Property Name | Value | Description |
Form Template | Data Type: Object Value Class: Form Template Cardinality: Single Required: Yes Hidden:Yes |
The form template used to create the instance of form data. |
Form Policy Launched Workflow Number |
Data Type: String Cardinality: Single Required: No Hidden:Yes |
A unique workflow ID associated with the form data object. |
Form Proxy | Data Type: Object Value Class: Form Proxy Cardinality: Single Required: No Hidden:Yes |
A custom object that contains the launched workflow number and the associated form policy. |
Form Policy Step | Data Type: String | This value is set only if a form-based step processor (Form Launch HTML and Form HTML) is used. |
Descriptor | Cardinality: Single Required: No Hidden:Yes |
A multi-part string that includes the workflow sheet name, step name, and step ID. |
Form Policy Sequence Number | Data Type: String |
Contains the current sequence number for a form template field configured with an auto-increment value. |
Custom Form Data Document Class
An enterprise manager can also create custom subclasses based on the principal form data document class to handle your custom properties for a specific form design and for custom mapping. For example, a special form data document class named "Travel Expenses Form Data" can be created exclusively for Travel Expense forms. In addition to the document properties listed in the table below for the base Form Data Document Class, you can create custom properties such as "Expense Form Number" or "Department Name" that correspond to fields on the ITX. See the topic "Creating a subclass" in the Content Engine Help for details on how to create new document classes.
Feedback