If an attribute links to a list of sub-objects or related objects, you have the option of incorporating a filter into the path. The filter could be the sub-object's role or related object's category. For example, you may want to filter matter assignees by role or involved parties by category (role). This is done with the use of a special intermediary table that appears in Object Navigator but is not actually part of the object model.
In this intermediary table between the starting table and the related or sub-object table, you can do either of the following:
•Choose the specific item for the filter.
•Select (Any)->, meaning that you do not want the list to be filtered.
For example, to create a path from a matter to its involved parties' contact records which have the role Outside Counsel, you could specify the following:
involvedList-> Outside Counsel-> contact-> (ok)
This would result in the following path:
.involvedList(Outside Counsel).contact
The following image shows what this path looks like in Object Navigator:
Object Navigator Related Object Filtering Example
If you want to create a path from a matter to its involved parties without filtering them by their role, you could make the following selections:
involvedList-> (Any)-> contact-> (ok)
This would result in the following path:
.involvedList(Any).contact
The following image shows what this path looks like in Object Navigator:
Object Navigator Unfiltered Related Object Example
The third table, which represents the involved parties, is the same whether you filter the list with an involved role or not. From the TInvolved table, you can access the contact information for the involved parties, such as their phone numbers or rates, through the contact-> attribute.
The following table indicates which attributes lead to intermediary, filtering tables in Object Navigator and the table to which the attribute links in the object model.
Object Navigator Attributes That Link to Intermediary Tables
Object table |
Attribute |
Leads to this intermediate table in the user interface |
Then leads to this table in the object model |
TProject |
accountList-> |
Category |
TAccount |
appointmentList-> |
Category |
TAppointment |
|
assigneeList-> |
Assignee Role |
JProjAssignee |
|
childList-> |
Child Object |
TProject (labeled with the custom object's name) |
|
expenseList-> |
Category |
TExpense |
|
involvedList-> |
Involved Role |
TInvolved |
|
taskList-> |
Category |
TTask |
|
rightRelationList-> |
Relation Type |
JProjRelation |
|
leftRelationList-> |
Relation Type |
JProjRelation |
|
TContact |
addressList-> |
Address Type |
JContAddress |
emailList-> |
Email Type |
JContEmail |
|
faxList-> |
Fax Type |
JContFax |
|
phoneList-> |
Phone Type |
JContPhone |
|
inetAddressList-> |
Internet Address Type |
JContInetAddress |
|
skillList-> |
Skill Type |
JContSkill |
|
rateList-> |
Task Category |
JContRate |
|
rightRelationList-> |
Relation Type |
JContRelation |
|
leftRelationList-> |
Relation Type |
JContRelation |
|
TInvolved |
rightRelationList-> |
Relation Type |
JInvlRelation |
leftRelationList-> |
Relation Type |
JInvlRelation |
|
TAppointment |
resourceList-> |
Resource Type |
JApptResource |