Fields are managed in field groups in the Project Tree pane. Fields can be organized into logical groups so that finding specific fields within a large class is more straightforward.

Fields can be used in Tungsten Transformation at the project-level, the class-level and on folders.

Fields added to the Project Class behave differently to fields added to any other classes in the project hierarchy. Fields inserted at the project-level are extracted before classification is performed. This means that the field cannot rely on any information provided by classification and the extraction step. If you configure a field in a child class that is inherited from the project-level so it is populated with a local locator, that field is not populated during testing or production. This is because the project-level fields, including inherited fields, are extracted before classification runs, and before child class extraction is performed.

There are two types of fields. Simple fields or table fields, and either can be added to any field group.

For all kinds of fields, different properties are available and you can define validation methods for them. However, each field type is processed at a different point in time during the processing workflow.

You can manage fields in the following ways:

• Add a new field

• Rename a field

• Delete a field

• Modify field properties

• Map a field to a locator

• Add a single field validation rule to a field

• Add a multi-field validation rule to a field

• Reorder fields

Related topics:

• Manage field groups

• Project Tree window

• Simple fields

• Project-level fields

• Class-level fields

• Folder fields

• Table fields

• Validation methods