Attribute to use for filtering

The attribute that you want to use to filter the data. Select the appropriate attribute from the list. This setting is only applicable to criteria that are based on an attribute. For example, if you are filtering a group of work order tasks, you might select the Task status attribute. You can then select one of the task statuses (for example, Planned) as the value to filter on. The list contains only eligible attributes that are owned directly by the specified class. This means that the following types of attributes are excluded: • Binary objects • Html texts • Icons • Variable length strings • Variants

	See Also

And/or

If you are creating multiple filters based on the same attribute, you may wish to change the And/or setting. When you use more than one filtering criterion, you must establish the relationship between them. APMAPM Remote supports two Boolean operators: AND and OR. AND displays records that satisfy both criteria. OR displays records that satisfy either criterion. Criteria based on a common attribute or column are considered to be in the same filter group. For table configuration and calculation input filters, you cannot define groups directly. The system always uses the AND operator between different filter groups. For example: Criteria 1 is “work orders where the Planner is Jane Smithopen work requests where Asset Name includes ‘Pipe’ ”. Criteria 2 is “work orders createdrequests in the last month”. These criteria are based on different attributes (Planner and Creation DateAsset Name and Date Requested). Therefore, the system uses the AND operator. The result is a list of work orders that were created by Jane Smithassets with “pipe” in their name with work requests in the last month. You cannot change the operator used between groups, but you can change it when working with criteria within a group. For example, you may want to see work requests for both pipes and pumpsorders created by both Jane Smith and Jacky Lee: Criteria 1 is “work orders where the Planner is Jane Smithassets with “pump” in their name”. Criteria 2 is “work orders where the Planner is Jacky Leeassets with “pipe” in their name”. If you use the OR operator between these criteria, you get a list of work orders created by both Jane Smith and Jacky Leeassets with either “pump” or “pipe” in their name. Usually, criteria for the same attribute use the OR operator.

	See Also

Condition

The condition the objects must meet in order to be included in the filtered group. For example, if you are filtering using the attribute Task status, you could select the condition ‘Is’ and the value ‘Planned’. This would include only work order tasks that have the status ‘Planned’ in the filtered group. If you select the condition ‘Is not’, only work order tasks that are not ‘Planned’ will be included in the group.

	See Also

Value

The value of the attribute that will be used to filter the objects in the group. For example, if you are filtering using the attribute Task status, you could select the condition ‘Is’ and the value ‘Planned’. This would include only work order tasks that have the status ‘Planned’ in the filtered group.

	See Also

Class that contains the filter value:

The name of the object (class) that owns the selected attribute. If you have selected a relationship to another object, the name of that object will appear in the box. You cannot directly change the object listed in the box.

	See Also

Attribute that contains the filter value

Select the attribute that contains the data to be used for filtering. The list contains any eligible attributes owned directly by the specified class. For example, to select work orders that belong to the same site as the one that owns the current indicator, the join path is Asset.Site and the filter value is Site name.

	See Also