This topic describes resolutions or solutions in GainSeeker versions 8.4.2, 8.4.1, and 8.4.0 and corrections to the Online User Guide.
|
Contents [Hide] |
Version 8.4.2
Version 8.4.1
Changing a traceability value using the Traceability tab on the Edit Data dialog did not always work correctly with Pervasive.SQL databases. This issue is resolved.
When a user selected defects in a process and saved them in a specific order, the defects did not retain that order. Now they always display in the user-specified order.
When using the GainSeeker system on a case-sensitive database, some features did not function properly, including changing configurations and editing standards. This issue is resolved.
When a user created the first defect for a new configuration, the defect did not correctly display on DMS charts. This issue is resolved.
The number of decimal points set for Gate and Cost for a DMS standard,and DPU value for a DMS Process did not correctly display as any of those items was being edited. The correct number of decimal points now displays.
Version 8.4.0
When the configuration was changed during a data entry session that used a template, and the template was then changed, the traceability list from a previous configuration sometimes displayed. This issue is resolved.
When the first Event, Action, or Cause was added to a new table, it did not properly store that item. This issue is resolved.
When the See all users, roles and configuration, Roles tab setting was set to Deny Access, the user could still change configurations when running GainSeeker modules. This issue is resolved.
The Corrective Action Lists dialogs that open from the Actions taken setting for a configuration, displayed the lists for the user logged into the System Administration module, not the list specific to a configuration. This issue is resolved.
The installation program did not check the cms.ini DSN value to determine if a non-default Data source name was used. This issue is resolved.
When an HTML Table or Body attribute was set in the System Administration module, the set value did not properly apply. This issue is resolved.
When the Hide statistics or legends after charts option was selected in the System Administration module, those items still sometimes displayed with charts.
When data grouping for OEE charts was being set for a configuration, only the traceability list for the administrator logged in who was making the change displayed. Now the traceability list for the correct configuration displays.
When creating new Event, Cause, or ActionTaken list items, an audit trail entry was created. This issue is resolved.
Version 8.4.0
Version 8.4.0
When all available part numbers were selected for a retrieval in the Dynamic Reports module, the information associated with each part number did not always properly retrieve. This issue is resolved. The Part Numbers tab on the Report Retrieval Settings dialogs for SPC and DMS retrievals now additionally features a Select All checkbox option
When the value for the Maximum count for retrieval setting for a Dynamic Report was saved at 0, the value display changed to Not Set. This issue is resolved.
Charts
Version 8.4.2
When the contents of a filter were set using the Filter Builder, and the line entered below the initial Operation was deleted and reentered, that Operation was not retained. This issue is resolved.
When displaying a Pareto chart that was sorted by a traceability field, two values that were identical except for differences in uppercase and lowercase characters were displayed on two separate bars. The Pareto chart analysis has been corrected to ignore uppercase and lowercase characters when sorting data into bars.
Version 8.4.1
When a user did not have rights to the right-click menu group data option on a chart, the option still displayed. This issue is resolved.
When OEE bar charts were drawn with the Display values for OEE Charts setting checkbox selected, the data values for the bars did not display on the chart. This issue is resolved.
Some x-axis label settings could prevent a Time Axis chart from displaying. This issue is resolved.
When a chart skin specified a Plot background color setting value (other than white), the chart skin did not use that value. Chart skins now correctly use the setting value. To remedy this for a chart skin created before GainSeeker version 8.4.1, apply the chart skin to a chart, update the Plot background color setting value, and then resave the chart skin.
When data was grouped on some chart types, GainSeeker made a distinction between traceability values that had been stored using uppercase and lowercase characters. This resulted in data that was sometimes improperly grouped. This issue is resolved.
When numerous bars displayed on an OEE chart, the x-axis bar labels were sometimes difficult to read. Now, when more than 12 bars display on a chart, GainSeeker rotates the labels to a more vertical position for better readability. When more than 55 bars are displayed on an OEE chart, not all bars display labels for this reason.
Version 8.4.0
When all part numbers or all processes are selected for a DMS chart, the retrieval is not limited to those part numbers or processes displayed in the list. Retrieved data that is not associated with a standard now displays on the chart. Charts with this type of retrieval may display differently than in versions prior to GainSeeker 8.4. For more information, see Storing charts and dashboards as desktops
When a Scatter Plot chart was drawn from the Variation Wizard, GainSeeker incorrectly filtered the data using the selected Discrete traceability instead of the selected Continuous traceability. This issue is resolved.
When no coding method was set for a short run process specification, GainSeeker Charts would retrieve the data as Uncoded. SPC Charts and Reports would retrieve the data as Target/Nominal. Now both modules retrieve the data as Target/Nominal when no coding method is set.
When the Apply restrict selections to retrieval settings checkbox was selected on the Restrict List dialog, date period and filter settings were not always applied to the retrieval. This issue is resolved.
MINITAB versions 15 or 17 users: GainSeeker uses MINITAB version 16 as the default version to which it communicates. You can change this setting to have GainSeeker automatically recognize MINITAB versions 15 or 17 as the default version to which it communicates as it did in previous versions of GainSeeker. See Important note for MINITAB 15 and MINITAB 17 users
X-Axis label settings no longer apply to SPC Multiple charts (for example, Multiple Charts, Box and Whisker, Statistics Table, Multiple Data Table, and Combined Control charts).
For DMS charts, GainSeeker now uses the NCUCost column or DefectCost column, depending on the Use cost information from setting.
The second column of a Statistics List sometimes did not always correctly line up. This issue is resolved.
The value set for the Back Color= setting for Data tables, Statistics tables, and Statistics lists did not always correctly display on these window types. This issue is resolved.
When the Apply the standardized coding method option was selected for a configuration on the Incomplete subgroups and Varying Subgroup Sizes dialog, the values did not always correctly display on charts. This issue is resolved.
When the x-axis on a chart was labeled by count and the chart contained five or less data points, the first two points would incorrectly label 1, 1 instead of 1, 2. This issue is resolved.
The Sort data for Pareto chart bars and Bar color Pareto chart options on the Settings dialog are now disabled after you drill down on a Pareto Chart.
When data from a multiple data table was sent to Minitab, that program placed data points in incorrect columns when the subgroup size varied, and smaller subgroup sizes preceded larger-sized subgroups. This issue is resolved.
When a filter based on NCU or Sample Size was set for a DMS chart, no data was returned. This issue is resolved.
Some OEE Combined chart elements, such as a chart title, may sometimes visually conflict with the chart's color legend. To remedy this, you can now click on the legend and drag it to another location on the chart.
Single bar DMS charts sometimes displayed incorrect label text. This issue is resolved.
When a chart image was sent to Microsoft Word, the chart did not properly size on the Word page. 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 was resolved in version 8.3.1.
When brushed data for a chart was permanently bypassed by a user, the action did not log to the Audit Trail. This issue is resolved.
When data was edited using the Edit Data dialog, an extra decimal digit displayed for the standard on the dialog's Data tab. This issue is resolved.
When external data was attempted to be stored for a standard that did not exist in an Oracle database, GainSeeker did not automatically present the option for the user to add the standard. This issue is resolved.
When a user opted to change the chart type on a multiple chart from a Control chart to a Histogram and the chart had a background image, GainSeeker ceased to operate properly. This issue is resolved.
When a filter was changed, under some circumstances the traceability list for a previous user incorrectly displayed instead of the list for the current configuration. This issue is resolved.
When counts with fractional values were stored for defects, incorrect statistics and drill-down information could be displayed. This issue is resolved.
When editing DMS data from a data table in GainSeeker Charts, saving the data did not update always the Number Good and Percent Defects columns correctly. This issue is resolved. See also a related known issue with cost columns.
When drawing Pareto charts from the External Data option and then doing a drill down into a Pareto bar, GainSeeker sometimes halted unexpectedly. This would happen when the default sort by item was not imported in the external data. This issue is resolved.
DPU charts
Version 8.4.0
When the Group By setting for a DPU chart was changed from Week to Month, the X-axis labels positioned too high. This issue is resolved.
The Month column in the data table for a DPU Detail chart sorted incorrectly. Now it correctly sorts by date.
In some cases when data was grouped on a DPU chart, the improvement curve did not correctly display. This issue is resolved.
Variation Wizard
Version 8.4.0
Version 8.4.2
When a Dashboard Grid control refreshed in earlier GainSeeker 8.4 versions, the sort order of the first column reversed for numeric retrievals. This issue is resolved.
When a user attempted to download an entry from the GainSeeker Python Design Library using an Oracle database, the entry did not always save correctly.
When a data table was embedded in a dashboard, the table did not display the correct number of decimals as set for the standard. This issue is resolved.
Version 8.4.1
When a list of available DMS statistics was switched from short- to full-list view for a Marquee, Button, or Dynamic Text dashboard control, the control sometimes ceased operation. This issue is resolved.
When a user refreshed a Chart dashboard control with an applied chart skin, the skin did not display unless the user refreshed the chart using the F5 keyboard shortcut. This issue is resolved.
When a user changed configurations inside the GainSeeker Charts module, the list of available chart skins for a Chart dashboard control did not update to the Chart Skin list for the current configuration. This issue is resolved.
Version 8.4.0
When a retrieval for a Scatter chart on a dashboard had no data, GainSeeker ceased to properly operate. This issue is resolved.
When using the right-click menu to draw a chart from a dashboard Dynamic Text control, not all the retrieval parameters were applied to the new chart. This issue is resolved.
Dashboard Grid control
Version 8.4.1
The Dashboard Grid control sometimes did not correctly display custom statistics. This issue is resolved.
Version 8.4.0
The Open/Edit dialog sometimes displayed incorrect filtering options for the Dashboard Grid control. This issue was resolved in version 8.3.1.
When defects for a specific process were selected for a Dashboard Grid control, the GainSeeker Charts module sometimes closed unexpectedly. This issue is resolved.
When a column for today's data and a column for yesterday's data were added to a Dashboard Grid control, those columns displayed data for the same date period. This issue is resolved.
When viewing a Dashboard Grid and selecting the View failure data... right-click menu option, all data for that cell displayed instead of just the failure data. This issue is resolved.
Version 8.4.2
Version 8.4.0
A desktop that is created or edited in GainSeeker Charts version 8.4 will not run correctly in earlier versions of GainSeeker Suite. GainSeeker displays an error message if this is attempted.
When a desktop was opened using a command line, and it contained a dashboard with a single control that had no retrieval, the desktop failed to properly open. This issue is resolved.
When a dashboard was stored in a desktop with the Fixed dates option selected, the desktop did not display data when it was reopened. This issue is resolved.
Version 8.4.2
Chart Overrides and Chart Skins settings can no longer be applied to inspection charts using the Inspection Editor. Inspection charts display the values set for Chart Overrides and Chart Skins settings in the System Administration module. However, these settings: Filter, Retrieval/Configuration, and Standard overrides can still be applied using the Inspection Editor.
Version 8.4.1
When defects were present in a Defect List test, the inspector was not required to write a note for the test even when that action had been set by the inspection designer. This issue is resolved.
In the Inspection Editor, when a sub-inspection was attempted to be deleted using the right-click menu "delete" option, GainSeeker instead deleted the currently selected sub-inspection. This issue is resolved.
Version 8.4.0
When the ellipsis button was used to display options for the Traceability property in the Traceability sub-inspection test, the current value was not highlighted. This issue is resolved.
When selecting a part number for an inspection, the full part number list displayed even when the priority list was set to display. This issue is resolved.
Version 8.4.1
When an SPC standard with a subgroup size greater than 1 was picked at runtime for a Numeric Input test, the subgroup size always displayed as 1. This issue is resolved.
Version 8.4.0
When a defect name containing a quotation mark (“) was part of a mobile inspection, GS Collect ceased operating for that inspection. This issue is resolved.
Version 8.4.2
When data was deleted using the Import/Export function in the GainSeeker Utility module, GainSeeker did not confirm that the user had rights to perform this action. This issue is resolved.
When data without a corresponding standard was imported using the Import/Export function, the user was unable to successfully create the standard when following the dialog prompts. This issue is resolved.
When SPC data for a standard was deleted using the Import/Export function, only data stored in the VDATA table successfully deleted. Data stored in the Note, Monitor, and Auxiliary tables did not delete. This issue is resolved.
Version 8.4.1
When specific SPC or DMS standards were imported as TAB or XML files using the Standard Utility, data for all of the standards was imported. This issue is resolved.
When specific columns were selected when notes were exported using the Import/Export Utility, those columns were not retained in subsequent exports. This issue is resolved.
When a user replaces existing standards using the Standard Utility in the GainSeeker Utility module, GainSeeker now records that action in the Audit Trail.
Version 8.4.0
When a user attempted to delete monitor records using the Import/Export Utility, the records remained. This issue is resolved.
When the Select all option was selected for DMS notes on the Note Manager Wizard in Note Manager, GainSeeker did not display all of the associated data. This issue is resolved.
The Standard Utility function in the GainSeeker Utility module is updated to check for the correct user rights.
An informational dialog that GainSeeker displays when the Duplicate feature of the Standard Utility is used, included random characters within the text. This issue is resolved.
The SQL Utility in the GainSeeker Utility module now recognizes the EXEC keyword in addition to EXECUTE. Typical usage is EXEC StoredProcedure_Name.
When data was attempted to be deleted using the Import/Export Utility, the data was not deleted. Also, when DMS data was deleted, GainSeeker would sometimes display an error message indicating that the Note column was not present in the database. These issues are resolved.
Version 8.4.0
Version 8.4.2
When a Microsoft Office file associated with an inspection was edited and saved, PC Collect sometimes failed to operate properly when the inspection was reopened. This issue is resolved.
A PC Collect inspection would not accept asterisks (sentinels) as part of a value in a PC Collect inspection. This issue is resolved.
When a valued entered for a Numeric Input test triggered a real-time failure, the message describing the failure did not display to the user. This issue is resolved.
PC Collect sometimes ceased to properly function when attempting to calculate a real-time failure for a Numeric Input test. This issue is resolved.
When a user attempted to store SPC data with a Numeric Input test, monitor records were not stored. This issue is resolved.
When a user attempted to download an entry from the GainSeeker Python Design Library using an Oracle database, the entry did not always save correctly. This issue is resolved.
Version 8.4.1
When a sub-inspection containing a DMS Standard test with a preset standard followed a sub-inspection containing the same, the latter sub-inspection incorrectly displayed the standard for the first sub-inspection. This issue is resolved.
A minus sign could not be entered from a numeric keypad as part of the value for a Numeric Input test as it was designed to do. This issue is resolved.
Pass/Fail test button labels that contained numerous characters did not display well in a running inspection. This issue is resolved.
The part number text field for a DMS Standard sub-inspection test did not accommodate more than 13 characters. Now the field scales the text to accommodate part numbers with more characters.
Version 8.4.2
A DMS part number selected for an inspection failed to properly set the inspect.dmspartnumber Python command. This issue is resolved.
When the datadms.autocreatedefects or the datadms.createdefect() Python commands were used, duplicate defects were added to the master defect list and the script failed to properly function. This issue is resolved.
A user now receives an error message if no part number is set when a DMS record is being stored using the datadms.store command.
When a user attempted to store SPC data with the dataspc command, monitor records were not stored. This issue is resolved.
Version 8.4.0
Version 8.4.2
The GainSeeker Charts and Dynamic Reports modules can now be used in place of these legacy modules:
DMS Charts and Reports
SPC Charts and Reports
Enterprise Dashboard
The new GainSeeker Utility module can now be used in place of these legacy modules:
Import/Export Manager
Priority List Editor
Audit Trail
GainSeeker Lists
Transfer Utility
SQL Utility
SPC Standard Utility
Note Manager