This topic describes resolutions or solutions in GainSeeker version 10.1 and corrections to the Online User Guide.
|
Contents [Hide] |
In some cases, with a very small data set, the Range chart would give errors and fail to draw. This occurred when the calculated minimum and maximum values were the same. This issue has been resolved. (Issue: GAIN-4711)
Creating a chart skin and applying it would sometimes show Fonts and Colors as changed on the Settings dialog when they had not changed. This issue has been resolved. (Issue: GAIN-4614)
Added additional language support for the Edit Data dialog and the Dashboard Grid right-click menu. (Issue: GAIN-4739)
When editing data and GainSeeker was set to not display the second user-defined traceability, the next traceability field on the Edit Data screen only allowed one character to be entered. This issue has been resolved. (Issue: GAIN-4751)
Although WebViz will continue to run if it is set up correctly, the settings to configure it are no longer available in the Administration module. (Issue: GAIN-4719)
Changes to the Traceability Restrict to list and Require entry where incorrect when logged to the Audit Trail. The values written were opposite of the actual change. This issue has been resolved. (Issue: GAIN-4716)
The Last Login feature did not show the dates of the last login for GainSeeker users. This issue has been resolved. (Issue: GAIN-4726)
The Importing new users from a file documentation has been updated to better explain how to import users with the Use Windows Display Language option. (Issue: GAIN-4706)
Using the Used By function to identify where a python script was being used did not always return all occurrences. This issue has been resolved. (Issue: GAIN-4673)
The file.delete command now uses the error.stoponerror setting. (Issue: GAIN-4732)
Importing a Python script would lose special characters, such as foreign language characters. This happened when importing the script with an inspection. This issue has been resolved. (Issue: GAIN-4742)
When retrieving data with the external data python commands and using a filter sometimes not all the data points in a subgroup were returned. This would happen when a filter was used with a traceability column from the auxiliary data table but that column wasn't the first column specified in the filter. This issue has been resolved. (Issue: GAIN-4356)
When drawing temporary data points on the side panel of an inspection, the last point entered was sometimes duplicated. This issue has been resolved. (Issue: GAIN-4740)
Copying and pasting DMS Standard tests in an inspection could sometimes cause Planned Inspections to lose their DMS Part Number values. This issue has been resolved. (Issue: GAIN-4749)
Changing the password of a user in the Reset Password Utility did not log that change in the Audit Trail. This issue has been resolved. (Issue: GAIN-4636)
When changing Defects in the SQL Assistant option of GainSeeker Utility, the Process Defect List could get duplicate defects causing problems when running PC Collect. This issue has been resolved. (Issue: GAIN-4746)
When using command line parameters to open and print a report the report would not print if the CLOSE parameter was also used.. This issue has been resolved. (Issue: GAIN-4743)