By setting a report's Limits, you will be limited the scope and quantity of data that may be retrieved when the report is executed. You may also further the limit the scope of the data by user or even expose some date filter capabilities to the end user.
Each of the options are discussed below.
There are several pre-defined date ranges that may be used to define limits on the report. These limits are based on the Start Date of requests for the process you specified when creating the report:
For instance, if you were to select Last 30 Days as the default date range, the report will only retrieve requests that have started in the last thirty days based on the time the report is executed.
If you would like to specify a specific date range you may do so by selecting the (Date Range) option:
At a minimum when using the Date Range option, you will need to add a date in the Start Range option. In the example above, the report will never retrieve request data for requests that were started prior to April 4, 2017. Even if the report date filters are exposed to the end user, they will still be restricted to any requests that start after April 4, 2017.
Exposing Date Range Filters
By default, no report limits are exposed to the end user running the report. If you would like to do so, select the option Expose date filtering to user running report:
By selecting this option, the user will be offered the opportunity to select any of the available date ranges when executing the report. Be aware that the results returned by the date range that the user selects when executing the report will never extend past the date range set here. For example, if you select Last 30 Days when configuring up your report, and the user selects Last 60 days when executing the report, the data returned will only be for the Last 30 Days.
Limiting Report Data
The default behavior for all reports is to retrieve data without any security restrictions with regards to tasks or participation in a request by the end user executing the report. This means that regardless of user’s participation with a request(s) for the process you are reporting against, he/she will be able to view all data even if the data returned is on a task which they were not originally granted to see or even a request he/she has taken part in.
It is possible to restrict the report output based on the user executing the report so he/she will only see request data which they participated in by selecting the option Only report data attached to current user (Requests, Assigned Tasks):
Publish Status Filter
Since Integrify has the capabilities to be a standalone development, testing, and production environment, all of your development and testing request data is intermingled with the production level request data.
At times it is advantageous to filter process data based on the Publish Status of a given process; especially if you are building reports in parallel to your process development. To alter the scope of that data retrieval you may filter on any of the available Publish Statuses:
Note: in most scenarios, when your process is in production, you will want to set this filter to be Production.
Process Version Filter
Since Integrify allows for process versioning, you can optionally define the version of the process you are reporting against. If left undefined, the default will be the current verison.
Do not show links to requests or tasks in report
Option to allow users to link to the underlying request or task data in the report. By default, it will allow for links to the requests or tasks.
Records Per Page
You may limit or increase the default result set viewed by your user by selecting one of the available record thresholds:
If any of these thresholds are met with the number of records returned, Integrify will provide the user with paging controls to view the rest of the records returned for the report.
For Custom Reports, the Date Range on the FILTERS tab can be accessed by built-in parameters:
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:
where INSTANCE.CREATED_BY = @user_sid
and CREATE_DATE >= @date_limit_start
and CREATE_DATE <= @date_limit_end
and INSTANCE.DELETED_DATE is null