26 lines
1.5 KiB
Plaintext
26 lines
1.5 KiB
Plaintext
REPORTING SPECS
|
|
|
|
CASES
|
|
1734 - REPORTS:GRIDS: - grid filter name and summary of filter criteria available as fields to print on report
|
|
|
|
|
|
REQUIREMENTS
|
|
|
|
- All v7 reports ported to RAVEN
|
|
- ALL Fields even the ones that don't show on the report but are available for adding to a report in the editor need to be available
|
|
|
|
- REPORTS
|
|
- Report object has following properties:
|
|
- DataList name it's based off of
|
|
- Required fields from DataList
|
|
- Report template itself with it's own code and template requirements TBD
|
|
- Report columns returned: When user selects to show a report, client will fixup any missing columns from the datalistview currently in use
|
|
- For example they are viewing a table based on a TestWidgetDataList DataListview with only 3 columns in it
|
|
- They drop down the reports list which shows all reports based off TestWidgetDataList view
|
|
- They select a report to print.
|
|
- Report code looks at report's required fields from DatalistView and sees report uses 6 fields listed
|
|
- Code compares report fields to in use DataListview fields and appends any report required fields missing from current view to the right of the collection in the current DataListview
|
|
- When report is run it will have all fields this way returned but will still be sorted and filtered by table view
|
|
- As part of editing process user can select an existing datalistview to prime their report editing view
|
|
- A report can be selected from any client table that is based on the same view
|
|
|