This topic applies to ArcEditor and ArcInfo only.
Extended properties are used to allow each individual organization to store different business-specific properties dependent on their needs. These properties are configured by job type because it is likely that different types of work will have different properties associated with them.
Workflow Manager allows the configuration of 1–1 relationships (extended properties) and 1–M relationships (linked/related properties).
Before you begin, make sure you have added the extended properties tables to your Workflow Manager repository.
Once the relationship is configured, your Workflow Manager system is now ready to be configured to use these properties. Within the Job Type dialog box in Workflow Manager Administrator, navigate to the Extended Properties tab. At this point, you should see the tables you created relationships for in the list on the left.
The top-level elements in the tree view on the left-hand side represent the tables related to the JTX_JOBS table. The elements in the level below these tables represent each of the fields in the table. By checking the box next to these fields, you are making that field visible from within Workflow Manager for that job type.
As you click through the fields and the tables, information about the currently selected node will appear in the right-hand panel. When a table is selected, a list of the fields currently configured for the job type will appear. You have the ability to set the order the fields will appear to your users when viewing the extended table properties.
When you click on a field element, the following information is available:
- Field—The name of the field (fixed).
- Field Alias—Display name of the field (editable).
- Data Type—The value type of the field. This is dependent on the data type of the field in the table. With the string data type, you have the following options:
- Text—Presents the user with a text box.
- File—Allows the user to browse for a file and stores the file path in the extended properties table.
- Geographic dataset—Allows the user to browse for a geodataset and store its path as the value.
- Folder—Allows the user to browse for a folder.
- TableList—Allows the user to pick the field value from a list of values (similar to a domain). The list of values comes from another table that you configure.
- Editable—Whether the field can be edited or not (editable).
- Required—Whether the field value is required or not (editable).
- User Visible - Whether the field is visible to the user in the client application. Note:
You can populate the values of this field via the API and disable the visibility in the client application.
- Display Field—Whether this field will be used as the identification value when displaying 1–M records on the Linked Properties tab (editable).
- Default Value—The default value placed in the field when the record is created (editable).
Once all the properties have been configured to your needs, click OK and the property configuration is saved. This needs to be done for each job type independently.