WinSPC version 9.0.15 has been released and is now available for download.
Customers with an active ESC (Extended Service Coverage) account are eligible to receive the new version.
FEATURES IN RELEASE 9.0.15
Feature Request 2803: An appendix providing the WinSPC license and incorporated open source software licensing is now included in WinSPC Help.
FIXES IN RELEASE 9.0.15
4464: When launching WinSPC on a Remote Desktop client via Remote Desktop Services, the rare situation of the Remote Desktop server name being incorrectly used as the WinSPC station name no longer occurs.
FEATURES IN EARLIER VERSION 9 RELEASES
Feature Request 2713: WinSPC’s ability to communicate with external serial devices has been enhanced. In many cases, WinSPC can now detect when a connection to a serial device gets severed and, within a few seconds, automatically restore that connection. As a result, the need to unload and then reload a collection plan that suffers a severed connection is considerably reduced, rendering disconnections less disruptive, particularly when the network between WinSPC and the serial device is unstable. This detect-and-reconnect capability requires no customer setup; it is ready to do its work the moment WinSPC 9.0.14 launches.
Feature Request 2721: Six new statistics are now available for stat panels in dashboards: Percent Above URL, Percent Above USL, Percent Below LRL, Percent Below LSL, Percent Outside Reasonable Limits, Percent Outside Spec Limits. These new statistics enable dashboard designers to display limit violations as percentages, complementing the existing ability to display them as explicit numbers. Configuring a dashboard stat panel to show these new statistics is the same as it is for any other statistic: simply select the Stat Panel component and then select the statistic from that component’s Statistic property’s list. For more information on dashboards, see the Working with Dashboards write-ups in WinSPC Help.
Feature Request 2464: New Ability to Date-Time Stamp Readings Using WinSPC’s API: It is now possible for an API application to set a default date and time and have that date and time automatically assigned to future readings. These future readings include: those collected through the API application, those collected directly into the WinSPC client associated with the API application (such as readings entered directly using a keyboard or via a device), and those that are calculated by that WinSPC client.
One benefit of this feature is that it enables readings to end up with dates and times in WinSPC that match dates and times in an external source, improving date-range analysis and reporting. Another benefit is that it permits a calculated variable to be assigned the date and time of one of the readings employed in its calculation, as opposed to the date and time the calculation was performed, which could be quite a span of time later. This makes it easier to be confident that date-range based searches return the complete set of relevant collected and calculated readings.
The main item that makes this feature possible is a new API property in WinSPC’s Data Collection interface: DefaultReadingDate. Simply by writing a date and time to this property, an API application sets readings to be stamped with that date and time.
Following is an example of the syntax to write a date and time to this property:
DataCollectionAuto.DefaultReadingDate = “MM/DD/YYYY HH:MM:SS”
(Note: The actual format for the date and time, given here as MM/DD/YYYY HH:MM:SS, is dictated by the Windows regional settings on the computer running the API application.)
Clearing a date and time from this property is accomplished by writing an empty string to it:
DataCollectionAuto.DefaultReadingDate = “”
Reading this property’s date and time can be done with this syntax:
Dim defaultReadingDate As String = DataCollectionAuto.DefaultReadingDate
When using this new DefaultReadingDate property to date-time stamp readings collected through the API application, precedence is given to the ReadingDate property, a property that has been in the Data Collection interface for some time. This means that ReadingDate must be null when DefaultReadingDate is to stamp readings collected through the API application. (Unlike DefaultReadingDate, the ReadingDate property has no effect on readings collected outside of the API application.)
Similarly, when using DefaultReadingDate to stamp readings collected via an ODBC Data Source device, precedence is given to that device’s Date/Time field setting. This setting—which is found on the Device Setup window’s TBD tab—is for a field in the ODBC source that contains dates and times. If it is configured, readings collected via the device will be stamped with that field’s dates and times and DefaultReadingDate will be ignored.
If the ODBC Data Source device condition just mentioned is not applicable and neither the Reading Date property nor the new DefaultReadingDate property are set, readings—no matter how they are collected—will be stamped with the current date and time from the computer on which the API application is running.
New WinSPC Database Certifications: WinSPC is now certified to work with all current versions of Microsoft SQL Server up to and including SQL Server 2017. The procedure to configure WinSPC to use these versions is fully documented in the WinSPC Installation and Configuration Guide accompanying this release.
WinSPC E-Mail Encryption and Authentication: WinSPC’s e-mail capabilities have been enhanced to support both encryption and authentication. This means that corporate e-mail servers or other third-party e-mail servers configured to reject e-mails that are unencrypted or sent by users who can’t be authenticated can now accept WinSPC e-mails. As a result, stakeholders with such a server in their infrastructure are able to get up- to-the minute test violations, reports, statuses, and other vital information that WinSPC e-mails are depended on to deliver—and do so in a controlled and secure manner. These e-mail enhancements are designed for e- mail servers that employ the Simple Mail Transfer Protocol (SMTP). (Feature Request Numbers 726, 742, and 999.)
To set up WinSPC for e-mail encryption and authentication:
a. Log into WinSPC as the Admin user and, from the Administrator window’s Tools menu, click System Settings.
b. In the System Settings window that appears, select the E-mail tab.
c. On this tab, select the SMTP option and:
- At SMTP Server Name or IP Address, enter the name or IP address of the SMTP e-mail server that you want WinSPC to interact with. (Your IT department or external e-mail provider can supply this information along with the other information required by the e-mail server on this E-mail tab.)
- At Port, enter the port number used by that e-mail server.
- At Connection Type, select the degree of encryption you want WinSPC to employ when communicating with the e-mail server. The options are:
- Allow end-to-end transmission as clear text: This option results in WinSPC sending unencrypted communication to and accepting unencrypted communication from the e-mail server. It is for an open-relay type of server.
- Allow initial connection as clear text: This option results in WinSPC sending unencrypted communication to and accepting unencrypted communication from the e-mail server only to establish an initial connection and then, once a connection is established, sending and accepting only encrypted communication. (With this option, at the appropriate time, WinSPC signals the beginning of encryption by transmitting the STARTTLS command.)
- Require end-to-end encryption: This option results in WinSPC sending only encrypted communication to and accepting only encrypted communication from the e-mail server, including the communication related to the initial connection and all communication subsequent to that initial connection.
- If the e-mail server authenticates e-mail senders and you want it to accept WinSPC e-mails:
- At User Name, enter the full e-mail address of an authenticated user on that server.
- At Password, enter that user’s password.
- At Default Sender E-mail Address, enter an e-mail address to be displayed by default in e-mails as the sender address. (See step d below to override this default address with individual user addresses.)
- Click the Test e-mail button.
- In the prompt that appears, enter an e-mail address for the test e-mail to be sent to.
- If the message that appears indicates the test e-mail was successfully delivered, no further steps other than clicking OK need to be taken. If the message that appears indicates the test e-mail was not successfully delivered, review the above steps to locate the incorrect configuration and remedy that configuration.
d. If desired, setup user-specific overrides of the default user name, password, and sender e-mail address just configured. To do this:
- In the Administrator window, right-click the user for whom you want to set up an override and select Properties.
- In the User Setup window that appears, on the General tab:
- At E-mail Address, enter the e-mail address that is recognized by the SMTP e-mail server for theuser.
- At E-mail User Name, enter the user name associated with that e-mail address.
- At E-mail Password, enter the password associated with that user name.
- Click the Test e-mail button.
- In the prompt that appears, enter an e-mail address for the test e-mail to be sent to.
- If the message that appears indicates the test e-mail was successfully delivered, no further steps other than clicking OK need to be taken. If the message that appears indicates the test e-mail was not successfully delivered, review the e-mail address, user name, and password you supplied to locate the incorrect configuration and remedy that configuration.
- Chart-Only Mode for Collection Plans: Administrators can now setup a collection plan so that no data entry fields are visible. With this setup, when the collection plan is loaded in Data Collection, only the chart(s) will be visible. The setup is accomplished using the new (none) option for the User Interface Type in the Collection Plan Setup window (specifically, the General subtab of the Step Options tab in this window). The value of this new mode is it improves the display of the collection plan when data entry fields are not needed, such as when data is being collected automatically from a device. (Feature Request Number: 505.)
- Improved Active Directory Searching: The ability to search Active Directory for users or user groups from within WinSPC has been enhanced. Now, using the Find button on either the User Group Setup window’s Defaults tab or the System Settings window’s Active Directory tab, users can specify more precise conditions and, in so doing, get more targeted results. (Feature Request Number: 2022.)
- Ability to Limit the Number of Threads to be Used by the WinSPC Application Server: In prior releases, the WinSPC Application Server used two threads per application server machine core for caching operations. Particularly for machines with a large number of cores, server admins may want to reduce the number of threads used. They can now do this using a new MaxCacheThreads setting in the WinSPCsvr.ini file. As documented in this file, the default value for this setting is 0. When set to this value, two threads per core will be used by the application server as it historically has. When set to a specific number, the total threads used for caching the main database will be limited to that number. (Feature Request Number: 2112.)
- WinSPC OLE/API Changes: Existing applications that utilize the WinSPC API may be impacted by these three changes:
- Automatic Quiet Mode for an OLE Launch: When WinSPC is launched through OLE (using any of the WinSPC OLE objects), the splash screen and login screen will now always be hidden. Applications that have previously enabled Quiet Mode for WinSPC for an OLE launch (by adding the “/q” command line option to the WinSPC OLE registry entries) no longer need to do so. If an application needs to display a login screen for the user to have a GUI session in addition to the OLE session, the application can launch WinSPC directly through a shell command (by running the WinSPC.exe executable). (Feature Request Number: 780.)
- LoginFormVisible Property Removed: This property has been removed from the DataCollection OLE object due to the WinSPC OLE launch changes noted above, as the login screen will now always be hidden.
- LoginAsWindowsUser Property Added: This new property (added to all four WinSPC OLE objects) allows an application to login to WinSPC as the current Windows user. This property will only function if WinSPC Active Directory Integration is enabled, the current Windows user is a WinSPC managed user, and the current station is configured to hide the login screen (configured in the System Settings and Station Settings). This property is intended to replace usage of the Username and Password properties to login to the OLE object when WinSPC is configured to automatically login the current Windows user through Active Directory (as in the case when the application does not have access to the current Window user’s password and could not use the normal Username and Password properties).
- WinSPC Application Server Specifics Displayed for Easy Reference: To streamline the installation and upgrade of a WinSPC application server instance, the instance’s version number and instance name are now displayed within WinSPC. The number and name can be found on the Server tab of the System Settings window. (Feature Request Number: 1821.)
- Enhanced Installation: The installation process for WinSPC clients as well as the WinSPC application server has been substantially enhanced. It now provides even better security and simplifies the readying of multiple instances on the same station. As part of the latter enhancement, new capability for both repairing and uninstalling instances is introduced. (Feature Request Number: 861, 1822.)
- Enhanced WinSPC Security Utility: The WinSPC Security Utility has been modified to permit the selection of domains. This enables users of the utility to be logged into one domain and grant WinSPC permissions to users and user groups who are members of other domains. (Feature Request Number: 664.)
- Single-Click Access to Important Directories: The WinSPC remote directory, also known as the shared WinSPC folder, is now accessible by clicking a link in WinSPC’s About window (which itself is accessible from the WinSPC Help menu). Similar single-click access has also been added for the WinSPC Application Directory and the WinSPC Data Directory. (Feature Request Number: 734.)
- More Favorable Permissions for the Shared WinSPC Folder: The requirement to grant the Authenticated Users group permission to the shared WinSPC folder has been dropped. When installing the WinSPC application server, all that is now required is that the application server machine itself be granted Read level Security permission to the shared WinSPC folder (assuming the shared folder is on a machine other than the application server machine). When installing WinSPC on additional WinSPC clients, permissions beyond those applied by the WinSPC Security Utility are no longer required. (Feature Request Number: 1847.)
- A Contemporary New Look: An update of WinSPC’s entire look-and-feel, including every button on every tool bar.
- New Archiving Capability: A reengineering of your ability to archive content and work with archives after-the- fact. The new archiving capability allows for archives to be stored in an Oracle or SQL Server database, scheduled for automatic execution, and accessed using WinSPC’s standard analysis and reporting tools. (Feature Request Number: 803.)
- Enhanced Security Configuration Utility: A redesign of the WinSPC Security Configuration utility to make applying WinSPC-specific permissions both easier and more flexible.
- Active Directory Integration: Support for Active Directory, Microsoft’s technology for managing users. This feature facilitates the automatic creation and management of WinSPC users with Active Directory and allows for automated login to WinSPC based on the current Windows user. (Feature Request Number: 248.)
- Report Designer Enhancements: New ability to report on attribute and collection plan data and a comprehensive self-study guide for users to learn the Report Designer in depth. (Feature Request Numbers: 546, 670, 823, 856, 927, 936, 1034, 1037, 1050, 1069, 1100, 1108, 1174, 1426, 1591.)
- The Attribute Analyzer: A new tool for analyzing an attribute, similar to the Variable Analyzer introduced in the Version 8 series for analyzing a variable. (Feature Request Numbers: 116, 168, 323, 492, 823, 1050, 1214, 1302, 1591.)
- New Options for Exporting Data: New ability to export attribute data and enhanced ability to export variable data. (Feature Request Numbers: 168, 492, 1050.)
- Improved Procedures for Forcing Logouts: Reorganized tools and procedures for forcing the logout of users when required. (Feature Request Number: 772, 1502.)
- Streamlined License Management: Enhanced tools and options for license management tasks. (Feature Request Number: 772, 1502.)
- Reengineered Database Migration Procedure: A new Migration Wizard that simplifies and enhances the migration of a WinSPC database.
- New User Permissions for the Administrator Window: A new, more intuitive structure for managing Administrator window user permissions.
- Expanded Chart Schemes: A significant reworking of what was previously referred to as color schemes to give users granular control over a greater number of chart types and chart elements. (Feature Request Numbers: 987, 1112, 1269, 1405, 1427, 1551, 1699.)
- New Easier-to-Use Administrator Window: Two new Administrator window features: the ability to resize icons and enhanced cut/copy/paste functionality. (Feature Request Numbers: 87, 1268.)
- Compatibility with Windows 8.1 and Windows Server 2012 R2: Internal lab certification of Windows 8.1 and Windows Server 2012 R2 for use with WinSPC. (Feature Request Number: 1374.)
- More Powerful Data Sets: Data sets extended to attributes and collection plans. (Feature Request Number: 856.)
- New Password Management: Improved procedure for managing system-wide password policies.
- Expanded Support for Excel Devices: New support for XLXS and CSV file formats when capturing data user anExcel device. (Feature Request Number: 785.)
- Dashboards:Dashboards are new presentation modes to display and share your data. Customizable dashboards can be used to harness the power of data sets to display a big screen view of your WinSPC data. Dashboard visualizations include control charts, box plots, Paretos, tables, statistics, graphical display gauges, and more. (Feature Request Numbers: 74, 1153.)
- Chart Drill-Down: A new drill-down capability when working with charts, permitting you to filter your view of a chart’s data with a single mouseclick. (Feature Request Number: 1214.)
- Translation Utility: A new visual localization and language string editing tool enabling you to customize WinSPC for speakers of languages other than English.
- Additional Visual Groups: An increase in the maximum number of visual groups that can be configured for a collection plan from 10 to 20. (Feature Request Number: 47.)
- Variable Analyzer Refresh Timer: Two new Variable Analyzer tool bar buttons—Refresh Now and Periodic Refresh—that give users the ability to refresh the data in the Variable Analyzer with updates that occurred since the Variable Analyzer was launched. (Feature Request Numbers: 882.)
- New Variable Analyzer Chart Types: A variety of new chart types, including Pareto charts and pie charts, in the Variable Analyzer. (Feature Request Numbers: 1302.)
- VariableSetupEnhancement:An automatic default of the Subrange Size to 2 whenever the Subgroup Size in basic Variable Setup is set to 1. (Feature Request Number: 1538.)
- Application Server Enhancement: An alternative method of connecting a WinSPC application server to a WinSPC database that does not involve a UDP broadcast. (Feature Request Number: 1634.)
FIXES IN EARLIER VERSION 9 RELEASES
2987: The uncommon sequence of selections in the Tags window that generated a “Value must be a member of valuelist” error no longer generates this error. (The Tags window may be accessed from the Data Collection window’s Tags toolbar button.)
3639: Prompting a serial device after the connection to it was severed and then restored, in many cases, no longer generates an access violation, behavior that has been observed in environments utilizing Microsoft Terminal Services. (For additional information on this fix, see Feature Request 2713 on the preceding page. That feature and this defect fix are nearly identical and the same coding change addresses both.)
4336: When the Tags window automatically appears after launching a collection plan, it is no longer necessary to select values for optional pull-down tags in order for the clicking of that window’s OK button to complete the loading of the collection plan. Additionally, when the only tag in the Tags window is an optional pull-down tag, clicking the Cancel button now returns the display to the window from which the collection plan was launched, as expected. (An optional tag is a tag for which the Force Entry option is disabled in the Tag Setup window.)
4417: Notes, assignable causes, or corrective actions submitted for an attribute in Data Collection are now immediately visible in the Attribute Analyzer. (Accelerated Defect: 4138.)
4418: Clicking the Cancel button in the Tags window, when that window is displayed as a result of launching a collection plan, now always returns the display to the window from which the collection plan was launched. (Accelerated Defect: 4126.)
3811: Values calculated by the Cubic Interpolate function in WinSPC’s Equation Builder are now in line with the accepted mathematical definition of cubic interpolation.
4361, 4367, 4368, 4369: Attempts by a WinSPC client to communicate with the WinSPC application server no longer result in the access violations or other errors occasionally seen since the release of WinSPC 9.0.11. That release, to provide some background, introduced new client authorization code, code that has since been determined to be the cause of those occasional access violations and errors. Consequently, WinSPC 9.0.12 is being released with that code removed and the client authorization code in use prior to WinSPC 9.0.11 reinstated, and the request that the new code was intended to satisfy—recorded as defect number 4337—has been rescheduled for inclusion in a future release. All other defect fixes included in release 9.0.11 along with that release’s new API feature remain unchanged and functional in WinSPC 9.0.12.
4373: Dashboards that employ the Variable Grid component, when used to view a data set, now correctly limit the variables displayed to those that match the data set’s list filter criteria.
4374: The error handling code for the WinSPC data collection process no longer enters a “No transaction is active” error in WinSPC’s event log when circumstances do not warrant it. (Accelerated Defect: 4360.)
4385: The rarely used dashboard setups that resulted in an access violation—either while configuring a dashboard or when subsequently loading a dashboard into the Dashboard Setup window for further configuration—no longer cause this access violation.
2444: The Location column on the Step Options and the Tag Options tabs, both in the Collection Plan Setup window, now display locations as expected, including those defined for an ODBC device.
3386: List filter descriptions in the top portion of the Data Set Builder now update to reflect the filtering criteria supplied by a user in the Parameter Editor, which is the editor that is sometimes displayed as part of the loading of a data set to give users an opportunity to customize the data set’s list filtering criteria. As a result, the list filter descriptions now represent the current state of the filters, not the configured state.
3822: Part grids in a dashboard now consistently display their labels correctly.
3979: In a dashboard, when a part grid contains a variable grid, the variable grid is now populated with thecorrect number of variables; that is, the number of variables expected based on the filtering criteria in effect.
4015: The memory issue that occasionally occurred after printing a report and that prevented somesubsequent action from completing, resulting in a bug notification related to that subsequent action, has been remedied. The remedy, in addition to resolving this defect (#4015), resolves 24 other defects now known to be symptoms of the same root cause. These other defects are included below in their proper numerical order and reference this description.
4059: See defect 4015 above.
4060: See defect 4015 above.
4064: See defect 4015 above.
4086: See defect 4015 above.
4095: See defect 4015 above.
4100: See defect 4015 above.
4101: See defect 4015 above.
4103: See defect 4015 above.
4128: See defect 4015 above.
4133: See defect 4015 above.
4142: See defect 4015 above.
4151: See defect 4015 above.
4152: See defect 4015 above.
4154: The circumstances that generated a bug report when closing WinSPC, specifically one indicating that theform TProgressForm couldn’t be released, no longer have this effect, allowing WinSPC to close cleanly.
4155: Attempting to close WinSPC by right-clicking the WinSPC icon in the task bar and clicking Close Windownow closes WinSPC without errors unless conditions exist that preclude WinSPC a clean closing, such as an undismissed message box, in which case the closing operation is abandoned and WinSPC is left in a running state.
4156: The circumstances that generated a bug report when closing WinSPC, specifically one referencing a problem releasing TTimerReminderDialog, no longer have this effect.
4170: See defect 4015 above.
4179: See defect 4015 above.
4180: See defect 4015 above.
4208: See defect 4015 above.
4215: See defect 4015 above.
4226: See defect 4015 above.
4229: See defect 4015 above.
4231: See defect 4015 above.
4233: See defect 4015 above.
4238: When running WinSPC on an RDP client, double-clicking the X in the Data Collection window’s top rightcorner to close the active collection plan no longer leaves the Unloading notification visible after thecollection plan has completed the unloading process.
4244: Same as 4155. (The difference between these two defects concerns the condition that precludes a cleanclosing of WinSPC.)
4255: See defect 4015 above.
4261: Archives configured in the month of December to run on a monthly basis now run as expected.
4262: See defect 4015 above.
4273: When running WinSPC via a Remote Desktop Protocol connection, the Data Collection window nolonger occasionally loads as a blank window.
4276: The scheduling of archives to run monthly can now be done consistently.
4308: Same as 4155. (The difference between these two defects concerns the condition that precludes a cleanclosing of WinSPC.)
4327: In a dashboard, when a variable grid contains an organizational component, such as a splitter, thevariables displayed in that grid are now sorted correctly.
4333: The rare collection plan configuration that prevented the Unloading progress bar from completingwhen attempting to exit a collection plan from the Data Collection window no longer has this effect.
4334: When running WinSPC via a Remote Desktop Protocol connection, the RDP client name is now correctlyand consistently used as the station name, as opposed to the RDP host name sometimes being used.(Accelerated Defect: 3848.)
4335: Adding an assignable cause to a data point in the Data Collection window no longer occasionally causesa pull-down list of tag values for a related tag to be blank. (Accelerated Defect: 3330.)
4337: The WinSPC Application Server now recognizes and rejects foreign protocol requests, meaning protocolrequests from a source other than a WinSPC client. (NOTE: Due to an unforeseen conflict introduced by this defect fix, it was rolled back in WinSPC 9.0.12 and rescheduled for resolution in a future release.)
4040: The Statistic Value list filter, which is configured on the List Filter window’s Filtering Options tab in the Data Set Builder, now filters the complete body of data it is supposed to filter.
4117: Computers running the specific versions of Windows 10 and the specific drivers that, together, generated access violations when editing a report template in WinSPC’s Report Designer no longer generate those violations.
4123: Tag values collected via a device into multiple visual groups within a collection plan are now always associated with the correct subgroups.
4146: Report templates that employ a CalcByDateRange data view now return multiple records when appropriate.
4167: The rare conditions that caused some ODBC Data Source devices to collect the same data more than once or fail to collect data that should be collected no longer have this effect.
4168: The memory leak in the WinSPC application server that resulted from enabling Active Directory Integration is now resolved. (Accelerated Defect: 3848.)
4169: The Plant Monitor layout load speed is now restored to the level it was at before the release of WinSPC 9.0.9.
4175: When creating an item using the WinSPC API, the unique circumstance that caused the item to be incorrectly named no longer has this effect. (Accelerated Defect: 3449.)
4176: Right-clicking a dashboard in the Select Data Set window and clicking View As now properly displays the dashboard’s data. (The Select Data Set window is accessible from the Data Sets button in the Navigator and Data Collection windows) (Accelerated Defect: 3902.)
4177: Variables can now be copied-and-pasted into a part consistently, regardless of the copy-and-paste method used. (Accelerated Defect: 3676.)
4183: WinSPC now properly handles user authentication for SMTP servers that utilize the following authentication protocols: [RFC 2831] DIGEST-MD5, [RFC 2195] CRAM-MD5, and [RFC 1760] SKEY.
4124: When running an archive configured to delete data from the source database, only the appropriate free- format annotations are now deleted. (Free-format annotations are notes, assignable causes, and corrective actions that do not belong to any pull-down annotation list. Because, in release 9.0.8, the potential was introduced for free-format annotations to be deleted during the archiving process when they shouldn’t be, customers who employ them and who archive are encouraged to upgrade to release 9.0.9.)
4125: E-mails sent as a result of WinSPC’s E-mail trigger now display Chinese characters correctly for all e-mail addresses. (Accelerated Defect 4104.)
2347: When a tag’s Remember Previous Entry check box is unchecked, that tag is now presented in the Tags window with no default value, ensuring that an entry of a particular value for it is intentional. (The Remember Previous Entry check box is located on the Tag Setup window’s Settings tab. The Tags window is the window used by data collectors to supply tag values.)
2975: WinSPC’s rendering of PDF reports now compensates for PDF readers that improperly display special characters such as (mu) and (sigma), resulting in those characters being correctly and consistently displayed.
3211: The time required for the Properties window within the Administrator window to open when there are a significant number of entries in the event log is now reduced.
3270: The Confirm Password prompt now accepts only passwords of users explicitly selected during the setup of the Prompt for Password trigger, which is the trigger that causes the Confirm Password prompt to be displayed.
3295: The speed with which WinSPC’s DBSweep utility deletes orphaned tag values is now substantially increased.
3321: When saving a report template in WinSPC’s Report Designer, the default file type is now PDF.
3626: When a user resizes the Blueprint Setup window, the image box within it now resizes correctly.
3630: The circumstance that resulted in an Interface not supported error in WinSPC’s Administrator windowno longer causes this error. (The circumstance consisted of attempting to create a new object—tag, variable,etc.—while a linked item is selected in the Administrator window’s right pane.)
3694: The WinSPC splash screen that displays during an upgrade no longer hides other upgrade prompts orwindows in a way that prevents them from being used.
3714: Assigning filtering criteria to the export of a data set results in the export file now having the expected,filtered data.
3737: Revoking a station’s access to a collection plan folder no longer prevents the Admin superuser fromviewing that folder on that station.
3741: Stations running Windows with Chinese selected for the regional settings can now save WinSPC reportsas PDF files in such a way that no errors are generated when those PDF files are subsequently opened.
3754: Copies of WinSPC reports that have been previewed and e-mailed are no longer saved to a local folder.
3756: The Variable Chart Matrix dashboard now uses the default chart type that is configured for a variable todisplay that variable’s data.
3780: The access violation that, under specific conditions, would occur during the shutdown of WinSPC nolonger occurs.
3872: List filter groups in the Data Set Builder now function as expected.
3916: The archiving of WinSPC data from an Oracle database now requires significantly less time.
3946: Collection plans configured to Prompt for tags on every cycle and/or Prompt for tags on everycharacteristic now enforce the entry of new tag values at the appropriate times before data collection ispermitted to continue.
3954: WinSPC’s security utility now leaves permissions to the ProgramData folder unchanged for users anduser groups who have more than the minimum Read and Execute level.
3978: Resizing the Tags window now results in that window’s Tag Value pane resizing proportionately, makingit easier for users to view and enter long tag values in full.
3983: Custom subgroup-level control tests with names exceeding 50 characters no longer truncate data or cause other issues when violated.
3988: For WinSPC implementations that utilize the Chinese Simplified translation, the Parity field on the Device Setup window’s Connection tab for a serial device no longer gets inadvertently blanked out and now functions as expected.
4009: A 30-second timeout within INSERT SQL statements no longer occasionally causes the posting of a subgroup to the WinSPC database to fail.
4011: Upgrades no longer occasionally result in the loss of offline data that hasn’t been uploaded to the WinSPC database.
4019: Evaluation or temporary WinSPC licenses are now able to be extended when approved by WinSPC Support.
4031: WinSPC implementations employing Chinese Traditional or Chinese Simplified translations are now able to get test readings and test the device configuration in the Device Setup window an unlimited number of times.
4034: The ASUBGRP table in the WinSPC database is now also indexed by the DATETIME_ column, resulting in noticeably faster queries of that table’s data.
4047: The WinSPCp.dll library now successfully encrypts and decrypts passwords when called from Visual Studio during the debugging of a properly hashed, external application.
4048: WinSPC reports can now sort data based on a calculated statistic (e.g., Cpk) in descending order.
4078: Administrative users are now able to edit their own first name, last name, and e-mail address on the User Setup window’s General tab. VERSION 9.0.7
4030: Local databases used to run WinSPC in an offline mode are now programmatically compressed by WinSPC when their size approaches the limitations of Microsoft Access (the database software integrated into WinSPC for offline functionality) that could risk corrupting data. This compression occurs when offline mode is initiated, significantly reducing the corruption risk. In cases where a local database cannot be sufficiently compressed, a message indicating the offline mode cannot be used will be displayed and customers are invited to contact WinSPC Support for assistance.
3931: Changes made to the setup of WinSPC users, including the locking and unlocking of user accounts, on an offline WinSPC client and updated in the main WinSPC database when that client goes back online are now properly propagated to all other offline client databases.
3932: Tag lists from the main WinSPC database now correctly synchronize with client databases for offline use.
125: When uploading data collected offline, WinSPC now manages any termination of the connection to the main WinSPC database in such a way that the upload resumes and completes properly once the connection is restored.
1263: Translation of the Synchronization progress bar now occurs as expected. (This progress bar appears after checking the Can Work Offline check box and clicking OK on the Station Setup window’s Miscellaneous tab.)
1299: Collecting data offline now results in a local database that is the appropriate size.
1487: Adding a blank value to a list of assignable causes, corrective actions, or notes and then synchronizingan offline WinSPC database and main WinSPC database no longer occasionally duplicates values in the tablesfor assignable causes, corrective actions, or notes.
1492: Dropdown lists of tag values are now visible and function as expected when collecting offline data.
2064: Free format tag values can now be entered when collecting data offline (even if the tag is configuredwith a Response Type of Both and a List Update of None).
2795: Erroneous values in the WinSPC.ini file that prevent WinSPC from finding the database no longerinterfere with WinSPC’s offline functionality.
2981: Uploading of values in the PREVTAGVALUE table now occurs as expected when synchronizing databases after offline data collection.
3096: The circumstances that occasionally caused an Access Violation error associated with the Tags prompt when loading a collection plan no longer cause this error.
3286: After using Task Manager to stop the synchronization of an offline database with a main database, WinSPC now resumes and completes the sync the next time WinSPC is run on the station with the offline database and establishes a connection to the main database.
3688: Report templates configured to group tag values now do so correctly.
3693: A Cannot change Visible in OnShow or OnHide error will no longer occasionally occur when clicking on asubgroup or prompting for notes in Data Collection.
3742: New user passwords can now be changed to blank when offline functionality is enabled.
3768: Users who get locked out when working in WinSPC offline are now able to get their account unlocked.The unlock procedure is performed by a qualified supervisor and consists of clicking the Unlock User button that appears in the Access Center when an offline user has been locked out and, in the Unlock User window that appears, supplying the name of the locked-out user and his or her own supervisor credentials. A qualified supervisor, in this case, is a user who has been assigned the Edit Users and User Groups permission and is hierarchically senior to the user group to which the locked-out user belongs. (The Admin user is a qualified supervisor to all other users.)
3792: When running a Simplified Chinese translation and editing tag information, the circumstances that occasionally caused a Format ‘%d’ invalid or incompatible with argument error no longer cause this error.
3847: Clicking Cancel on the Tags prompt for a collection plan that is configured to prompt for tags (or jobtags) on collection plan load no longer occasionally loads the Collection Plan window when the user, instead,should be taken back to the window from which they attempted to load the collection plan.
3852: Users can now have WinSPC release 9.0.5 (or newer) installed and install earlier releases in the version 9series.
3854: The typo “toautomatically” in the WinSPC Upgrade: Security Credentials Required window has beencorrected to “to automatically”.
3862: The LotSize and Total OLE properties of the Data Collection object (used for attribute data collection)now work as intended.
3882: The Last Week and This Week data filters now work consistently.
3888: Changing the ID of a station in offline mode no longer interferes with proper synchronization when aconnection to the main database is reestablished.
3850: When running an archive configured to delete data, only the appropriate notes, assignable causes, and corrective actions are now deleted. (Since, in earlier releases, the potential exists for notes, assignable causes, and corrective actions to be irreversibly deleted during the archiving process when they shouldn’t be, customers who archive are encouraged to upgrade to release 9.0.4.)
3600: Complete functionality of the WinSPC application server now resumes after an inability to locate the WinSPC.ini file.
3645: Users can now toggle off the Spreadsheet Date Entry pane in the Data Collection window for one variable separately from other variables in the same visual group.
3678: A change to the on or off state of a collection plan’s Spreadsheet Date Entry pane in the Data Collection window now persists until the state is changed again, even if a subsequent change is not made until a later data collection session.
3690: The WinSPC installer executable should no longer be reported as corrupt or invalid when downloaded using Internet Explorer.
3692: The complexity of a specific customer’s domain that prevented integration between Active Directory and WinSPC no longer prevents integration.
3703: The precise circumstances that resulted in an error when exiting WinSPC no longer have this effect. The circumstances include, among other things, content having been copied to the WinSPC client’s clipboard.
3704: Data collection in WinSPC now operates at normal speed following the archiving of large amounts of data.
3711: Archive databases can now properly be cached without affecting the cache of the main database.
3719: The OLE properties DefectIndex, DefectName, LocationIndex and LocationName properties can now beused as documented.
3721: An edit to a sample value, regardless of how many times that value was previously edited, is nowreflected in that value’s parent subgroup and on charts.
3753: When loading a collection plan through OLE, an Invalid Pointer Operation error could rarely occur. Thishas been resolved.
3757, 3775: The WinSPC application server now properly shuts down (and saves the current cache) when theserver operating system is shut down or restarted.
3762: Active Directory users are now properly auto-populated in WinSPC implementations that employ anOracle database.
3765: If Active Directory integration is enabled and the current station is configured to hide the login screen,launching WinSPC through OLE on the current station will no longer perform a login automatically. Now, the OLE application will need to supply a specific username and password to login or use the new LoginAsWindowsUser OLE property to login as the current Windows User. (For related details, see the new features section above regarding the WinSPC OLE changes.)
3769: Scheduled archives now start and stop as expected.
3797: The misspelling of the word dashboard has been corrected.
3798: Complete functionality of the WinSPC application server now resumes after an inability to locate theshared WinSPC folder.
3590, 3801: The WinSPC application server now successfully archives variables with an extremely largeamount of data.
3662, 3802: Values entered into data entry cells in the Data Collection window now remain visible up to the9th digit.
3664, 3803: WinSPC now continues to function normally after an attached OLE session exits.3718, 3804: The current values of the DefectIndex and StepDefectIndex OLE properties are now accurately returned.
3745, 3805: The Visible and RunHeadless OLE properties now function as expected regardless of whether theyare set before or after login.
3661, 3806: The Change User Password window’s Old Password field now appropriately has no default value.
3751, 3807: The settings related to changing passwords (on the System Settings window’s Password Controltab) now prompt users to change passwords only when it is appropriate.
3638, 3808: Users are now consistently free to leave their passwords unchanged when the Required passwordchange every check box (on the System Settings window’s Password Control tab) is unchecked.
3825: The Active Directory Resolver window now properly lists unlinked Active Directory users.
3826: The specific rare circumstances that prevented WinSPC from launching through OLE no longer have thiseffect.
3585: In the report designer, the PointsPerGraph property of the WinSPCChart component now works as expected.
3596: A Remote Desktop Services client that suffers a fatal error can now successfully reload the collection plan that was active at the time of the error.
3599: The access violation that sometimes occurred when exiting WinSPC no longer occurs.
3615: Collection plans that contain multiple prompted network devices no longer generate an access violationwhen exiting Data Collection.
3616: Upgrades no longer occasionally result in two or more report templates having the same name.
3619: The ReadyForLogin property of the OLE DataCollection object now functions as intended.
3620: The performance of data-intensive reports in environments with an active application server has beenenhanced.
3621: The CollectingAsStationName and CollectingAsStationID properties of the OLE DataCollection objectnow properly set the station alias.
3625: Long lists of Active Directory user groups are now imported quickly into WinSPC.
3631: Data can now be filtered by tags when running WinSPC in a Chinese Simplified Windows environment
3636: Archiving data that contains a large number of tags now takes significantly less time.
3647: Data can now be collected using a virtual Serial device in Remote Desktop Services (formerly known asTerminal Services) environments.
2835: Capability parameters in the Variable Analyzer are now consistent with those in legacy report books.
3516: Excel devices will now collect data from an Excel spreadsheet regardless of whether or not thatspreadsheet contains hyperlinks.
3529: WinSPC databases created in SQL Server that contain one or more tables with a schema that differs fromthe schema for the primary WinSPC tables can now be upgraded.
3531: Tag values can now be collected from an ODBC device regardless of whether or not that device useschannels.
3533: The format of data in an Excel file is now retained when that data is collected into WinSPC using an Exceldevice.
3541: Text File devices in use prior to an upgrade to WinSPC 9 now continue to function properly following theupgrade.
3571: A collection plan that is configured to collect its data under a station alias now retains that configurationwhen that collection plan’s properties are viewed or edited. (Configuring a collection plan to use a station aliasis done in the Station Selection pane of the Collection Plan Setup window’s Collection Plan Options tab.)
3579: Semicolons can now be used to separate email addresses when configuring an E-mail trigger.
3581: The unique condition that prevented a Version 9 upgrade from adding dashboards and upgrading reporttemplates and data sets no longer causes these effects.
3584: Reports now run considerably faster.
3594: WinSPC installations that contain one or more custom color schemes can now be upgraded.
3595: WinSPC no longer hangs when a network device is prompted for data.
1303: Data points on a Pre-Control chart in the Data Collection window can now be edited without generating an Access Violation.
2153: The Lifetime notification setting on the Timed Data Collection subtab of the Collection Plan Setup window’s Step Options tab can now be configured when variables and attributes are multi-selected on the Step Options tab.
2229: Archiving an attribute now results in a Historical marker being added to charts for that attribute.
2304: Adding one or more additional defect types to a previously configured attribute but clicking Cancelbefore those additional types are saved now discards those types as expected.
2306: When collecting attribute data, clicking in the New Value field no longer occasionally submits the datato the WinSPC database.
2308: When collecting attribute data, clicking Done no longer occasionally generates an Out of Order ReadingRejected message.
2310: When collecting attribute data, clicking Done no longer occasionally records the data incorrectly.
2334: The drop-down list of characteristics now expands as expected, even when one of the characteristics inthat list is an attribute for which keyboard data entry is not allowed.
2342: The Automatically prompt device option on the Timed Data Collection subtab of the Collection PlanSetup window’s Step Options tab is now properly disabled for attributes.
2446: The list of users and user groups in WinSPC Security Utility now properly and efficiently populates, even when the domain contains an unusually high number of users and user groups.
2534: Excel devices now correctly process data from an Excel file that contains merged cells.
2616: Querying an archive that has been converted from Paradox (used prior to the WinSPC 8 series) toAdvantage (used in the WinSPC 8 series) no longer occasionally results in an Access Violation.
2644: Custom queries in the Report Designer can now be edited when parameters are employed for a reporttemplate without generating a List Index Out of Bounds error.
2784: Archiving is now considerably faster.
2823: Report templates created using the Report Designer wizards now function as expected.
2927: The Data Listing report template can now be used with WinSPC databases created in Oracle 9i andOracle 10g.
2928: Custom queries in the Report Designer can now be created when parameters are employed for a reporttemplate without generating an error.
2954: The presence of a Timed Data Collection Prompt window indicating time has expired for the collectionof attribute data no longer generates an error when Done is clicked in the Data Collection window.
2970: When creating a new user, the Inherited check boxes for Screen Display and Printed Reports are nowchecked by default on the User Setup window’s Defaults tab.
2994: The axis labels on Pareto charts are now properly aligned.
2996: When working in the Chart Properties window from within the Report Designer, modifications to thefollowing Element Visibility settings on the General subtab of the Line Charts tab are now saved as expected:Upper Chart Visible, Middle Chart Visible, and Lower Chart Visible.
3023: A user can now change the password of another user only when the following two conditions are met:the user changing the password has been granted the Edit Users and User Groups permission; and the user whose password is being changed belongs to a user group that descends from the user group to which the user changing the password belongs.
3036: A user who is authorized to change the password of another user is now also authorized to set the User must change password at next login setting for that other user.
3038: Collecting data for an attribute that counts defective units and is configured with a fixed lot size of 1 no longer causes an error when the following sequence of actions is taken: enter 1 in the New Value field; left- click in the Total field; and click Done.
3138: Character limits for the TEST.TESTNAME and TESTFLDR.FOLDERNAME database fields are now 250 characters, regardless of previous upgrades performed.
3203: A scripting property for the Historical Control Limits Visible chart option is now available in the Report Designer.
3209: The savings-related columns in the Process Improvement Savings report are now properly highlighted.
3222: Exporting from the Variable Analyzer to CWR when one or more tag values are blank now results in thedata being properly exported.
3319: When data is being collected by an OLE application, the unique sequence of actions that unloaded acollection plan before displaying a Prompt For Notes and Message Box trigger when such a trigger shouldhave been displayed no longer has this effect.
3395: In multi-select mode, with a variable and attribute selected, the Automatically prompt device check boxon the Timed Data Collection tab is enabled and should be disabled.
3404: When collecting attribute data, pausing the ribbon by clicking in the Total field, editing the data, andthen clicking Done now results in the edited data being saved to the database as expected.
3409: When collecting attribute data, the following sequence of actions no longer generates an error: enter aLot Size value; press Enter; click in the Total field and enter a value; click Done.
3429: WinSPC can now be run on a Windows 8.1 client.
3440: The specific circumstances that resulted in an Out of Memory error in the app server log when caching alarge volume of data no longer cause that error.
3447: When a user in Data Collection is logged out as a result of the Automatic logout due to inactivity interval specified on the General tab of the System Settings window in the Administrator window being exceeded, that user’s session is now cleanly and fully terminated.
3487: Device overrides configured on the Station Setup window’s Device Overrides tab are no longer removed by a running of the DBSweep utility.
3488: User-defined sample level control tests that involve an evaluation of spec limits (Self.USL, Self.Target, Self.USL) now properly evaluate those limits.
Your main facility contact should have received an email containing the download information for WinSPC Maintenance Releases. If not, please contact our WinSPC Product Support by phone (248.447.0140) or by email (email@example.com) to request the download information or if you need assistance with the upgrade. WinSPC Product Support is available Monday through Friday, 9:00 a.m. – 6:00 p.m. EST.
About DataNet Quality Systems
DataNet Quality Systems empowers manufacturers to improve products, processes, and profitability through real-time statistical software solutions. The company’s vision is to deliver trusted and capable technology solutions that allow manufacturers to create the highest quality product for the lowest possible cost. DataNet’s flagship product, WinSPC, provides statistical decision-making at the point of production and delivers real-time, actionable information to where it is needed most. With thousands of installed facilities worldwide and distributors across the globe, DataNet is dedicated to delivering a high level of customer service and support, shop-floor expertise, and professional Continuous Improvement, Six Sigma, and Lean Manufacturing services.