Using the option labeled Generate report as of this date, you can look at the data in a report, as of the date you enter.
The report that is generated will display the results as of the date that you enter. Note the following:
- Point in Time filters are available for Column, Summary, Matrix, Aging, Treegrid, Dashboard, Container and Custom report types
- You cannot drilldown from a point-in-time aging report, as the results are not useful
- Dashboard and Container reports may or may not contain reports which have point-in-time date options set. In these report types, the dates set will override the dates set within the individual reports
- Custom URL reports will require custom code to support the feature
- All issues that are retrieved for point-in-time reports compare the date entered in the report editor to the last modified date (the TIMESTAMP field within the database)
- The title of the report is modified to highlight the point in time which is used to generate the report, thereby clarifying that the report is not displaying current information
- You may use $$SYSDAY$$ or $$SYSDATE$$ as the date for the point-in-time report. For example, if you want to generate a report that always showed yesterday’s results, you can set $$SYSDAY$$-1 as the date
- If the report contained filters that used $$SYSDAY$$ or $$SYSDATE$$ as values, then these values will be replaced with the same date that you entered into the Generate report as of this date field.Example: To generate a report so that it always returns the data as of the close of business on the previous day, use $$SYSDAY$$ – 1 as the entry
- You may use the $$RUNTIME$$ token as the date for the results to be generated. The runtime filter screen will prompt for the date when running the report
- Any drilldown from the report, by clicking on a value within a Summary or Matrix report, or clicking on the Edit button within a Column report will show the current results, not the historic result. This prevents you from attempting to edit the historic values within any issue as this would be a contravention of the audit trail that is maintained within all issues
- The date used for the point-in-time results will be displayed on the report output, in the user’s personal date / time format. Within workspaces this is found by mousing over the user button which displays who prepared the report along with the date and time
- If your administrator imported legacy issue data into ExtraView from a remote source, the TIMESTAMP on these records reflects the actual date and time the records were imported. This is not likely to be the same date and time the records were created and point-in-time reports are not likely to display the results that you expect. This is the correct behavior, and cannot be altered, as it is imperative that ExtraView’s audit trail correctly records the transactions. Note that the Date Created field (DATE_CREATED) may be altered on the import of issue data, but the date last modified (TIMESTAMP) field is independent of this
- Within workspaces, dragging and dropping issues to and from point-in-time reports is disabled
- You cannot perform a mass update from the output of a point-in-time report
- You cannot perform a Quickedit operation from a poin-in-time report. If a Quickedit button is placed on a point-in-time report, it will not be rendered.