This describes resolutions or solutions to issues in GainSeeker versions 8.3.1 and 8.3.0 and corrections to the Online User Guide.
|
Contents [Hide] |
Prior to version 8.3.1, some newer GainSeeker modules would run as 64 bit on computers with 64-bit operating systems, and 32 bit on operating systems with 32-bit systems, causing some problems for users with 64-bit systems and connections to ODBC datasources. This issue is resolved.
Part number searching was disabled in GainSeeker Charts when the Show standard list first setting checkbox was cleared and the Automatically fill standard list and Hide standard list settings checkboxes were selected for a configuration. This issue is resolved.
When the Number Good label= value was changed for a configuration, the change did not display on a DMS Data table. This issue is resolved.
The Anchor label = setting can now only be changed in the settings for a configuration in the GainSeeker Systems Administration module. Formerly it was also available in the Charts Overrides node of the Settings tab.
When external data was saved, the standard did not save with the data. This issue is resolved.
When an attempt was made to import a file that was in an incorrect format, GainSeeker would terminate and display an error message. This issue is resolved. GainSeeker now displays a message stating that the file is unable to be read.
When a default date period for the DMS Charts & Reports, SPC Charts & Reports, or SPC Data Entry setting was changed from Default low to today in the System Administration module, the label for the setting’s value did not update. This issue is resolved.
When a configuration was copied to a new configuration name, all of the settings for the original did not always copy to the new one. This most often occurred when settings for the original were changed between the time the Systems Administration module was opened and the Configuration was copied. This issue is resolved.
Rights to the new GainSeeker Charts module and the legacy SPC and DMS Charts and Reports modules were previously combined. Limiting users to one or the other was not allowed. This issue is resolved.
To enable the Macro Launch utility to recognize a filename, double quotation marks had to be omitted before and after the name. Using double, single, or no quotation marks is now acceptable. Double quotation marks must still be included for the entire path and name if the Launch.Exe path contains spaces.
The GainSeeker System Administration module now uses a license.
The error message Unrecognized role audit number 803 sometimes displayed when a user attempted to change a password in some modules. This issue is resolved.
When users assigned a new label to any of the statistics labeled Standard variable 1–4, GainSeeker did not always display the user-assigned label. This issue is resolved.
The MARPOSS_CONNECT and MARPOSS_ACQUIRE commands enabling GainSeeker to interface with Marposs device EasyBox U4F and some others, unloaded the Marposs form with too much frequency. The new MARPOSS_DISCONNECT and MARPOSS_UNLOAD commands remedy this.
Blank charts windows were sometimes the result when the SPC Data Entry window was resized. While that issue is resolved, depending on the number of charts that are simultaneously displayed, resizing may leave a small remnant of a chart if one of the charts is maximized when the data entry window is resized.
When an RS_Status command was terminated by a user before a reading was taken or before it "timed out," a syntax error message displayed. This issue is resolved.
Between GainSeeker versions 8.1 and 8.2.1, the data entry process significantly slowed when a Short Run retrieval query was selected. This issue is resolved.
If a row in a template was not set to display a chart, DE_OPT 29 read the incorrect row. This also occurred if a user attempted to read Row 2 or beyond in a template that contained multiple rows. This issue is resolved.
The previous cell sometimes displayed the color for the last subgroup value instead of the color for the individual value. This issue is resolved.
When a user removed a note associated with a data point, the note marker still displayed on the control chart for that data point. This issue is resolved.
If the third parameter was omitted for the Q_COLUMN command, the syntax checker did not generate an error and the system would generate unreliable results during execution. This issue is resolved.
When multiple part numbers were selected for an SPC report, the retrieval included bypassed data. This issue is resolved.
When two filters were combined and one of the filters only specified how data should be ordered, GainSeeker displayed an error message. This issue is resolved.
The same color dialog is now used throughout the GainSeeker Charts module.
When a user had a blank test value when creating or editing a filter, the filter sometimes failed. This issue is resolved.
After a group of DMS charts was created and some settings for a chart were subsequently changed, when the chart redrew, it reflected all the settings and data for the first part number picked when the chart group was first created. This issue is resolved.
When a user attempted to close multiple GainSeeker Charts windows using the right-click menu for the module’s icon on the taskbar, an error message sometimes displayed. This issue is resolved.
Brushing data on a short run chart sometimes produced unexpected results when a new chart was drawn using the brush data points. This issue is resolved.
When a note for a cause, event, or corrective action taken was changed for chart data, the related text sometimes failed to display. This issue is resolved.
When a color was selected for the background of a Combination chart, only some of the background area displayed the selected color. This issue is resolved.
When a Combination chart was stored on a desktop, the statistics list below the chart sometimes did not display. This issue is resolved.
When the font size was changed for a chart element, sometimes an unexpected font size displayed. This issue is resolved.
When two or more desktop charts of different sizes were sent to email, the resulting chart images were also differently sized. Each chart is now maximally sized when it is sent.
Title 2 and Title 3 chart title settings are not used for SPC multiple retrieval charts.
The Data - Line width and Data - Line type settings on the Settings tab were incorrectly used to determine how bars on DPU charts displayed. This issue is resolved.
When an improvement line was used for a DPU chart, GainSeeker ignored the DPU improvement Goal setting value on the Settings tab. Instead, it used the default value for that setting in the GainSeeker System Administration module. This issue is resolved.
When a Variation Wizard user changed the data type for a traceability field to continuous data, and the data contained blank fields, GainSeeker did not return a value for the variation test. GainSeeker now calculates and returns a value that ignores any blank fields that may be present.
When a Statistics List for a DMS multiple retrieval was sent to a word document or to Excel, the list displayed twice under certain circumstances. This issue is resolved.
After a user entered a title for a chart using the Print Title / Company name = setting on the Settings tab, the title could be changed, but not removed from the chart. Users can now clear the setting value to opt out of displaying a title.
The Line Type setting for chart data on control-type charts could not be changed from a solid line. This issue is resolved.
When the label color for Control Limits on a Trend chart was changed from black, the font remained black. This issue is resolved.
When a DMS Events list was edited after an SPC Events list had been edited, the event list displayed the SPC list for the DMS record. This issue is resolved.
When a user changed from one configuration to another, only the standards associated with the original configuration displayed in the Select Part Number dialog when standards were edited. This issue is resolved.
When a chart was drawn for brushed data that contained bypassed points, the data was not bypassed on the new chart. This issue is resolved.
When a Statistics Table contained percentage values, the columns sometimes did not correctly sort. This issue is resolved.
Control chart
When a Control chart was grouped by hour, the chart axis labels sometimes failed to correctly display. This issue is resolved.
When a user double-clicked the title bar of a Combined Control chart window to maximize it, the chart display over-magnified. This issue is resolved.
The data grid scrolling items for a Control chart did not use the decimal place number that was set for the standard. This issue is resolved.
When a Pareto chart with no defect data was refreshed, some chart elements displayed abnormally. This issue is resolved.
The Pareto detail column for % of total cost and the plot points and percentages listed for the Pareto - cost as % of total cost chart now accurately reflect the defect cost values if the Use cost information from setting value is set to Defect list. The calculated values were previously and incorrectly based on the NCU cost.
A single-bar Pareto chart scaled disproportionately large on the top x-Axis of the chart. This issue is resolved.
In some cases, the traceability value did not display when data for a Pareto chart bar was sorted by Event. This issue is resolved.
When more than 12 data groupings were displayed on a Performance chart, some chart labels could be difficult to read. Now GainSeeker automatically reorients the top and the bottom chart labels to display vertically under that condition.
When the Statistics Report option was selected on the right-click menu for a Performance chart, the change reflected on the Statistics under chart setting instead of the Statistics under Performance chart setting. This issue is resolved.
The Title 2 and Title 3 chart title settings for Performance charts did not recognize set user values. This issue is resolved.
When the defects/counts were edited for a data record on a DMS Data Table, the % of Sample did not correctly update. This issue is resolved.
When the Edit Data dialog was opened for a DMS Data table record, the date and time it was opened was saved in the note field of the dialog, even if no changes were made to the note. This issue is resolved.
Some options did not always display on the right-click menu for a DMS Data table. This issue is resolved.
The Open/Edit dialog sometimes displayed incorrect filtering options for the Dashboard Grid control. This issue is resolved.
When the main dashboard window is small or irregularly shaped, some chart elements sometimes failed to correctly size. This issue is resolved.
When no filter was found, the DateTime Display Options dialog sometimes displayed an error message. This issue is resolved.
When a dashboard Chart control was saved as a file using the control's right-click Send Control To option, the resulting .jpg file or HTML web page sometimes did not properly display. This issue is resolved.
The BackgroundImage property for the Chart dashboard control has been replaced by the more flexible Chart Skin property. The replacement was due to a potential conflict between the two properties.
When the Send Control To or Save as File option was selected for a Chart dashboard control, the resulting file did not always save in the correct format. This issue is resolved.
When a dashboard without a window caption was sent to email, the name field for the dashboard to be sent was blank. Now, the given dashboard name displays if no dashboard window caption is present.
The Chart... right-click menu option for a Chart dashboard control was unavailable. This issue is resolved.
The user-specified URL on an HTML dashboard control did not always correctly display on a running dashboard. This issue is resolved.
When colors were set for the ExtendColorUpper and ExtendColorLower properties for a Bar Gage dashboard control, the colors did not save. This issue is resolved.
When a Dashboard Grid control containing sparkline cells was sent to email, the GainSeeker Charts module sometimes displayed an error message and ceased operation. This issue is resolved.
When the date period for a dashboard was changed, any Dashboard Grid controls it contained sometimes failed to update accordingly. This issue is resolved.
The Settings tab values for a chart generated from a Dashboard Grid control did not always reflect what was correctly displayed on the actual chart. This issue is resolved.
When Dashboard Grid control data was refreshed, any column sizes a user manually adjusted on the grid were lost during the refresh. This issue is resolved.
When a chart was drawn from the data for a Dashboard Grid control, the chart titles failed to display the specified part number and date range other than "All Dates." This issue is resolved.
When a row on a Dashboard Grid control was defined by part number and grouped by a traceability, the control malfunctioned. This issue is resolved.
In previous GainSeeker versions, the Last XBar statistic for the Dashboard Grid control was not formatted to the correct number of decimals. This issue is resolved.
When rows on a Dashboard Grid control for a DMS retrieval were defined by part number and process, and alert colors were set, the colors did not correctly display. This issue is resolved.
The descending and ascending sort options for columns on a Dashboard Grid control were reversed with the exception of the first column. This issue is resolved.
If a pass/fail color was not specified for a statistics filter in a Dashboard Grid control, some columns displayed no color and had undecipherable text. This issue is resolved.
When a traceability field greater than the sixth field was used in a filter for a Dashboard Grid control, no data was returned. This issue is resolved.
The [Detail] statistics did not correctly display information for a Dashboard Grid control. This issue is resolved.
When a Control chart that displayed a data grid header was saved on a desktop, some highlight colors on the grid that are used to denotes events did not correctly display. This issue is resolved.
When a user sent a desktop containing dashboards to an RTF file, the desktop and any charts windows on it were sent to the file, but not the dashboards. This issue is resolved.
When data for a desktop chart originates from a dashboard control, neither the data or the notes can be edited for that chart.
When the main desktop window is small when the items on it are saved or the window is irregularly shaped, the chart fonts sometimes failed to correctly size. This issue is resolved.
When a filter was changed for a group of charts stored on a desktop, the part numbers used for the retrieval would sometimes change. This issue is resolved.
When a Traceability test was added to a sub-inspection in the GainSeeker Inspections module, the traceability information did not always correctly save when the inspection was run from a mobile inspection. This issue is resolved for any new inspections created using GainSeeker Service Pack 8.3.1 or beyond. For pre-existing inspections, this issue can be remedied using the following method:
Open the inspection in the Inspection Editor, which is used to create inspections. This opens the inspection in edit mode. Then, resave and republish the inspection.
When GainSeeker tested the syntax for an Inspection Editor Formula sub-inspection test, the validation program failed to operate properly, causing an error message to display. This issue is resolved.
The names of users assigned to run an inspection cleared when the inspection was published. This issue is resolved.
If any part of a command line argument had a word containing the letter s, it enabled silent mode. This issue has been resolved. Now, the letter s can be independently used as a parameter to enable silent mode.
GainSeeker did not use the regional settings for a workstation when importing data. Thus, GainSeeker did not always recognize every record. This issue is resolved.
The revamped Standard Utility function in the GainSeeker Utility module allows you to import and export both SPC and DMS standards. These capabilities were limited to SPC standards in earlier versions.
When a traceability field greater than six was edited for the GainSeeker Lists or the Priority Lists functions, the field did not display data. This issue is resolved.
GainSeeker Utility - Note Manager function
The Send to Editor... button in the Note Manager function of the GainSeeker Utility module is renamed Export... .
The Send to Editor... function for the Note Manager in the GainSeeker Utility module failed to export all of the data for a standard to the text editor program. This issue is resolved.
When a list of available standards for a configuration was limited to a priority list, the full list of standards sometimes displayed in a Note Manager dialog in the GainSeeker Utility module. This issue is resolved.
GainSeeker Utility - Priority List function
Sometimes the Priority List Editor incorrectly prompted a user to add a duplicate standard to a DMS priority list. This issue is resolved.
In the Priority List Editor, the traceability list associated with the current configuration displayed instead of the list for the selected user. This issue is resolved.
The Send to Editor... button in the Priority List Editor function of the GainSeeker Utility module is renamed to Export...
The Copy to user... button in the Priority List Editor function of the GainSeeker Utility module is renamed to Duplicate... .
The Priority List Editor incorrectly indicated that you could create a priority list for desktops. This feature is now enabled.
In some instances, when standards were added to a priority list using the SPC Priority List Editor, the descriptions for the standards displayed extra characters or spaces. This issue is resolved.
In cases in which a user's system had many thousands of standards or more, importing standards using the Import/Export function could sometimes be slow. This issue is resolved.
When a record was deleted using the Import/Export function, the action logged to the Audit Trail as a change instead of a deletion. This issue is resolved.
The Import/Export Status dialog step in the Import/Export function incorrectly displayed an error message when a user prepared to export data using a filter that had a traceability test field greater than six. This issue is resolved.
The Import/Export Status dialog step in the Import/Export function reversed the values displayed in the Low Date Time and High Date Time columns. This issue is resolved.
When a user was denied permission to Enterprise Dashboard, a button for that module still displayed on the GainSeeker LaunchPad, however, access was successfully denied. This issue is resolved.
When role permissions were limited to some GainSeeker applications, an access button for the denied applications sometimes still displayed on the GainSeeker LaunchPad. This issue is resolved.
When permission to use specific modules was denied for a role, access buttons to those modules sometimes still displayed. This issue is resolved.
When a user with a password attempted to open some applications using LaunchPad, the user was asked each time to log into GainSeeker.
The online user guide was updated to accurately reflect how the Run length is used during real-time checks.