Defining Resource Editor Filters
Create filters to provide Resource Planners with a method to refine the list of projects and resource pools available for selection within Resource Editor.
- To create project filters, create single or multi-select list metrics (defined or query driven) that are defined as filter metrics.
- To create pool filters, create single or multi-select list extended fields.
These filters are driven by the data that exists in the system, meaning that when you click filter options, the projects, pools, and resources that are listed actually exist in the filtering categories. This allows you to create a hierarchy of filters. For example, given three filters such as Division, Product Line, and Product, when a user selects a division, only the product lines that are in that division are displayed in the next filter, and when the user selects one of the product lines, only the appropriate products are displayed in the Product filter.
In this example, the Division filter metric would contain only A and B while the Product Line filter metric would contain all the potential options: 1, 2, 3, 4, and 5, and so on for the Product filter metric.
| Division | A | B | |||
| Product Line | 1 | 2 | 3 | 4 | 5 |
| Product | a, b, c | d, e | f | g, h, i | j, k |
But in the projects the project managers in division A would only select Product Line 1, 2, or 3 in their projects, while managers in division B would only select Product Line 4 or 5, so that, in the filter dialog, when a planner selected A in the Division filter, the only options available in the Product Line filter would be 1, 2, or 3.
Vertical Ordering of Filters
Metric filters are listed in order by their defined Order numbers. A lower number places the filter higher in the list. Extended field filters for pools are ordered alphabetically by their display names.
Create Filters that Match Pools to Projects
If your company uses security lists, and the Enable Extended Demand Constraints system parameter is set to 1, the security list selections for the pool and project must match for the pool and project to be available within Resource Editor. A match between a resource pool and a project occurs in an individual list when the same item is selected for the pool as for the project or when a selected item for one (pool or project) is on a branch below a selected item for the other (project or pool).
For example, consider a three-level list based on geographical location:
Continent
Country
City
If the pool has Europe selected as the continent, a project that has Paris selected matches the pool because Paris is in a branch coming down from Europe. A project with Dallas selected would not match because Dallas is not on a branch below Europe. The match would also occur if it were the project that had a selection at the Continent level and the pool that had a lower item selected.
To make a complete match there must be at least one match between the pool and the project in every active list in the security list system.
|
Notes:
|