8206.04 Release Notes
The following topic provides all the information that you need to know about this release of WebFOCUS.
Have questions? Click Send Us Feedback (on the right) and we'll be in touch!
|Release Date||Gen Information||Reporting Server|
|Friday, August 16, 2019||wf081319a Gen 62||8206 Gen 1742|
New WebFOCUS Integrated Installation
WebFOCUS Integrated Installation is a new, simplified installation, which installs and configures all required product components to allow you to use the product for your reporting and analytics needs.
WebFOCUS Integrated Installation is an all-in-one downloadable installation package. Benefits include:
- WebFOCUS and the Reporting Server bundled with Tomcat, Derby, and Java.
- Hyperstage preconfigured as a high-speed target for uploaded data.
- Simplified configuration for email distribution.
With WebFOCUS Integrated Installation, you can quickly and easily perform reporting and analysis, data discovery, and scheduling and distribution, all in a single web-based environment.
For more information, see WebFOCUS Integrated Installation.
New Integration of the Solr Search Platform With WebFOCUS
You can now configure Solr, an open-source, high-performance, full-featured enterprise-search platform, to work with WebFOCUS features. Solr uses the Apache Lucene Java search library as its core for searching and indexing. The WebFOCUS Integrated Installation and WebFOCUS Client create a directory with zip files that contain Solr indexes for the retail samples data and the Solr Version 8.0.0 distribution archive, which enable Enterprise search and analytics.
The following Information Builders features make use of the Solr platform:
- WebFOCUS Home Page
- Home Widget
- Navigation Widget
For more information, see WebFOCUS Integrated Installation.
WebFOCUS Repository Procedures Are Now Available for Use as Pre- and Post-Distribution Schedule Procedures
The Task Pre/Post Processing Procedures dialog box now includes links to procedures located in the WebFOCUS Repository, as well as the Reporting Server, as shown in the following image.
This new capability expands the range of pre-processing and post-processing procedures you can attach to distribution schedules to include procedures located in the WebFOCUS Repository as well as those located on the Reporting Server.
For more information, see the Schedule Pre-Processing and Post-Processing Procedures topic in the ReportCaster Guide.
Adapter for REST: Enabling Support for Custom Headers
When you configure a connection for the Adapter for REST, you can now add custom headers consisting of name=value pairs that are passed in the HTTP headers.
To add custom headers for a REST connection, on the Connect to Data page of the Web Console, either add REST to the configuration or, if the adapter is already configured, edit an existing connection or add a new connection. In the Advanced HTTP connection options section, click Add Custom Headers.
A text box opens in which you can add the custom header, as shown in the following image.
Custom Header values should be enclosed in double quotation marks, and the individual custom headers should be delimited by semi-colons (;). For example:
Custom headers can also be created in the metadata as part of the process of creating a synonym. Defining custom headers in the connection string makes the custom headers apply to the entire REST service. Defining the custom headers at the metadata level makes the custom headers apply to the specific REST call, and the custom header values can be changed at report time using WHERE or IF statements.
For more information, see Adapter Administration.
Automatically Adjusting Only the Width of a Chart
This feature enables you to adjust only the width of a chart without adjusting the height, giving you more flexibility in displaying chart output. When the AUTOFIT parameter is set to ON, chart height and width are adjusted to fit the size of the container. When the AUTOFIT parameter is set to WIDTH, the width of the chart is adjusted to fit the width of the container without adjusting the height.
For more information, see Creating HTML5 Charts With WebFOCUS Language.
- When creating a chart from App Studio, the Run with OLAP property is enabled when it should not be. (190730106, 190722101, 190729102)
- Unable to control borders within internal cells in a heading and footing in XLSX or HTML reports. (20553557, 70352006, 80172024, 90592515, 92672521, 11813555, 30393512, 161012021, 170125094, 170223043, 170428050, 170517097, 170621009, 30063540, 160329026, 22093513, 180522092, 190320059)
- A report containing many spot markers for fields is triggering an agent crash error. This occurs with all styling formats. (190529056)
- An XLSX report may not open when a numeric field used in a styled multi-item heading is either zero, formatted with the S option, or missing with the NODATA set to a blank value. (190108003)
- User receives unreadable content errors while running an XLSX template report and trying to open the report in Excel 2010 or Excel 2013. (190725070)
- In App Studio, the Action, Method, Enctype, and Accept properties have been removed from the Form component in the Properties panel because these properties were not actually being used.
- When upgrading from previous versions of ReportCaster, FTP setting configuration information remains available in existing distribution schedules as long as the default value (Customized FTP) is assigned to the FTP Server Name field.
- If you replace this value with a predefined FTP setting configuration in an individual schedule, the previous FTP Setting configuration information for that schedule is overwritten automatically.
- If you limit FTP Setting configurations to a predefined list by selecting the Don’t allow user defined FTP in schedule check box in the (Default Settings) configuration, the previously FTP Setting configuration information for all schedules becomes unavailable, and is replaced by the default FTP Setting configuration or a predefined FTP Setting configuration selected for an individual schedule.
- After an upgrade to Release 8206, only those users working in roles that include the new Create Shortcuts (opShortcut) privilege, located in the Basic Reporting privilege category, can continue to create shortcuts. Even though this privilege is included in the DomainBasicUser, DomainAdvancedUser, DomainDeveloper, DomainAnalyst, and WebFOCUSManager roles, it is not selected by default. Administrators must either select the Create Shortcuts privilege check box directly, or use the Role Update utility, located on the Configuration tab of the Administration Console, to include this privilege in each of the roles that can continue to use this feature.
- The following changes appear on the InfoAssist Properties page of the Administration Console Configuration tab. These changes were called for by In-Document Analytics rebranding, and they match changes to the labels of the corresponding format options in the Output File Format list that opens from the Format Group in the InfoAssist Home Page ribbon.
- In the Format Tab section, the Active PDF option was renamed PDF Analytic Document Format and the Active Report option was renamed HTML Analytic Document Format.
- In the Report Output Format, Chart Output Format, and Document Output Format lists located in the Tools Options Dialog Defaults section, the Active Report option was renamed HTML Analytic Document and the Active PDF option was renamed PDF Analytic Document.
- The functions previously categorized as Statistical Python functions have been reclassified as Machine Learning (Python-based) functions. The names of the functions have changed as follows:
- BLR_CLASSIFY is now named CLASSIFY_BLR.
- KNN_CLASSIFY is now named CLASSIFY_KNN.
- KNN_REGRESS is now named REGRESS_KNN.
- RF_CLASSIFY is now named CLASSIFY_RF.
- RF_REGRESS is now named REGRESS_RF.
- POLY_REGRESS is now named REGRESS_POLY.
- The enhanced In-Document Analytics user interface available is configured by default for new installations and is not supported with the Microsoft Internet Explorer 11 browser. If you have requirements to support Microsoft Internet Explorer 11 browser, you can configure the Legacy In-Document Analytics user interface using the WebFOCUS Administration Console.
Customers upgrading to 8206 from 8205 or earlier releases will have the Legacy In-Document Analytics user interface configured.
The new In-Document Analytics setting appears in the Tools Option Dialog Defaults section of the InfoAssist Properties page, which is located on the Configuration tab of the Administration Console. This setting establishes the default value for the In-Document Analytics setting in the Procedure Settings dialog box which opens from the InfoAssist Quick Access toolbar. The value in this setting determines the interface used to display reports, charts, and documents using the HTML Analytic Document format. There are two valid values:
- Designer Style. Content displayed conforms to the conventions of WebFOCUS Designer and includes the Navigation icons, such as the Chart Format menu and the ellipsis menu.
- Legacy. Content displayed conforms to the legacy run-time interface and provides options like the legacy column menu.
Content created in earlier versions is automatically assigned to the Legacy display, which conforms to the conventions of the Active Technologies format, and provides options like the Chart/Rollup and Pivot tools.
New content is automatically assigned to the WebFOCUS Designer option, which is selected by default.
To convert content created in earlier versions to the WebFOCUS Designer display, developers must open that content for editing, reset the value in the In-Document Analytics setting to Web FOCUS Designer, and save the revised procedure. As an alternative, developers can use the text editor to add the following commands directly to a procedure.
-DEFAULTH &WF_ARVERSION=2; SET ARVERSION=&WF_ARVERSION;
- To prevent unexpected field transformations, when creating a chart in WebFOCUS Designer, the buckets are type sensitive. Certain buckets, such as the Size and Tooltip buckets, only accept measure fields, while others, such as the Horizontal and MultiPage buckets, only accept dimension fields. Additional buckets, such as the Vertical and Color buckets, accept both field types. When you attempt to drag a field into an incompatible bucket, the cursor changes to a cancel sign.
To add a measure field to a dimension bucket or a dimension field to a measure bucket, right-click a field in the Fields panel and click Add as dimension or Add as measure. The field is added to the default dimension or measure bucket. You can drag the field into another bucket, as needed. As in previous releases, measure fields used as dimensions display as distinct instead of aggregated values, while dimension fields used as measures are aggregated using the Count operation.
- If, in Release 8206.03 and higher, when migrating a chart created in InfoAssist to WebFOCUS Designer, the chart type is not supported and a similar chart type cannot be found, the chart is converted to a bar chart. You can then modify the bar chart in Designer. Previously, the chart type was maintained, but the buckets were not accessible and the chart could not be edited. Affected chart types include 3D charts, stock charts, and polar charts.
Note: To open an InfoAssist chart in WebFOCUS Designer, you must have the associated Technical Preview enabled. For more information, contact your Information Builders representative.
- In Release 8206, the default value assigned to the Account Creation on Sign In (IBI_ALLOW_LOGIN_EXTERNAL_GROUPS) setting, located on the External page of the Administration Console Security tab, changes from All to OFF. If you must continue to use All as the default value in this setting, after upgrading to Release 8206, you must open or create the webfocus.cfg file, type the IBI_ALLOW_LOGIN_EXTERNAL_GROUPS=* setting in it, including the asterisk (*) value, which represents All, and then save the updated file.
- WebFOCUS page breaks in format XLSX report output are synchronized with Excel page breaks. To revert to the behavior in previous releases in which page breaks were not synchronized, issue the SET XLSXPAGEBRKIGNORE=ON command.
- When clicking a column for a report that has only the Freeze option enabled, and the width of the report container is big enough to display all columns, a blank column menu displays.
- If you are working with an In-Document Analytics chart in landscape mode on an Android mobile device and you switch to portrait mode, your content displays in fullscreen mode. Your chart displays at the bottom. If you run your content in new window mode, your In-Document Analytics chart does not display in fullscreen mode, displaying the chart on the right.
- When working in Document mode with In-Document Analytics, an error occurs if you attempt to run a document or dashboard using Internet Explorer 11.
- When creating bar charts using the New option on the Ellipsis menu, the Color bucket incorrectly performs a count for a dimension field. It also shows a heat legend. The expected result is a color legend for each unique item.
- If you add an existing ARVERSION=1 report to an AHTML document set to ARVERSION=2, it fails at run time, displaying JSON text on the screen instead of the expected report output.
- Running the configuration migration from the CMD line or UNIX Shell displays an error message in the log file. This error does not impact migration of the configuration files.
- After running WFReposUtilCMDLine.bat or WFReposUtilCMDLine.sh, the RPT_DATA, RPT_METADATA, and RPT_USAGE tables are not getting dropped and are still available in the repository.
- If you attempt to run an ARVERSION=2 (In-Document Analytics) AHTML Fusion chart procedure (.fex), it continuously loads and produces an F12 error. This does not occur with Fusion charts that employ ARVERSION=1.
- If you are working with a procedure (.fex) and you change the ARVERSION to ARVERSION=2, global filters do not display when you run the procedure.
- When you use the WebFOCUS Online Help in Japanese, if you type a search term in the Search box that contains NLS characters and press Enter, the words next to the Search box are corrupted. The workaround is to click the Go button next to the Search box, instead of pressing Enter.
This release is now certified and has been tested with Google Chrome version 76, Firefox Quantum version 68, Microsoft Edge version 44, and Internet Explorer version 11.