x

Colors defined using RGB values display slightly different shades in PDF and HMTL. This is due to a rounding factor when RGB values are converted from whole numbers used by HTML to decimal values required by PDF.

x

The following is a known issue with PDF Table of Contents (TOC) reports:

• If a PDF is created with an option other than the WebFOCUS reporting FORMAT PDF option and is uploaded to the WebFOCUS Repository, an error will occur when opening the file. The file may open, but only Table of Contents information will display.

x

The following is a known issue with HTML Table of Contents (TOC) reports:

• When the size of the LEFTMARGIN is customized, only the first table, which is displayed automatically when the request is run, respects this margin. When the second or lower value for the highest-level sort field is selected from the TOC tree, the default size of the left margin is used.

  As a result, when View Entire Report (On/Off) is selected in the TOC tree, two left margin sizes are displayed and a separation of the report into two parts occurs. The first table shows the left margin specified, while all other tables adhere to the default left margin size.

x

The following are known issues with Accordion By Row reports:

• If a large data file is used, the HTML page no longer freezes when expanding or collapsing the tree in an Accordion By Row report.

  However, delays occur depending on the number of records in the sort field. The time it takes a sort field to expand or collapse, depends on the number of records to be displayed. As the number of records increase, the time it takes to expand or collapse the field, will be longer.

• In Internet Explorer 10, Chrome 28.0.1500.95 m, and Safari 5.1.7, an Accordion By Row report shows empty grids, nested to the left of the plus signs (+) and minus signs (-), after the highest level sort field value has been expanded. This does not occur in earlier releases of Internet Explorer or Firefox 25.0.1 and earlier.

x

The following are known issues with EXL2K FORMULA:

• The INT function is only supported if the result is returned to a field defined with an Integer data type.
• The phrase ON byfield RECOMPUTE does not recalculate the formula at the sort break, but rather, repeats the formula from the previous row.
• SET SUBTOTALS = ABOVE may produce incorrect formulas when used with EXL2K FORMULA.

x

The following is a known issue with EXL2K PIVOT:

• NLS characters are not supported in HOLD file names (FORMAT EXL2K PIVOT) when the Reporting Server is set to native code pages, for example, Japanese codepage 942. NLS characters are supported when the Reporting Server is set to 65001 - Unicode (UTF-8).

x

The following issues apply to FORMAT EXL07:

• FORMAT EXL07 and FORMAT XLSX are synonyms and can be used interchangeably. The FILE SAVED message will always display XLSX FILE SAVED, regardless of the format specified to identify that the actual file format generated is the XLSX file structure supported by Excel 2007, Excel 2010, and Excel 2013.
• As of WebFOCUS Release 8.0 Version 06 and Reporting Server 7.7.05M gen 140, reformatting that is applied to virtual fields with dynamic or field-based formats is available for XLSX format, with the exception of packed decimal formats.

x

The following issues apply to the HTML HFREEZE reporting feature:

• WRAP styling is not supported.
• The HFREEZE reporting feature does not support dynamic addition of HTML elements and tags. HTML HFREEZE alignment and scrolling features rely on a specific structure that includes both HTML and JavaScript elements. Inserting additional HTML or JavaScript elements interferes with this structure and is not supported.
• When using a non-Internet Explorer browser, the top and bottom border styling of the column title is missing 1 pixel between the field column titles.

x

The following issue applies to compound layout reports using document composer syntax:

• Prior to WebFOCUS Server Release 7.7 Version 05 gen 115, text markup strings containing the special page variables <ibi-page-number> and <ibi-total-pages> in compound documents displayed embedded spaces between the words and page number values. For example:

  MARKUP=ON, TEXT='Page <ibi-page-number/> of <ibi-total-pages/>',$

  would display

  Page 1      of 100 

  In WebFOCUS Server Release 7.7 Version 05 gen 115, the space can be removed from the text object with WRAP=OFF and no embedded styling between the page number variables. For example, the following code produces a page number string without the extra spaces:

  MARKUP=ON, WRAP=OFF, TEXT='<font face="ARIAL" size=10><i>Page <ibi-page-number/> of <ibi-total-pages/> of Sales Report </i>', $

  would display

                Page 1 of 100            

  The extra space will continue to be presented within text objects where WRAP=ON or styling is embedded in the text string. For example:

  WRAP=ON,MARKUP=ON, TEXT='<i>Page</i> <ibi-page-number/> of <ibi-total-pages/>', $

  would display

                 Page
  1      of 100