This describes the resolution of known issues in version 8.1 and corrections to the Online User Guide.
When the previous version of GainSeeker was configured to use the "Subtract" method for the default low date, the upgrade to GainSeeker version 8 incorrectly set the amount of time being subtracted in the new version. For example, a default low date of "subtract 14 hours" was incorrectly converted into "subtract 14 months". Also, converting this "Subtract date" to the format needed for GainSeeker version 8 sometimes generated an error 6 (memory overflow error). These issues have been resolved.
When an SPC standard with a subgroup size of 2 or greater was configured to display a Moving Range chart (instead of a Range chart or Sigma chart), there was an error in the calculation of the R-Bar statistic. This also affected any other statistics whose calculations were based on the R-Bar statistic. This issue has been resolved.
On the Users tab, if you assigned a user to the Role that had an internal identification number of 3, the system would automatically change that user's role to the Data Entry Operator pre-defined role. In the previous version, the easiest way to work around this problem was to "retire" this particular role and make a new copy of it that you could correctly assign to users. This issue has been resolved.
In GainSeeker version 8, the Administration module allows you to enter a user name that is longer than 20 characters, but some GainSeeker tables can only accommodate the first 20 characters of the user name. The Administration module has now been updated to ensure that the first 20 characters of each user name will be unique. This module has also been updated so that when a user name is renamed or deleted, any priority lists and stored sessions assigned to that user name will be renamed or deleted.
The Cms.ini settings web_inactive=, web_log=, web_purge=, web_pws= and web_url= were used only by GainSeeker WebSPC. Because WebSPC has been replaced by GainSeeker WebViz, which does not use any of these settings, they have been removed from the CMS.ini Settings screen in the Administration module and from the Online User Guide.
If the user worked with SPC standards and then tried to work with traceability labels and lists for the same configuration, they were only able to work with the first six traceability fields instead of the 48 available traceability fields. A similar issue prevented the user from setting an SPC standard to a subgroup size greater than eight. These issues have been resolved.
The steps for creating a new user, role, configuration and database connection have been updated for consistency across these tabs.
When multiple users created dashboards at the same time, and the names of these new dashboards all began with an identical sequence of six alpha-numeric characters, GainSeeker sometimes pointed multiple dashboard names to the same source file instead of pointing each dashboard name to its own source file. This issue has been resolved.
When a KPI Gage dashboard included a "File or URL" gage, refreshing the dashboard or doing a complete refresh could sometimes lose the file or URL being referenced by this gage. This issue has been resolved.
In all of the datasets that are automatically created from the Retrieval Settings you choose, the field names in each dataset are automatically updated to remove and/or replace any special characters (such as spaces, dashes, parentheses, etc.) found in those field names. In the previous version, special characters in these field names sometimes prevented custom code from performing correctly. You can update any report that was created in the previous version (GainSeeker 8.0) by viewing the Retrieval Settings for that report and then saving the report.
If the user configured the Retrieval Settings for an Advanced Report to retrieve multiple defect names and defect counts, and if the user selected at least one DMS statistic in the Retrieval Settings, then on the Report Designer window only the first defect name and defect count was shown. (If the DMS statistic was removed from the Retrieval Settings, then all defect names and defect counts specified in the Retrieval Settings were shown in the Report Designer window.) This issue has been resolved.
If the user configured the default printer for landscape mode and then created a dynamic report, viewing or printing the report would correctly render the report in landscape mode. However, sending the report to a file format such as .jpg or .pdf incorrectly rendered the report in portrait mode instead of landscape mode. This issue has been resolved.
When viewing a report, clicking the toolbar button to show or hide the sidebar could make the Sidebar item on the View menu incorrectly display a check mark when the sidebar was not currently displayed. This issue has been resolved.
When viewing a dynamic report, it was discovered that you can
refresh the data on the report by clicking the View menu and
then clicking Refresh, or by clicking the button, but not by
pressing the F5 key. For this reason, references to the F5 key have
been removed from the View menu and the button, and the Online
User Guide topic for Viewing
and Sending Dynamic Reports has been updated with instructions
for refreshing the data on the report.
Similarly, it was discovered that the Auto refresh report property
does not refresh the data on a dynamic report. (This property can
be found by clicking the Report menu, clicking Report Properties,
and then clicking General - or by viewing the Property grid
for the Report and going to Misc\AutoRefresh.) The Online
User Guide topic for Introduction
to the Report Designer window has been updated with instructions
to disregard this property.
If GainSeeker was first configured to "Show time to" seconds and a DMS data record was stored with a Note attached, changing the configuration to "Show time to" minutes could make this note appear blank. This issue has been resolved.
When building a chart for multiple parts and processes, if the user first selected multiple processes and then selected only a few of the part numbers available for one of those processes, then the resulting chart would sometimes reflect other part numbers that had data for that process. This issue has been resolved.
The text that explains the order in which feedback commands will be executed has been updated for clarity. You can view this explanation on Template Wizard Step 5 by clicking Row n feedback and then clicking View Order.