Architecture.md
... ...
@@ -14,35 +14,37 @@ Izenda Reports was designed with end-user performance in mind. We are 100% AJAX,
14 14
15 15
For optimal performance of your views, and database we suggest indexing any field that maybe joined in views, sorted, or filtered by. For example in SQL this can be done using the index tuning wizard.
16 16
17
-Report List Page (ReportList.aspx)
17
+###Report List Page (ReportList.aspx)
18 18
19 19
Report List (ReportList.aspx, example here) is first page the user typically interacts with unless given a link to a specific report. This page displays the list of reports. By default, it displays uncategorized reports first (in alphabetical order) and then displays an alphabetized list of the reports by category. If allowed, users may:
20 20
21
-Click the report to view the report in the report viewer page,
22
-Click modify icon to load the report in the report designer
23
-Click the delete icon to delete the report
24
-Report Viewer Page (ReportViewer.aspx)
25
-
26
-Report Viewer (ReportViewer.aspx, example: here) The user uses this page to view a report which has already been designed. Modifications to the report can be made without permanently altering or overwriting the report in any way. If permitted, users may:
27
-
28
-Add fields to the report,
29
-Filter the report using fields
30
-Export the report.
31
-Navigate to the report list page
32
-Load the report into the report designer page
33
-Report Designer Page (ReportDesigner.aspx)
34
-
35
-Report Designer (ReportDesigner.aspx, example: here) The user creates and modifies reports using this page. The page structure is a tabbed menu at top, followed by a toolbar of icons, and then the page content. Using this page, users will be able to:
36
-
37
-Choose data sources for a report
38
-Choose fields which are shown in a report grid and perform simple operations on the fields
39
-Create filters to filter report data
40
-Create a summary grid using fields and perform simple operations on the fields
41
-Create a chart to display data
42
-Create gauges to display data
43
-Schedule a report for emailing
44
-Change visual elements of the report, titles, descriptions, colors etc
45
-Preview the report after selecting all of the above
21
+ * Click the report to view the report in the report viewer page
22
+ * Click the modify icon to load the report in the report designer
23
+ * Click the delete icon to delete the report
24
+
25
+###Report Viewer Page (ReportViewer.aspx)
26
+
27
+Report Viewer (ReportViewer.aspx, example: here) is used to view a report that has already been designed. Modifications to the report can be made without permanently altering or overwriting the report in any way. If permitted, users may:
28
+
29
+ * Add fields to the report
30
+ * Filter the report using fields
31
+ * Export the report
32
+ * Navigate to the report list page
33
+ * Load the report into the report designer page
34
+
35
+###Report Designer Page (ReportDesigner.aspx)
36
+
37
+Report Designer (ReportDesigner.aspx, example: here) is used to create and modify reports. The page structure is a tabbed menu at the top, followed by a toolbar of icons, and then the page content. Using this page, users will be able to:
38
+
39
+ * Choose data sources for a report
40
+ * Choose fields that are shown in a report grid and perform simple operations on the fields
41
+ * Create filters to filter report data
42
+ * Create a summary grid using fields and perform simple operations on the fields
43
+ * Create a chart to display data
44
+ * Create gauges to display data
45
+ * Schedule a report for emailing
46
+ * Change visual elements of the report, titles, descriptions, colors, etc.
47
+ * Preview the report after selecting all of the above
46 48
47 49
###Settings Page (Settings.aspx)
48 50