Emulate RtReports 3​.3

The previous release of RtReports, RtReports 4.0, included a new PDF generation engine, replacing the legacy server-side printing feature. As a result, report printing is more robust and users have the freedom to view and/or print PDFs from a client computer. As a result of these changes, the format of some printed reports will look different than in previous releases. In most cases, the results will more accurately reflect options selected in the report formatting template. However, some customers may prefer the legacy report formatting in order to ensure that older reports render as closely as possible to the way they did in earlier versions. In order to assist in that effort, the following configuration options are provided:

• NestedTableTextWrapping

  In prior versions of RtReports, when a table was nested inside of another table's column, text was prevented from wrapping regardless of whether table data elements were configured to wrap in the format template. To preserve this behavior, set the value of this setting to "false". This setting can be found in Web.config and it is set to "true" by default.

  It is not recommended that this setting be changed unless old reports need to be generated and text wrapping in nested tables is causing a problem. For new reports, this issue is best resolved by setting related table data elements to No Wrap in the format template (checkbox in layout tab in format template).

• NestedTableForceFullWidth

  This setting allows system admins to force nested tables to full width to preserve the look of RtReports 3.3 for certain reports. Without this behavior gaps may appear within columns that contain nested tables. This is especially apparent if the nested table has visible borders around it. This setting can be found in Web.config and by default it is set to "false". It can be set to "true" to force the nested tables to take up the full space of their container, removing any apparent gaps.

• Emulate34Spacing

  In RtReports 3.4, extra spacing was added in section headers and footers. Reports that contained multiple levels of sections therefore included an undesirable amount of additional whitespace. In RtReports 4.0, this behavior was removed, but it can be added back in if desired by the use of this setting. This setting is in Web.config and by default it is set to "false".

• DefaultPageMargin value = "0.4 0.5 1 1"

• EnforceDefaultPageMargin value = false

  These two settings can be found in the OSISoft.RtReports.RtRemotingHost.exe.config file. By default, PDF margins are set in RtReports Format Template settings. This does not always result in similar margins to RtReports 3.3 (and prior versions) where a system default margin size was generally used. System administrators can set the EnforceDefaultPageMargin setting to "true" to emulate the legacy behavior.

  The default margin sizes to apply are specified via the DefaultPageMargin value, which is initially set to mimic the margins applied in RtReports 3.3. These values can be changed to use any desired default sizes using the DefaultPageMargin setting. The value of this setting is a space-delimited set of numbers representing margin sizes in inches. The order of the items in this list are top, bottom, left and right.

• Extra whitespace is added between sections when compared to 3.3.

  To remove the extra whitespace, please decrease the margin top and the margin bottom in sections EntryElement and ParagraphElement in ReportStyle.css:

  EntryElement {
  margin-top: 1em;
  margin-bottom: 1em;
  }
  
  .ParagraphElement {
  display: block;
  margin-top: 1em;
  margin-bottom: 1em;
  margin-left: 0;
  margin-right: 0;
  }