You can add a filtering report parameter to a custom
report. At run time, the filtering parameter links in to
the Talent Management Search Framework to create a
filterable field. For example, in the image below, the User
field is filterable: it includes the Filter
button.

The User Status field is a common BIRT parameter, using the ? syntax.
When report runners click the Filter
button, they see the user search
framework as defined in the User search selector. The search selector is
configurable, so the image below shows
only one possible configuration.

To call the filter, you first must know the name of the selector that you want to use. The Talent Management libraries contain a preconfigured parameter for every search selector. Choose the parameter that matches the entity you want users to filter.
In the library, find the parameter that matches the Talent Management entity that you want users to filter.
Copy the parameter from the library to the report.
Save the report.
Write the SQL query for the report.
To call the filtering search parameter, enclose the parameter name in brackets. For example, for the parameter called "User Search" type: WHERE stud_id in [UserSearch].
To fully test filtering, you must import the report to Talent Management. When it is unpublished, you can troubleshoot it, but it will not be accessible to most users.
The following SQL query selects the user ID, last name, and first name from the PA_STUDENT table. There are additional features in the SQL statement, but this example concentrates on the filtering feature.
SELECT a.stud_id, a.lname, a.fname
FROM pa_student a
WHERE a.active = ?
/** AND a.stud_id in [UserSearch]
AND [security:pa_student a]
ORDER BY [order_by_parameter OrderBy "FNAME=a.fname;LNAME=a.lname"] */
The query also uses the common parameter syntax of BIRT, the question mark (?), to allow the run time user to select active or inactive users.
The User Search parameter links to the User search selector. User (the name of the search selector for user filters) appears in the Custom XML property of the User Search parameter.
At run time, the sub-select statement is replaced for [UserSearch]. For example, if the user filtered for users with the middle initial "A" then the statement at runtime would be:
SELECT a.stud_id, a.lname, a.fname
FROM pa_student a
WHERE a.active = user selection
/* SEARCH FILTER START*/
AND a.stud_id IN (SELECT stud_id FROM pa_student WHERE mi="A")
/* SEARCH FILTER END*/
/* SEC FILTER START*/
AND domain filtering
/* SEC FILTER END*/
/*ORDER BY START*/
ORDER BY order by selection
/*ORDER BY END*/