Report Filters

Report Filters are filters that may be applied to specific attributes within a process that limit the amount of data to be returned. The filter may be applied to key attributes of a given task such as an answer to a question on a form, the current status of a request (Last Milestone), the status of task, or even on a recipient of a given task.

In this section we will discuss:

• Adding filters to a report

• Exposing filters

• Bitwise Operators (and/or)

• Grouping Filters

Adding Filters

To add a new filter to your report, navigate to the Filters tab. You will be presented with a list of all filters current saved for that particular report:

To add a new filter to a report, select the Add Filter button and you will be presented with the following dialog:

Similar to adding columns, you will have various options with which to select Source data from within the process to filter on.

The dialog will be dynamic based on theSource option you select. For instance, if you were to select Request as the source then the dialog will change and present you with a list of available attributes about a Request:

The following is a high-level break down of each available Source:

NOTE: By nature, Any Data queries are non-indexed, full table scans. Use Any Data thoughtfully as it can result in poor performance.
Current Task
(for Task reports only) | Option to define the attributes for the current task. Commonly used to view how many tasks are assigned to users, total counts of tasks, time between task assignments and completions, etc.

Once you have selected the item from theField list, defined the Operator , and a Value , press the Save button and the new filter will be added to the filter list:

In the example above, we are restricting the results of the report to retrieve data only from requests where the Last Milestone is equal to the value Loan Approved.

Report Operators

Expose Filter Labels

If you want the user that runs the report to have the ability to define the filter, select the Expose Filter Label field for the filter you want to expose and give it a name (label).

When running the report, the exposed filter will give the user to edit the filter. In this example, we are allowing the user to change the ‘Last Milestone’ field to get the view he/she desires:

NOTE: If you blank out an exposed filter at runtime, the provided default value will be used.

Bitwise Operators (And/Or)

It is possible to create a report that will retrieve various elements of process data based on multiple types of filters. When this happens it is often necessary to employee the user of the bitwise operators for restrict or open the range of data you would like to retrieve.

To change the bitwise operator, add more than one filter to your report and double-click the And/Or column next to filter:

By default, the bitwise operator will always be AND but, as in the case above, you may want to change it to OR. This way, we can retrieve data from requests with two different filters.

Grouping Conditions

For complex filtering scenarios it is possible to group a series of filters to evaluate together when the report is executing.

To group a series of filters, click in the column marked with an open parentheses where you would like to start the filter and add an open parentheses.

To end your grouping, simply click in the closed parentheses column to the right of a filter and add a closing parentheses.

For Custom Reports, there are some built-in Parameters that can function like Report Filters

When working with custom reports based on your own SQL query, there are a few built-in parameters that can be used to qualify the data returned on your report:

@user_sid allows you to access the SID associated with the user that is running the report

@date_limit_start & @date_limit_end accesses the corresponding date values stored in the report’s LIMITS tab

Here’s an example use:

select
INSTANCE_GUID “REQUEST_LINK”,
INSTANCE_ID “ID”
from
(select
INSTANCE_ID,
INSTANCE_GUID,
REQUESTER_GUID
from
INSTANCE
where INSTANCE.CREATED_BY = @user_sid
and CREATE_DATE >= @date_limit_start
and CREATE_DATE <= @date_limit_end
and INSTANCE.DELETED_DATE is null
) derived
order by
derived.INSTANCE_GUID