This topic describes resolutions or solutions in GainSeeker versions 9.2 and 9.2.1, and corrections to the Online User Guide.
|
Contents [Hide] |
When a dashboard contained a DPU Yield Chart or a DPU Cost Chart, but no data existed for that chart, an "Object reference not set to an instance of an object" error was generated. This issue has been resolved.
When using the System Administration module to compare two configurations, some items were not included in the comparison: traceability labels for fields 7 and higher, statistics labels, real-time error messages, colors for drill-down Pareto charts, and Inspection unique ID expiration. This issue has been resolved.
When editing the list of defects for a DMS process, GainSeeker would fail to save any newly-created defects to the process defect list (on the right-hand side). The user had to close all windows related to editing the process before GainSeeker would allow them to add these new defects to the process defect list and store them correctly. This issue has been resolved.
Right-clicking on a DMS data table and using the "Edit Data Range" function to set the DMS Event for one or more records would set the wrong DMS Event and incorrectly logged the change to the Audit Trail. This issue has been resolved.
When displaying a Dynamic Report, an "Evaluation" watermark was erroneously added to the report. This issue has been resolved.
The Online User Guide topics for Installing GS Analyze and Installing GainSeeker Mobile Web Service have been updated to reflect that the current version of these applications is 9.2.
The Online User Guide topic for Workstation Requirements incorrectly listed Microsoft .NET Framework version 4.5 instead of 4.6.1 as a prerequisite to installing the GainSeeker client. (.NET Framework version 4.5 is still required to run GS Analyze.) This issue has been resolved.
Some GainSeeker functions that used the Windows Clipboard to copy information would crash if the Clipboard could not be accessed. GainSeeker now performs these functions without crashing, even if Clipboard cannot be accessed. This issue has been resolved.
When a chart was stored in a Desktop, opening the Desktop would display the chart with fonts larger than the original chart. This issue has been resolved.
Opening a Desktop that contained a progression of drill-down Pareto charts failed to display the correct drill-down colors and footer information for those charts. This issue has been resolved.
Opening a Desktop that contained an External Data chart would sometimes generate a "NullReferenceException" error message. This issue has been resolved.
When a chart of External Data was displayed using only the Default settings, editing the Settings for that chart would erroneously display some of those settings in blue to indicate that they did not match the default settings. This issue has been resolved.
When certain charts were displayed, a user could click the "X-axis" toolbar button and make changes to the chart - even if that user's role was denied permission to change chart settings. This issue has been resolved.
A Dashboard control with a scripted retrieval that did not find any data would cause GainSeeker to stop working. This issue has been resolved.
A Dashboard Grid control that was filtered by traceability field 7 or higher would sometimes fail to display any results in that control. This issue has been resolved.
A Dashboard Grid control with the "Detail Defects" property set for a specific defect failed to display any results for any of the "[Detail]..." statistics. This issue has been resolved.
When a dashboard contained a Button control or Marquee control with the Retrieval set to "No Retrieval", opening that dashboard could sometimes fail to display any text on that control. This issue has been resolved.
When a dashboard was displayed, clicking the toolbar buttons "Date Period" or "Filter" would generate an "Unhandled exception" error. This issue has been resolved.
Opening a Multiple Data Table with more than ~6500 columns could generate an error message such as "Sum of the columns - FillWeight values cannot exceed 65535". This issue has been resolved.
For OEE Charts grouped by 5, 10, 15, 20, or 30 minutes, a data point that fell exactly on the division between two time groups was incorrectly added to the earlier group instead of the later group. This issue has been resolved.
When saving current chart overrides as a new Chart Skin, an "Open Without Saving" button was erroneously displayed. This issue has been resolved.
When using the "Edit data range" function on a data table and setting a new value with a single quote, two single quotes would actually be stored. This issue has been resolved.
Drawing a Combined Control Chart or Multiple Data table and using a traceability value for the "Columns used to match rows from different retrievals" setting would cause GainSeeker to report an error. This issue has been resolved.
The sort order of SPC standards displayed when editing those standards was sometimes different from how those standards were sorted when creating an SPC chart. This issue has been resolved.
When using a shortcut to email a Dynamic Report to multiple recipients, GainSeeker ignored the ExportList= parameter in the shortcut and sent email to the wrong recipient. This issue has been resolved.
When opening a very large inspection for editing, it was possible for additional tests to be erroneously added to a sub-inspection. This issue has been resolved.
When the Label for a Traceability test contained a hyphen (-), the Inspection Editor window did not display that test's label correctly. This issue has been resolved.
When a sub-inspection contained a Traceability test configured for Text Entry, and the Label property was set for that test, copying and pasting that test would not display the Label on that test. This issue has been resolved.
When editing the TestSpecificTrace property of a test that stores data (such as a Checkbox test or Numeric Input test, for example) in a configuration with more than nine traceability fields defined, those traceability fields were ordered incorrectly. This issue has been resolved.
When editing a Planned Inspection, traceability fields that are not set to "Display Traceability Label" were erroneously displayed. This issue has been resolved.
For the Checkbox test, the ClearValue property was never implemented in PC Collect, and changing this property had no effect on inspection data entry. This property has been removed from the Checkbox test. This issue has been resolved.
When editing a Text test where the Label property is blank, clicking the ellipsis button for that Label property would generate an error. This issue has been resolved.
Inspections published in version 9.1 were not displaying the last test of every sub-inspection in GS Collect. This issue has been resolved.
While running an inspection in Debug mode, if the Python Script Editor window had the focus even though a script was not currently running, the toolbar buttons for Save, Start/Continue, Step, and Stop were disabled but their corresponding keyboard shortcuts (CTRL+S, F5, F8, and ESC, respectively) were still functional. In the case of F5 (Start/Continue) and F8 (Step), using these keys would actually launch a second instance of the inspection. The keyboard shortcuts CTRL+S, F5, and F8 are now disabled when a script is not currently running. This issue has been resolved.
When a sub-inspection contained both a Click formula and an OnChange formula, the Click formula could erroneously fail to trigger if the inspector changed the value of a test that would trigger OnChange when focus was lost, and then clicked that formula button. This issue has been resolved.
An OnChange formula could erroneously fail to trigger if the inspector first changed the value of a test that would trigger OnChange when focus was lost, and then clicked on a test that would immediately trigger OnChange. This issue has been resolved.
An OnChange formula could be erroneously triggered even when the inspector did not change the value of a test. This could happen for any Traceability test with the EntryRestricted property set to False, for a Defect List test with Sample Size greater than 0, and for any Date/Time test. If the test got focus and then lost focus - typically because the inspector clicked on (or tabbed to) the test and then clicked (or tabbed) away - the OnChange formula would be triggered, even if the inspector did not change the value of that test. This issue has been resolved.
An OnChange formula could be erroneously triggered even when the inspector did not change the value of a test. This could happen after a Python script was used to change the value of a Traceability test with the EntryRestricted property set to False, a Date/Time test. a Numeric Input test, or a Defect List test. If the test got focus and then lost focus - typically because the inspector clicked on (or tabbed to) the test and then clicked (or tabbed) away - the OnChange formula would be triggered, even if the inspector did not change the value of that test. This issue has been resolved.
An OnChange formula could erroneously fail to trigger in the following scenario. After a Python script was used to change the value of the Traceability test with the EntryRestricted property set to True, if the Inspector changed the Traceability test back to its previous value (before the Python script was run), no OnChange formula was triggered. This issue has been resolved.
An OnChange formula could erroneously fail to trigger if a Timer test that was running a countdown timer registered zero seconds while another Python script was already running. In this scenario, the OnChange formula is now queued to execute as soon as the currently-running Python script finishes. This issue has been resolved.
An OnChange formula that executed disp.message() could sometimes cause two tests to appear to have focus at the same time. This issue has been resolved.
When a sub-inspection with the ForceNote property set to require entry had a Numeric Input test with a real-time failure, and the inspector did not use that test's individual Note button to enter the required information, clicking the Submit button would display the individual note for the test with the real-time failure but failed to display the real-time failure color in the note portion of this window. This issue has been resolved.
When running an Inspection in a maximized window, that window would be quickly resized and then maximized each time side panel items were refreshed. Each time this occurred, the inspection window would flash and scroll from its current position to the top of the page. This issue has been resolved.
When running a planned inspection that configured one Numeric Input test to be invisible, that test's sub-inspection failed to display the charts for any visible Numeric Input tests. This issue has been resolved.
If a sub-inspection displayed a Statistics List or Statistics Table, but neither the current Chart skin (if specified) nor the current GainSeeker configuration specified a report name for that type of statistics chart, opening that sub-inspection would always prompt the inspector to select a report format for displaying that chart. Now the PC Collect module will display system default statistics in this situation, instead of prompting the inspector to choose a report format. This issue has been resolved.
Opening a sub-inspection that displays a Monitor Table or Process Capability chart on the side panel would generate an error message. This issue has been resolved.
When displaying the list of sub-inspections, a long Inspection name could sometimes be truncated. This issue has been resolved.
For users who were denied access to the PC Collect module, PC Collect was correctly removed from the LaunchPad, but these users could still run the PC Collect module directly via a shortcut or the by running the executable itself. This issue has been resolved.
When using Microsoft Outlook to send email from GainSeeker, the email message generated by a Numeric Input test configured to send real-time failure email to multiple recipients was invalid because it specified a comma-separated list of email addresses instead of a semicolon-separated list. The list of email addresses is now automatically updated with semicolon separators when sending Outlook email. This issue has been resolved.
When using Microsoft Outlook to send email from GainSeeker, no information was displayed to the user if Outlook was unable to send the message. Outlook errors are now displayed to the inspector. This issue has been resolved.
When using the built-in SMTP email function, a Numeric Input test that was configured to auto-send real-time failure emails would erroneously display the email window to the inspector instead of automatically sending the email. This issue has been resolved.
After using a Python script to hide a Numeric Input test by setting its .visible property to False, if that test remained hidden while any combination of executing inspect.update() or ending a Python script happened twice it a row, setting that test's .visible property to True would fail to display that Numeric Input test. This issue has been resolved.
After using a Python script with inspect.messagearea.script to change the message area at the bottom of the sub-inspection into a clickable button, setting inspect.messagearea.script to an empty string would erroneously continue to display a button border even though the message area was no longer a clickable button. This issue has been resolved.
When a Traceability test had a value in its TraceabilityPrep property, opening a Planned Inspection that was configured to set a different value for that Traceability test would erroneously prefill the value from the Inspection's TraceabilityPrep property instead of the Planned Inspection's traceability value. This issue has been resolved.
In previous versions, some Excel files created with Excel 365 could not be used with the file.xls Python commands. This issue has been resolved.
The list of GainSeeker tables generated by right-clicking on any configuration and choosing "View as Text > Tables and Paths (current)" or "View as Text > Tables and Paths (all configurations)" contained some trivial errors such as listing the Audit Trail table twice and listing table names like ERPFT_JOB and WORKHOURS which are not actually used to store GainSeeker data. This issue has been resolved.
GainSeeker users without permission to delete Audit Trail records were still able to delete these records. This issue has been resolved.
When creating or editing a shortcut for PC Collect, this module erroneously displayed a "Debug" check box. (Checking this box no longer affects how this shortcut functions.) This checkbox has been removed, and the issue has been resolved.
GS Analyze would display "8 hours ending now" even when the configuration setting for Last n hours ending now was set to a different number of hours. This issue has been resolved.
Some properties were not capitalized correctly when returned from the web server. This issue has been resolved.
Setting the date period to Fixed Range would display "Internal Server Error". This issue has been resolved.
Characters like á, é, í, ó, ú, ü, ñ, etc. were not displaying correctly in data grids in the GS Collect app. This issue has been resolved.
The topic for the DateTime Dashboard Control has been corrected to reflect that the "No data" label and color are displayed if the next scheduled data collection is more than four hours overdue.
The topics for SPC Chart Options and DMS Chart Options have been corrected to reflect that after any traceability changes or a Python script is executed by a Formula test, the side panel charts for the current sub-inspection will be refreshed.
The topics for Running standalone Python scripts in GS Console and Changing the settings for a Role have been updated to reflect that logging in to GS Console requires permission for Module Access to PC Collect.