From 3d8aae854f2875f9f6aa86be480e8697f07f397e Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 19 Aug 2020 17:58:15 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 15a261d7..0fe9a523 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -10,12 +10,15 @@ Procedure: Look at existing reports in v7 and generalize them and the features provided that are used pdf, email, print, download print / download / email / export immediately as an option no only preview and then those other things + custom fields must be available, perhaps as widgets that handle if they are present or hidden and etc + whatever is easiest from a design point of view wiki must be a type of field like any other that can be inserted into a report and will properly render this way they can make a report with only a wiki or a report with a hybrid data and wiki or whatever and it flows with how the wiki is now just a field on the data object like any other grid filter options and filter name must be an available field for report designer probably need a filter summarizer widget that can also be used inside the UI at the top of grids as well logo field with choice of size to correspond to the logo route + graphs and charts that show in UI should be printable / KPI Metrics stuff labels wtf? notification needs to be able to generate reports and send them Schedule form reporting @@ -27,7 +30,25 @@ Procedure: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3451 look at commercial ones just to steal ideas +todo: from reporting specs doc, not vetted, was written a while ago: + - 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 + TODO: Reporting datasources Needs to be able to handle getting data from different types of sources and be cool with it