• Disable scrollbars : If enabled, the Web view will try to disable the embedded browser scrollbars when the web page has been completely loaded. The feature is not enabled by default.
• Show statusbar : If enabled, the Web view will show the browser status bar. Not enabled by default.
• Follow Highlight/Selection : If disabled, when the Web view is in Link or Web Service mode, it will not navigate to a different link/webservice ignoring the current highlight/selection. Enabled by default.
• Provide 'omniscope' global object to scripts : If enabled, the WebView will pass the 'omniscope' global object to the scripts after the webpage has been loaded. Not enabled by default.
  Further information

• dmParamName - the name of a parameter to customise
  
• dmParamValue - the value for that parameter
  
• dmParam2Name - another parameter
  
• dmParam2Value
  
• dmParam3Name - another parameter
  
• dmParam3Value
  

<p><b>Total:</b> {{ SUBSET_SUM("Coupon") }}</p>

<#
  if (x==5) {
    y = 3;
  } else {
    y = 2;
  }
  out.println("Write some text into the document, programmatically");
  var array = subset_uniquesList("Category");
  for (var i in array) {
    #>
    <b>Some text and HTML with <#=array[i]#> (inserted values)</b>
    <#
  }
#>

1. In the function picker, only show functions which have the same resulting data type (in the same "logical value domain") as the field they are applied to.
   
   Visible choices (depending on field data type):
   
   • Sum
   • Mean
   • Median
   • Mode
   • Minimum
   • Maximum
   • Singleton value
   • First value
   • Last value
   • (Formula result)
   
   
   Power-user hidden choices:
   
   • Record count
   • Empty count
   • Non-empty count
   • Unique value count
   • Unique values list
   • Range
   • Standard deviation
   
   
   You would still be able to get at the power-user hidden choices easily but would not see these by default.
   
   This is necessary for (3), to avoid aggregation/grouping from changing the data structure and preventing formulas from working. Formulas are defined to operate over underlying raw data, and if your aggregation changes a text field into a numeric through the use of "Empty count", the formula will most likely fail.
   
   This change would occur in grouping and aggregation, but perhaps also elsewhere for consistency and to remove choices which are confusing - e.g. a value labelled "Sales volume" but showing "Range" is incorrect.
   
   
2. In the Table view, we provide a "Formula result" option for each field alongside sum/mean/etc., just like with aggregation, instead of the "calculate formulas over grouped results" precedence setting.
   
   
3. In aggregation and grouping, we make "(Formula result)" the default for any formula field. This would include the Table view grouping, in-view aggregation, and the Aggregation operation in the Data menu and in DataManager.
   
   Note: While the bar view aggregates automatically, we couldn't allow choosing "Formula result", since Omniscope couldn't tell whether to sum/mean/whatever in any fields referenced by formulas. Instead, you would use the new "Formula" measure in 2.7, which allows you to write your own field-independent formula where you are required to use SUBSET_SUM/MEAN as appropriate.