1. This screen may be skipped altogether if the user chooses a report from the server and clicks Ad Hoc or Edit or whatever. Also, the next screen would ordinarily be report type, but for now we’re only offering tables.

2. The Calculated… button pops a simple dialog - for now, just a text box and a prompt to enter a Java (or Groovy?) expression, along with a field for entering the name and a dropdown for data type. Users can enter the column label and preview the first 10 rows of data over to the side. User can also preview the whole report as HTML or PDF. The “Sample Preview” is still available at the bottom.

3. As each dropdown is populated, the next set of options appears, unchecked and disabled. If “Show Values” is unchecked for both Above AND Below details, the corresponding Summaries options are unchecked & disabled; group values will appear as non-repeated values in the details section, only.

4. Default is None for all columns. Ultimately, we may have a “context” (subtotals and/or grand totals) plus an option to have multiple rows of summaries.

5. In real life these would each represent a different canned theme. The “Current Report Styles” (a flex item) would hopefully show some representation of what these styles are. No Styles strips all style information from the report.

6. Optional text labels appear in the top table. Column details may be set in the second table. All columns, grouping and data, appear here, with their default widths and formatting shown. Formatting should be displayed using sample data – preferably taken from the actual column, but otherwise, some standard value.

7. Defaults should be provided for the file name and folder, derived from the report being edited or from the report title plus the current or default folder in the repository. Page properties defaults should be derived from the locale. Note that the input control names, if any, are read in from the report being edited. They are presented in the space shown, three across with multiple rows as needed.