This is not the latest version of Identity Director documentation.View available documentation.
Configure a filter for a table attribute
You can configure a filter for a global, people or service table attribute, to filter out irrelevant data from a table attribute.
These filters can be configured at Entitlement Catalog:
- on the Attributes tab of a service, when you create a service table attribute based on a copy of a global, people or service table attribute.
- on the Workflow tab of a service, when you configure a Perform Table Operation workflow action, with Operation set to Filter table.
The filter only applies to the service on which you configure it, for the duration of the service workflow.
- Several operators (≠, ≤, ≥, etc.) are available to apply criteria.
- Placeholders are supported.
- Refresh displays a limited preview of the filtered data.
- Restricted information contained in the table:
- is displayed as for administrators who are authorized to see the information.
- is displayed as for administrators who are not authorized to see the information.
- The filter is applied:
- at the moment the service is requested (for service table attributes that are filtered copies of another table attribute).
- at the moment the service workflow reaches the 'Filter table' workflow action (for Perform Table Operation actions).
- New row index numbers are assigned after filtering a table. Select, Edit and Delete by row index must use the new row index numbers. Example
Source table:
Product Quantity 1 Apples 20 2 Bananas 55 3 Cabbage 15 4 Corn 40 The following filter is applied:
Quantity ≥ is greater than or equals 25
OR
Quantity < is less than 20The filtered table is now:
Product Quantity 1 Bananas 55 2 Cabbage 15 3 Corn 40 With this filter in place, select, edit or delete row index 2 applies to the product "Cabbage".
If a service workflow contains a Perform Table Operation action on a global or person table attribute, the following also applies:
- A user cannot Add or Edit data in the filtered table if the new data is outside the scope of the filter.
In this case, the transaction will fail. Example
Source table:
Product Quantity 1 Apples 20 2 Bananas 55 3 Cabbage 15 4 Corn 40 The following filter is applied:
Product ≈ is like C
The filtered table is now:
Product Quantity 1 Cabbage 15 2 Corn 40 With this filter in place, a user:
- can add the product "Coffee" ("Coffee" contains a "c", which matches the filter criteria).
- cannot add the product "Sugar" ("Sugar" does not contain a "c" and therefore does not match the filter criteria).
- can change "Corn" to "Cereal" ("Cereal" contains a "c", which matches the filter criteria).
- cannot change "Corn" to "Bread" ("Bread" does not contain a "c" and therefore does not match the filter criteria).
- A user cannot Select data in, or Delete data from the filtered table that is outside the scope of the filter.
In this case, the transaction will fail.Example
Source table:
Product Quantity 1 Apples 20 2 Bananas 55 3 Cabbage 15 4 Corn 40 The following filter is applied:
Quantity ≥ is greater than or equals 40
The filtered table is now:
Product Quantity 1 Bananas 55 2 Corn 40 With this filter in place, a user cannot select or delete the products "Apples" and "Cabbage" (these products are not listed in the filtered table).
In this example:
- If "Apples" or "Cabbage" was selected before the filter was applied, the selection is now lost.
- If "Bananas" or "Corn" was selected before the filter was applied, the selection is kept.
The operator - is contained by can be used to filter data from a table using multiple values from another attribute.
Consider the following scenario:
-
Table global attribute 'Contacts' contains a list of email addresses and the region they apply to:
Region Contact
1 Global [email protected] 2 EMEA [email protected] 3 US [email protected] 4 EMEA [email protected] -
Table people attribute 'Divisions2Regions' contains a list of divisions people work for and the regions the divisions they are in.
For person 'Leia Organa', this attribute could look like this:Division DivisionRegion
1 Royals Global 2 Androids EMEA
In this scenario, to create a service attribute named 'SubscriberContacts' that contains only the contacts that apply to the subscriber:
- In the Management Portal at Entitlement Catalog, go to the Attributes tab of your service.
- Click Add attribute.
- For Name, type SubscriberContacts.
- For Type, select Table.
- Expand the field that lists Table columns and select Copy from global attribute or type Table.
- In the field directly below, select global attribute Contacts.
- Under Filter by, click Add criteria.
- Under Operand, select column Region.
- Under Operator, select - is contained by.
- Under Value, click .
In the Create pattern window, go to Subscriber > Divisions2Regions > Entire Column > DivisionRegion and click .
- Finish the configuration of your service and save your changes.
Now, when Leia Organa requests the service (or it is requested for her), the table service attribute SubscriberContacts will contain only contacts for the regions 'Global' and 'EMEA':
Region |
Contact |
|
1 | Global | [email protected] |
2 | EMEA | [email protected] |
3 | EMEA | [email protected] |