Associating and Dissociating Action Models with a Filter
Once you've created and registered your filter, you can also associate action models with your Simple Filter, or dissociate action models with your Universal Filter. This is done in *actionModels.xml.
Dissociating Action Models from a Universal Filter
In cases where you don't want a global filter to be applied to specific action models, you need to find those action models in *actionModels.xml that and update them to include an excludeFilter element, as shown below:
|
|
The name attribute of the excludeFilter element should correspond to the selector used to register the filter in *service.properties.xconf.
|
Associating Action Models with a Simple Filter
Suppose (hypothetically) you created and registered a simple filter called ProblemReportStatusFilter (and registered it with a selector of "problemReportStatus") and you wanted to apply it to a few action models. You would find the action models you want to apply your Filter to in *actionModels.xml and modify them to include includeFilter elements like this:
|
|
The name attribute of the includeFilter element should correspond to the selector used to register the filter in *service.properties.xconf.
|
Multiple Filter Inclusions/Exclusions for the Same Action Model
In theory, an action can have any number of universal filters dissociated from it and any number of simple filters associated with it. You would just add as many includeFilter and excludeFilter elements as you need in *actionModels.xml.
For example:
|
|
The order of the includeFilter and excludeFilterelements does not matter, nor does it have any bearing on the order in which the filters are called.
|
