This commit is contained in:
@@ -3,9 +3,7 @@
|
||||
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
|
||||
|
||||
|
||||
todo: reports need to know the custom field configuration for each type along with the data in teh report meta data I guess or something else maybe
|
||||
consumable by a function in ay-report.js which will then produce a block of localized json
|
||||
(maybe an option for non localized as well or both in same?)
|
||||
todo: convert custom field data to usable json from the string in getReportData
|
||||
|
||||
todo: report add "HasLogo" or "HasSmallLogo", "HasMediumLogo" to server meta data then leverage it in the logo helper?
|
||||
|
||||
@@ -28,7 +26,10 @@ todo: (make a priority 2 case?) Will this be a thing or keep as a case for futur
|
||||
todo: export from grid to xls, csv etc.
|
||||
I'm thinking perhaps also a secondary ability to make report templates that are actually intended for export to xls or whatever as an additional feature
|
||||
but the easiest thing for people would be a straight export of grid data from grid, perhaps using the reportdata system since it pulls in all the bits needed for full data rather than just id links
|
||||
|
||||
|
||||
Is the report list filtered by roles? It should not present reports that a user is not permitted to use by role.
|
||||
|
||||
Add sanitize html for Marked markdown helper as in Wiki control
|
||||
|
||||
|
||||
TODO: Report confirmation checklist
|
||||
|
||||
Reference in New Issue
Block a user