README.TXT Release Notes for NetResults ProblemTracker Version 4.1.1 © Copyright 1997-2002 NetResults Corporation, All Rights Reserved. NetResults is a registered trademark of NetResults Corporation. ProblemTracker is a trademark of NetResults Corporation. **************************************************************** Release Notes for ProblemTracker Version 4.1.1 **************************************************************** Upgrade Instructions -------------------- You can upgrade any installation of ProblemTracker 3.0 or later to this version by installing this on the same machine as your current installation. Upgrade instructions for users of Version 4.1 are in section 2.0. Upgrade instructions for users of Version 4.0 are in section 3.0. Upgrade instructions for users of 3.0 - 3.6.1 are in section 4.0. To upgrade ProblemTracker 2.11 or earlier to this version, please contact NetResults Technical Support (send mail to pt_support@n2r6.com) for information regarding the required database format upgrade. DO NOT ATTEMPT TO UPGRADE AN EXISTING PROBLEMTRACKER 2.11 INSTALLATION USING THIS SOFTWARE WITHOUT CONTACTING NETRESULTS TECHNICAL SUPPORT. DOING SO IS NOT COVERED BY YOUR EXISTING SUPPORT AGREEMENT. System Requirements for use of New Features ------------------------------------------- NetResults ProblemTracker 4 has the following requirements. Listed first are the requirements for use of multinationalization features. These features require newer versions of web browsers and web servers as many international web features have only recently been supported (and many standards are in fact still "in progress" in this area). Listed second are the requirements if you do not require multinational support (in other words, if it is OK to limit usage to the western European languages listed below). In addition to the requirements below, you will need to install Visual SourceSafe 6.0 *with Service Pack 5* if you wish to use the new source code control integration features. Requirements to use Multinationalization options: ------------------------------------------------- By default, ProblemTracker supports western European (Latin1) languages including the following - Basque, Catalan, Danish, Dutch, English, Finnish, French, German, Icelandic, Italian, Norwegian, Portuguese, Spanish, and Swedish. If your language is *not* one of the above languages, your system requires the following: Client Requirements: o Any platform on which Internet Explorer (version 5.0 or greater) or Netscape (version 6.2 or greater) is available. o Microsoft Internet Explorer (version 5.0 or greater) or Netscape (version 6.2 or greater). Server Requirements: o 300 MHz Intel Pentium II or compatible system (450 MHz Pentium III or faster recommended). o 128 MB RAM (256 MB recommended) o 4 GB Hard Drive (ProblemTracker uses approximately 10 MB of hard disk space for each workgroup). o Windows 2000 Server o Microsoft Internet Information Server 5.0 with Microsoft hotfix http://support.microsoft.com/support/kb/articles/Q294/8/31.ASP to fix known bug with UTF-8 (Unicode) character set o Microsoft JET 4.0 Service Pack 5 If you have applied Windows 2000 Service Pack 2, JET 4.0 SP5 has already been installed. If not, you can find download and installation information on Microsoft's web site at: http://support.microsoft.com/support/kb/articles/Q282/0/10.ASP Optional Database Support: In addition to the included support for Microsoft Access, ProblemTracker can be used with the following database systems o Microsoft SQL Server 7.0 o Microsoft SQL Server 2000 o Oracle 8i o Oracle 9i General System Requirements (if not using multinational features): ------------------------------------------------------------------ Client Requirements: o Any platform on which Netscape Navigator/Communicator (version 4.07+), or Netscape (version 6.2 or greater, 6.0/6.1 not supported), or Internet Explorer (version 4.0 or greater) is available. o Netscape Navigator/Communicator (version 4.07+), Netscape (version 6.2 or greater, 6.0/6.1 not supported), or Microsoft Internet Explorer (version 4.0 or greater). Server Requirements: o 300 MHz Intel Pentium II or compatible system (450 MHz Pentium III or faster recommended). o 64 MB RAM (256 MB recommended) o 4 GB Hard Drive (ProblemTracker uses approximately 10 MB of hard disk space for each workgroup). o Windows NT 4.0 Workstation or Server, Windows XP, or Windows 2000 Server (Windows 2000 Server recommended). Windows XP and Windows NT 4.0 Workstation are only recommended for evaluation purposes as they are "desktop" operating systems (not "server" operating systems) and as such Microsoft has limited concurrent access to web servers running on them to a small number of users. o Microsoft Internet Information Server 4.0 or 5.0 (IIS 5.0 recommended) o JScript 5.1 or greater. If you are using Windows 2000 (IIS 5.0) or if you have Internet Explorer 5.5 (or greater) installed on your web server, you already have JScript 5.1+. If not, you need to install IE 5.5/6.0 or download & install Windows Script 5.5 from Microsoft: http://www.microsoft.com/msdownload/vbscript/scripting.asp o Microsoft Data Access Components (MDAC) 2.5 or greater. If you are using Windows 2000 Server, you already have MDAC 2.5+. If you are using Windows NT 4.0, you may not have MDAC 2.5+. Download links and installation information is available on Microsoft's web site at: http://www.microsoft.com/data We recommend use of MDAC 2.5 Service Pack 2. o Microsoft JET 4.0 Service Pack 5. If you have applied Windows 2000 Service Pack 2, JET 4.0 SP5 has already been installed. If not, you can find download and installation information on Microsoft's web site at: http://support.microsoft.com/support/kb/articles/Q282/0/10.ASP Optional Database Support: In addition to the included support for Microsoft Access, ProblemTracker can be used with the following database systems o Microsoft SQL Server 7.0 o Microsoft SQL Server 2000 o Oracle 8i o Oracle 9i ============================================= 1.0 Backing up your ProblemTracker databases ============================================= Prior to any installation operation, please be sure to backup your existing database environment. Version 3 Users: Access Users: ============= 1. Copy all ProblemTracker database files which are to be upgraded and archive the copies in a safe location. These files are shown below for a default installation. \ptdev\Database\Bugtrack.mdb \ptdev2\Database\Bugtrack.mdb \ptdev3\Database\Bugtrack.mdb \ptdev4\Database\Bugtrack.mdb \ptweb\Database\Bugtrack.mdb where: may be "C:\Inetpub\wwwroot" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 2. Copy all ProblemTracker attachment files and archive the copies in a safe location. These files are located in the path (folder) shown below for a default installation. \ptdev\Attachments \ptdev2\Attachments \ptdev3\Attachments \ptdev4\Attachments \ptweb\Attachments where: may be "C:\Inetpub\wwwroot" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 3. If you have customized the login page with your own html, you need to back up the corresponding files as well. These files are located in the path (folder) shown below for a default installation. \workgroup\loginbottom.htm \workgroup\logintop.htm may be "C:\Inetpub\wwwroot" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. Workgroup is ptdev, ptweb,ptdev2, ptdev3, ptdev4, etc. SQL Server 7.0/2000 or Oracle Users ========================= 1. You may backup SQL Server 7.0/2000 or Oracle databas(es) by using SQL Server or Oracle backup or data export operation. Backups may done to a hard disk as well as to tape. Please review your SQL Server or Oracle documentation for further information. The database(s) to backup include one or more of the following: ptdev, ptdev2, ptdev3, ptdev4, ptweb. 2. Copy all ProblemTracker attachment files and archive the copies in a safe location. These files are located in the path (folder) shown below for a default installation. \ptdev\Attachments \ptdev2\Attachments \ptdev3\Attachments \ptdev4\Attachments \ptweb\Attachments where: may be "C:\Inetpub\wwwroot" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 3. If you have customized the login page with your own html, you need to back up the corresponding files as well. These files are located in the path (folder) shown below for a default installation. \workgroup\loginbottom.htm \workgroup\logintop.htm may be "C:\Inetpub\wwwroot" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. Workgroup is ptdev, ptweb,ptdev2, ptdev3, ptdev4, etc. It is REQUIRED that you either copy the database file(s) to a safe place (Access only) or perform a backup (Access, SQL Server or Oracle). UNDER NO CIRCUMSTANCES IS NETRESULTS RESPONSIBLE FOR THE LOSS OF ANY DATA AS THE RESULT OF THE INSTALLATION PROCESS. Version 4 Users: Access Users: ============= 1. Copy all ProblemTracker database files which are to be upgraded and archive the copies in a safe location. These files are shown below for a default installation. \workgroup\Database\Bugtrack.mdb where: may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 2. Copy all ProblemTracker attachment files and archive the copies in a safe location. These files are located in the path (folder) shown below for a default installation. \workgroup\Attachments where: may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 3. Copy the Workgroup Management System database file. The default location is: \ptadmin\Database\ptadmin.mdb where: may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 4. If you have customized the login page with your own html, you need to back up the corresponding files as well. These files are located in the path (folder) shown below for a default installation. \workgroup\Include\loginbottom.inc \workgroup\Include\logintop.inc may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. SQL Server 7.0/2000 or Oracle Users ========================= 1. You may backup SQL Server 7.0/2000 or Oracle databas(es) by using SQL Server or Oracle backup or data export operation. Backups may done to a hard disk as well as to tape. Please review your SQL Server or Oracle documentation for further information. 2. Copy all ProblemTracker attachment files and archive the copies in a safe location. These files are located in the path (folder) shown below for a default installation. \workgroup\Attachments where: may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 3. Copy the Workgroup Management System database file. This will in Access format even if your workgroup databases are SQL Server or Oracle databases. The default location is: \ptadmin\Database\ptadmin.mdb where: may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. 4. If you have customized the login page with your own html, you need to back up the corresponding files as well. These files are located in the path (folder) shown below for a default installation. \workgroup\Include\loginbottom.inc \workgroup\Include\logintop.inc may be "C:\Inetpub\wwwroot\ProblemTracker" for Internet Information Server users. Or, it may be a value other than the default if the default was overridden in the original installation. Typically it is at the "root" of your (virtual) web site. It is REQUIRED that you either copy the database file(s) to a safe place (Access only) or perform a backup (Access, SQL Server or Oracle). UNDER NO CIRCUMSTANCES IS NETRESULTS RESPONSIBLE FOR THE LOSS OF ANY DATA AS THE RESULT OF THE INSTALLATION PROCESS. ============================================================================================= 2.0 Upgrading from ProblemTracker Version 4.1 to ProblemTracker Version 4.1.1 ============================================================================================= 1. GO TO SECTION 1.0 ABOVE AND BACKUP ALL OF YOUR PROBLEMTRACKER DATABASES BEFORE PROCEEDING. 2. Temporarily disable any anti-virus software while you run the Version 4 installation program and perform configuration steps in the Workgroup Management System (WMS). This is recommended so that your anti-virus software will not prevent the installation program or WMS from performing operations such as copying files, running scripts, configuring your web server, setting file permissions and registry entries. Your anti-virus software can be reactivated safely after you have completed the installation steps and any necessary WMS configuration. 3. Temporarily stop all IIS services while you run the Version 4.1.1 installation setup program. Running the installation setup program without stopping all IIS services will prevent you from receiving all of the necessary file updates included in this version. 4. Install ProblemTracker Version 4.1.1. To do this, login to the web server machine as Administrator and then run (double-click from Windows Explorer) pbtrk411.exe. When the installation setup program has finished, you will be asked to reboot your system. 5. Login to the Workgroup Management System (WMS) by going to Start->Programs->NetResults ProblemTracker 4->Workgroup Management System->Login Page To upgrade your workgroups, click on the Admin icon on the Button bar. Select the option "Upgrade Workgroups from previous 4.x version to ProblemTracker 4.1.1". A complete list of the workgroups to be upgraded will be displayed. Click on the "Upgrade All Workgroups" button to proceed. The upgrade process may take a few minutes depending on the speed of your system and the number of workgroups to be upgraded. Wait until all workgroups are upgraded before attempting another operation. When all workgroups have been upgraded, you will see each workgroup's name displayed with a check mark to the left. Click on the "OK" button that appears at the bottom after the upgrade process is complete. 6. Re-activate your anti-virus software and re-start IIS services. 7. Login to a workgroup as Admin, then click on the Admin icon in the button bar. Click on the Maintenance button, then click on the "Fix Email Issue" button. When complete, the status bar will display "Operation Complete". Click on the Logoff button. 8. Repeat step 7 for each workgroup in the Workgroup Management System. Your system has now been upgraded to Version 4.1.1 for all workgroups. ============================================================================================= 3.0 Upgrading from ProblemTracker Version 4.0 - 4.0.3 to ProblemTracker Version 4.1.1 ============================================================================================= 1. GO TO SECTION 1.0 ABOVE AND BACKUP ALL OF YOUR PROBLEMTRACKER DATABASES BEFORE PROCEEDING. 2. Temporarily disable any anti-virus software while you run the Version 4 installation program and perform configuration steps in the Workgroup Management System (WMS). This is recommended so that your anti-virus software will not prevent the installation program or WMS from performing operations such as copying files, running scripts, configuring your web server, setting file permissions and registry entries. Your anti-virus software can be reactivated safely after you have completed the installation steps and any necessary WMS configuration. 3. Temporarily stop all IIS services while you run the Version 4.1.1 installation setup program. Running the installation setup program without stopping all IIS services will prevent you from receiving all of the necessary file updates included in this version. 4. Install ProblemTracker Version 4.1.1. To do this, login to the web server machine as Administrator and then run (double-click from Windows Explorer) pbtrk411.exe. During the installation setup program, you will be prompted to select a server time zone. Please ensure that you select the same time zone as the time zone set in your operating system. Failure to select the same time zone as your operating system's setting will result in incorrect date and time values in your ProblemTracker data. These incorrect values cannot be corrected at a later time. When the installation setup program has finished, you will be asked to reboot your system. 5. Login to the Workgroup Management System (WMS) by going to Start->Programs->NetResults ProblemTracker 4->Workgroup Management System->Login Page To upgrade the workgroups, click on the Admin icon on the Button bar. Select the option "Upgrade Workgroups from previous 4.x version to ProblemTracker 4.1.1". Select a workgroup from the pulldown menu, then click on the Upgrade Workgroup button. A confirmation page will be displayed confirming that the workgroup files have been upgraded. Click on the Continue button to proceed with upgrading the data for the workgroup. Another confirmation page will be displayed listing several areas of your database that need a time zone selection. Select a time zone for each these areas. The time zone you select can be different from the time zone you selected for your ProblemTracker server during the Version 4.1.1 installation setup. Click on the Upgrade Data button to proceed, then click OK to confirm. Click OK after the upgrade operation has completed. 6. Perform step 5 for each workgroup in the Workgroup Management System. 7. Reactivate your anti-virus software and re-start IIS services. Your system is now upgraded to ProblemTracker 4.1.1 for all workgroups. ============================================================================================= 4.0 Upgrading from ProblemTracker Version 3.0.5 - 3.6.1 to ProblemTracker Version 4.1.1 ============================================================================================= 1. GO TO SECTION 1.0 ABOVE AND BACKUP ALL OF YOUR PROBLEMTRACKER DATABASES BEFORE PROCEEDING. 2. Temporarily disable any anti-virus software while you run the Version 4 installation program and perform configuration steps in the Workgroup Management System (WMS). This is recommended so that your anti-virus software will not prevent the installation program or WMS from performing operations such as copying files, running scripts, configuring your web server, setting file permissions and registry entries. Your anti-virus software can be reactivated safely after you have completed the installation steps and any necessary WMS configuration. 3. ProblemTracker Version 4 requires a new license key. Your ProblemTracker Version 3 license key(s) will not function with ProblemTracker 4. If you have not received your Version 4 key, you can start a 15 day trial. NetResults Sales will send you a Version 4 key if your support and upgrades subscription is current. Please contact NetResults Sales at pt_sales@n2r6.com if you have licensing or subscription questions. 4. This procedure assumes that you are installing ProblemTracker Version 4.1.1 on the same machine where you have ProblemTracker 3 installed. If you are installing ProblemTracker Version 4.1.1 on a different machine than where you have ProblemTracker 3 installed, please review the following FAQ entry for instructions: http://www.problemtracker.com/pt_faq_howdoi4x.htm#moveupgrade40 5. Install ProblemTracker Version 4.1.1. To do this, login to the web server machine as Administrator and then run (double-click from Windows Explorer) pbtrk411.exe. During the installation setup program, you will be prompted to select a server time zone. Please ensure that you select the same time zone as the time zone set in your operating system. Failure to select the same time zone as your operating system's setting will result in incorrect date and time values in your ProblemTracker data. These incorrect values cannot be corrected at a later time. Enter your license key(s) information by going to Start->Programs->NetResults ProblemTracker 4->NetResults License Manager After the installation setup program has finished, you will be asked to reboot your system. 6. Log into the Workgroup Management System by going to Start->Programs->NetResults ProblemTracker 4->Workgroup Management System->Login Page Click on the Admin icon and select the option "Upgrade Workgroups from versions 3.x to ProblemTracker 4.1.1", then click on the Continue button. 7. In the Current Workgroup details section, type in the current workgroup name, select the current database type and web site, then click on the Continue button to proceed. 8. In the New Workgroup details section, enter information for the new workgroup including Workgroup Name, Description, Location, Template, Web Site, Host Name/IP Address, Port Number, and history comment. Please choose a workgroup name and location that are different than your current 3.x workgroup. This is very important because choosing an identical name will cause you to overwrite your 3.x workgroup. Please make sure you have a backup of your database before proceeding. Once you have entered the necessary information, uncheck the box to re-direct your Version 3 workgroup URL to your Version 4 database. Click on the Continue button to proceed with the upgrade process. 9. A confirmation screen listing information for both the current workgroup and the new workgroup will be displayed. Click on the Back button to make any necessary changes. Otherwise, click on the Upgrade Workgroup button to complete the Upgrade operation. Click OK to confirm. A confirmation page will be displayed confirming that the workgroup files have been upgraded. Click on the Continue button to proceed with upgrading the data for the workgroup. Another confirmation page will be displayed listing several areas of your database that need a time zone selection. Select a time zone for each these areas. The time zone you select can be different from the time zone you selected for your ProblemTracker server during the Version 4.1.1 installation setup. Click on the Upgrade Data button to proceed, then click OK to confirm. Click OK after the upgrade operation has completed. 10. Go back to the Workgroup Management System Home Page. To login to your upgraded workgroup, click on the key icon to the left of the workgroup name from the list on the WMS Home Page. 11. Repeat steps 6 - 10 for each workgroup you wish to upgrade to ProblemTracker 4.1.1. 12. Login to each workgroup to confirm that the upgrade was successful. 13. There are significant changes to the way your Version 3 data will be represented after upgrading to Version 4.1.1. Please review the details at: http://www.problemtracker.com/pt_41information.html#upgrade 14. After upgrading all the workgroups to Version 4.1.1, login to each of the workgroups and make sure that the upgrade was successful. After doing this, uninstall ProblemTracker 3 from your machine following the steps below. A. Select "Start / Programs / NetResults ProblemTracker 3 / Modify-Uninstall ProblemTracker". B. When the uninstall starts, click "Next". C. Select "Remove" option and click "Next". D. > For SQL Server or Oracle Users: Select "Components only (leave databases)" option as SQL Server or Oracle database(s) are upgraded "in place". If you select "Components and databases", you will delete the 4.1.1 SQL Server or Oracle database(s). > For Access Users: Select "Components and databases" option as Access database(s) are copied before being upgraded. E. Click "Next" and complete the uninstallation. 15. Reactivate your anti-virus software. 16. Now you have successfully upgraded to ProblemTracker 4.1.1. ============================================================= 5.0 Changes in ProblemTracker Version 4.1.1 ============================================================= 5.1 Enhancements ---------------- o When configuring a set of Dependent Pulldowns in Version 4.1, if no relations were configured between the option menu items of the related pulldown menus, the Default Items section for the child pulldown would not show any implicit (temporary) default option menu item(s). This has been changed such that an implicit (temporary) default is displayed for each option menu item in the parent pulldown. Implicit defaults are denoted by {Default}. Explicit defaults are denoted by [Default]. More information is available in the Online Help Document at: http://www.problemtracker.com/pthelp4/Admin/bots_dependent_pulldowns.htm 5.1 Fixes ---------------- o When upgrading from Version 3.x to 4.x with the email notification for "On Add and Delete, notify..." set to notify only the Current State Manager, invalid information would be added to the "On Add, notify..." and "On Delete, notify..." rules after the upgrade. This has been corrected such that the upgrade will create both "On Add..." and "On Delete..." rules without invalid information. o In Version 4.1, when running a query and using the Edit Results operation to change a field which was part of the query criteria, history entries were not created for the affected records. This has been corrected such that the history entries are created in this situation. o When using the date clean up utility when upgrading from Version 3.x to 4.x with dd/mm/yyyy format, the user could be prompted to update system generated dates. This has been corrected to allow the date clean up utility to update the system generated dates without prompting the user. o In Version 4.1, when a user had set a saved group query as the default query and the user group was deleted, a system error would occur. This has been changed such that the saved group query "Default [Users]" will become the user's default query when the user group is deleted. Likewise, if a user has a saved group query as the default query and the user is removed from the group, the saved group query "Default [Users]" will become the user's default query. o In previous versions, if a group saved query was saved with a personal report layout, a system error would result when another user ran the group saved query and used the "Format For Printing" option. This has been corrected such that a system error will not be generated. Instead, the global default report layout ("Default [Users]") will be used to format the query results for printing. o When upgrading from a previous version to 4.1 with an attachment file that contained a single quote in the name, a system error would be generated. This has been corrected such that the single quote in an attachment file name can be upgraded properly without generating an error. o In previous versions, when the number of characters entered into a field with "BigText" format during the Add operation was over the limit for the database type (typically 64,000+ characters), a stack overflow error would be generated during the Add or Edit operations. This has been corrected such that the user will be prompted if the number of characters is over the limit before the new record can be added. o In Version 4.1, when restoring a deleted option menu item, the dependencies configured for the option menu item were not restored. This has been corrected such that when a deleted option menu item is restored, its previous associations to other option menu items are also restored. o In Version 4.1, if the option to "delete all records" was selected when deleting an option menu item, any attachment files associated with these records were not deleted. This has been fixed so that the corresponding attachments files are deleted with the records in this situation. o In previous versions, when multiple task fields shared the same sort order within a transition, the fields were not sorted in alphabetical order. This has been changed such that multiple task fields with the same sort order within a transition will be displayed in alphabetical order. o In Version 4.1, if a user has visibility to a field on the Query page and is using this field in a Saved Query and the user group that provided the user with visibility to this field is deleted, then the Saved Query was not updated to remove the field. This has been changed such that the user will be prompted that the Saved Query will be updated to remove the field (since the field is no longer visible to the user due to the user group being deleted). o In Version 4.1, if 2 or more columns were used to display Attachments or Source Code files in a report layout, the description of the files would not be displayed in every column when using the "Format For Printing" option. This has been fixed to allow every column to display the appropriate description. o While using Netscape 6.2 with Version 4.1, an uneditable space was added to the option menu item labels of dependent pulldowns. This has been corrected so that the extra space is no longer present when using Netscape 6.2 with dependent pulldowns present. o When using Netscape 6.2 with previous 4.x versions while editing an email notification rule, the Assignee was selected even if it did not previously exist in the rule. This has been corrected such that the Assignee is not selected when editing a rule unless it already existed within that rule. o When using Netscape 4.x with previous ProblemTracker 4.x versions to upgrade from ProblemTracker 3.x, if certain date "clean up" operations that required user intervention (such as correcting a date that was in MM/DD/YYYY format when system settings were for all dates to be in DD/MM/YYYY format) were performed, one of the tables used to enter corrections was not displayed. This has been fixed so that Netscape 4.x can be used for the upgrade operation. ============================================================= 6.0 Changes in ProblemTracker Version 4.1 ============================================================= 6.1 Enhancements ---------------- o Field Visibility has been added. Fields may be displayed or hidden based on a User Group membership on the Add, Edit, View, Home, and Query pages as well as in Email. o ProblemTracker now supports multiple time zones. Each user can specify a time zone which they wish to use when entering or viewing date/time fields. o The ability to configure Dependent Pulldowns is now available, allowing the option menu items in a pulldown to be dependent on the option menu item selected in another (parent) pulldown. For instance, the value selected in a "product" pulldown can be configured to limit (specify) the list of items that will be displayed in a "component" pulldown. o The ability to sort reports (query results) dynamically is now available. Just click on the column name in a report on the Home or Query page to sort by that column. Click twice to sort in descending order rather than ascending order. o ProblemTracker now supports the use of Oracle 9i as the database software. o ProblemTracker now supports the use of Oracle 8i or 9i database on the Sun Solaris platform. o ProblemTracker now supports the use of Microsoft Windows XP. However, it is only supported for evaluation purposes. Microsoft has designated Windows XP as a "desktop" operating system (not a "server" operating system) and as such has restricted the number of users that may access a web server at one time on Windows XP. o In previous versions of ProblemTracker, the User ID (username) was displayed in various reports (Query, History, Home, View) as well as in Email. Now, you can select the format to display a user's identity in reports and email. The available options are: User ID, First Name, Last Name, Full Name. Upgraded systems will default to User ID for backward compatibility. Newly added workgroups will default to Full Name. o The ability to task records listed in the Second Home Page Report is now available. o When configuring a task field for a transition, the record order listed for the field in the Define Schema will now be the default value for the order of the task field in the transition. o The ability to remove the history comment from being displayed in a transition is now available. When a user selects a transition which is configured such that the history comment is not displayed and there are no task fields, the record will be updated immediately after selecting the transition, thereby allowing the task operation to be completed in fewer steps. o The functions on the Workgroup Database Tools page have been moved into the Workgroup Management System. o Users can now select an Advanced Saved Query as their default saved query (the one which is selected by default when they click the Query icon). o The following Help sections have had new information added. New sections are marked with (*): Installation Guide (*): Introduction: Overview (*) Setup: Preparation for Installing ProblemTracker Setup: System Requirements User's Guide: Operations: Logging In Operations: Adding Records Operations: Editing Records Operations: Querying Records Operations: Using Saved Queries and Reports Operations: Advanced Queries Admin Guide: Administration Guide: Tracking Defects with ProblemTracker: Code Development Template Administration Guide: Tracking Defects with ProblemTracker: Web Development Template Administration Guide: General Preferences Administration Guide: User Administration: User Groups Administration Guide: User Administration: User Privileges Administration Guide: Customizing the Data Record Administration Guide: Customizing Menu Values Administration Guide: Customizing Pulldown Menu Dependencies (*) Administration Guide: Customizing Workflow Administration Guide: Customizing the Login Page Administration Guide: Permanently Deleting Multiple Records Workgroup Management Guide: Introduction: Overview Introduction: Logging In Introduction: Adding a Workgroup Introduction: Deleting a Workgroup Introduction: Managing Aliases Introduction: Moving a Workgroup Introduction: Migrating a Workgroup Introduction: Synchronize Anonymous Account Introduction: Viewing Global Workgroup Information Introduction: Logging Workgroup Information Introduction: Blocking and Unblocking Workgroups Introduction: Managing Web Server Security Introduction: Workgroup Database Operations (*) Introduction: Upgrading Version 3.x Workgroups Introduction: Upgrading Version 4.x Workgroups (*) Appendix A: Using Oracle 8i (or later) Database Appendix B: Database Administration 6.2 Fixes --------- o In previous versions, when using a date field as part of an Advanced Query, a system error would be generated. This has been corrected to allow the advanced query to run successfully with a date field present. o In previous versions, searching Text or BigText fields for key words using an Advanced Query was not returning the expected results. This has been fixed so that advanced query key word searches generate the correct results. o Starting in version 4.0, the values for the From Email Account and Send Email Account are swapped, meaning that the from account was being used as the send account and vice versa. This has been corrected. o In previous versions, when using Windows NT 4.0 as the server machine, attempting to block/unblock a workgroup via the Workgroup Management System was not successful. This has been corrected to allow the workgroup to be blocked/unblocked when ProblemTracker is installed on a Windows NT 4.0 machine. o In previous versions under some certain instances, an attachment file upload could fail on a heavily loaded server (for example, when an application on the server is running with unlimited CPU), causing a timeout to occur and the system to no longer respond. This has been fixed such that the file upload will be handled in the case of a system with a heavily loaded CPU. o All system generated saved queries ("Default", "Assigned To Me [Users]", and "Reported By Me [Users]") will now exclude soft-deleted records (those that are not actually deleted from the database). This change may affect system generated saved queries in upgraded installations as well as new installations. If you wish to configure these system generated queries to include soft-deleted records, please see the related entry in our Frequently Asked Questions section at: http://www.problemtracker.com/pt_faq_howdoi4x.htm#deleted ============================================================= 7.0 Changes in ProblemTracker Version 4.0.3 ============================================================= 7.1 Enhancements ---------------- There are no enhancements in release 4.0.3. This release only contains fixes. 7.2 Fixes --------- o In previous 4.0.x versions, a "memory leak" occurred when a file attachment was added (a file was uploaded). The memory leak (increase in memory usage of the ProblemTracker "application") was equivalent to the file size. If enough large files were added, the system could run out of memory. This has been fixed. o In previous 4.0.x versions, a script timeout (web page timeout) could occur if a file upload took longer than 3 minutes. On IIS 4.0, a script timeout may also result in a session timeout (the user's ProblemTracker login session is ended by IIS when it performs the script timeout operation). On IIS 5.0 (Windows 2000), only the script timeout occurs (the user's ProblemTracker login session is not ended by IIS). During file upload the script timeout is now properly adjusted based on the file size, so that on any link with an effective upload rate of at least 2 KBytes per second (a 28.8 Kbps modem is faster), no timeout will occur. o In previous 4.0.x versions, if you were using Internet Explorer, started an Edit operation (go to the Edit page, but don't click OK), then used File->New to create a new window and performed a View, Edit, Task, or Delete operation on another record, then went back to the original window and clicked OK (on the original "pending" Edit operation), the last Edit operation would update the wrong record (it would update the record that was used in the intervening View, Edit, Task, or Delete operation). This could also happen if you started an Edit operation, then immediately started a second Edit operation (choose Edit icon in toolbar), then clicked Cancel on the second Edit (which would return you to the original Edit page), then clicked OK from the first Edit operation page. This could not occur if you started the Edit (click the Edit icon in the toolbar or in the Home or Query results pages), made your changes, then clicked OK on the Edit page without any intervening operations on other records. This issue has been fixed (intervening operations on other records will not result an Edit operation that updates the wrong record). However, in general, we recommend that you do not use multiple browser windows (use File->New in IE while logged in to ProblemTracker) on the same workgroup (login) at the same time. ============================================================= 8.0 Changes in ProblemTracker Version 4.0.2 ============================================================= 8.1 Enhancements ---------------- o It is now recommended that users temporarily disable anti-virus software while running the installation program and while performing operations in the Workgroup Management System. This is recommended so that your anti-virus software will not prevent the installation program and WMS from performing operations such as copying files, running scripts, configuring your web server, setting file permissions and registry entries. Your anti-virus software can be reactivated safely after you have completed the installation steps and any necessary WMS configuration. o In previous versions, the use of TCP/IP for all Workgroup Management System communications with SQL Server was not enforced. Now all communications from ProblemTracker to SQL Server are via TCP/IP (for improved performance and simplified firewall configuration). 8.2 Fixes --------- o When configuring a transition to use the option "Prompt with ", the list of states presented during the Task operation was not sorted according to the order value of each state. This has been fixed such that the states will be ordered correctly during the Task operation. o When using Oracle as the database type for a workgroup in previous versions, adding a state to a state group would result in a state appearing in both the "In Use" and "Not In Use" columns. The state actually was properly added (In Use), but the display was incorrect. This has been corrected so that the columns are updated appropriately when a state group is edited. o When using an Oracle database and specifying a "Date" type field as a Sort By column in a Query, a System Error was generated when running the query. This has been fixed. o If a system contained more than one Product with the same email notification rules, ProblemTracker was generating duplicate email notification messages to some users. This has been corrected so that duplicate email notification messages are no longer sent to users. o When using the Task operation, email notifications to the original Reporter were not always sent. This has been fixed. o If a Task operation displayed a list of users to select a new assignee, the list was not alphabetically sorted. This has been corrected such that the list of possible new assignees is sorted alphabetically. o If the PRN field was not the "top" field (the one with the lowest Record Order value), then a system error was generated when editing a PRN (after clicking the OK button on the edit page). This has been corrected such that the PRN field can be set to any Record Order value without generating a system error. o When a workgroup was created on a different web site than the Workgroup Management System, an error would be generated when trying to use the Show Chart function or when trying to use the Database Admin operations for the workgroup. This has been fixed. o If ProblemTracker was installed on a non-English operating system, a "type mismatch" error was generated upon login in a few cases (specifically the French version of Windows 2000, but this could potentially affect other non-English versions). This has been fixed. o In previous versions, when the Product field was changed for a record in the Edit page, the Status was changed to the Default Add State associated with the new Product selected. This has been corrected such that the Status field is not changed automatically when the Product field is changed on the Edit page of a record. o In previous versions, when a field included in an advanced saved query was moved to the "Not In Use" column, the advanced saved query would continue to include this field to generate results. This has been fixed such that a field that has been removed from the data record ("Not In Use") will also be removed from any advanced saved queries. o When using the Workgroup Management System to migrate an Access database to Oracle, the link to the Help section discussing Oracle configuration was invalid. This has been corrected. o On some systems, when browsing to the Workgroup Management System Login Page, a warning would be generated stating that the login user's credentials may not be sufficient to access the Workgroup Management System. In Windows 2000 Domain Server configurations where a domain level user was a member of the local Administrators user group, this warning was incorrect. In that case, the warning is no longer displayed. o If a ProblemTracker system was moved to another machine, a system error would be displayed on the first login to the Workgroup Management System. This has been fixed. o On systems with multiple workgroups distributed across multiple virtual web sites, moving ProblemTracker to another machine by using the option "Populate Workgroup based on WMS database" would fail if the new machine did not have the same virtual web sites as the old machine. The populate function now allows the user to enter the new machine's web site information as a part of the populate process. o In version 4.0.1 on some systems, the installation setup program did not set the appropriate file system permissions on some directories. This resulted in errors when trying to perform operations in the Workgroup Management System or on the workgroup Database Tools page. This has been corrected such that the installation program will set the necessary permissions on all directories created during installation. o When attempting to move or migrate a SQL Server workgroup in previous versions, the "Get Data" button would not obtain the data path in some cases. This has been corrected such that the path will obtained in all valid cases. o If you upgraded from version 4.0 to version 4.0.1, and you have added users in version 4.0, these users got a system error on the home page in some circumstances. This was corrected to eliminate the errors with the home page for these new users. o After upgrading from Version 3.x to Version 4.0.1 with any of the following RelNum type fields in use (RelNum76, RelNum80, RelNum84), a System Error was be displayed when attempting to Edit or Preview the system generated "Assigned To Me [Users]" and "Reported By Me [Users]" Saved Queries. Attempts to directly run one of those Saved Queries from the Query page, then subsequent attempts to access the Query page (clicking the Query icon) would fail. This has been corrected such that errors are not generated when editing saved queries or running queries with these RelNum fields. o In WMS, when attempting to synchronize the password for the ProblemTracker anonymous user in WMS, an error would be generated if the password was blank. This has been changed such that a blank password cannot be entered when using this option. ============================================================= 9.0 Changes in ProblemTracker Version 4.0.1 ============================================================= 9.1 Enhancements ---------------- o Advanced Queries can now be used in Home Page reports. o The Preview operation is now supported for Advanced Queries. o The Show Chart function in the Summary page is now supported for Oracle workgroups. o The Export Tables function in the Database Administration Utility page is now supported for Oracle workgroups. o The Netscape 6.2 (or greater) browser is now supported for use with multinational (UTF-8 character set) workgroups. o Actions associated with Source Code Control operations have been added to the History page. The following actions can now be selected for use in History queries: "SCC_ADD", "SCC_EDIT", and "SCC_DELETE" for adding, editing, and deleting the source code file list for a problem record, respectively. o The installation program not only provides the option to select a virtual web site to use when installing ProblemTracker, but also now provides an option to specify which host name (or IP address) and port number to use for the Start menu shortcuts it creates for browsing to WMS and the pteval (default) workgroup. This can be useful if your (virtual) web site is configured to respond to multiple host names, IP addresses, or port numbers. o The values which you specify for host name (or IP address) and port number are now automatically used as the default values for creating new workgroups from WMS (until/unless you set new default values). o An option has been added to the Workgroup Management System (WMS) to allow users to notify WMS that you have changed the password for the ProblemTracker anonymous user (PUSR4). This allows WMS to properly create, repair, upgrade, or move Problem- Tracker workgroups after you have changed the anonymous user password (in Windows User Manager). o If upgrading from Version 3 to Version 4, WMS will now default to the Web Site where Version 3 files were installed. As in prior versions, it always defaulted to the Default Web Site. o The following Help sections have new information added: User's Guide: Operations: Logging In Administration Guide: Setup: Preparation for Installing ProblemTracker Administration Guide: Customizing Workflow Workgroup Management System Guide: Introduction: Adding a Workgroup 9.2 Fixes --------- o When performing the Task operation on a record in previous versions, the user assigned to a problem record would not be displayed in the Assigned To pulldown. When a transition was set to use "Assign to a User Group" and the user group only had one member who was also the assignee for a problem record, a system error would result because no users were displayed in the Assigned To field under these conditions. This has now been resolved such that the user assigned to the problem record will be displayed in the Assigned To field. o In previous versions, when the component of a RelNum type field other than the first one (e.g. RelNumxxb, RelNumxxc, etc.) was deleted, the user was not prompted to select a replacement for any obsolete values in the database. This has been fixed such that the user is prompted to select a replacement for the obsolete values. o In Version 4.0, if a group name or a state name contained a double quote character, system errors would be generated when modifying email notification rules and workflow properties. This has been fixed to support the use of double quotes in group or state names. o In Version 4.0, if a user group or user id was changed, any advanced or standard saved queries referencing a user group or user id were not updated to reflect these changes. This has been corrected such that advanced and standard saved queries are updated when a user group or user id is modified. o When using Netscape 6 with Version 4.0, the double click operation was not working to select a project in the Associate Source Code page. This has been corrected to support double clicking on this page. o When upgrading from a ProblemTracker 3 installation which uses a virtual web site at a port other than 80 (the default for web servers), the shortcuts to upgraded workgroups (from the WMS Home page) did not work correctly. This has been fixed. o When upgrading from Version 3 to Version 4.0, any attachment files in the upgraded database would still reference a URL pointing to the Version 3 workgroup. If redirection was not used (there was no alias from the old name to the new workgroup name) a "Page not found" error would be displayed when attempting to view any attachment added before the upgrade. This has been fixed so that the upgrade process will change the URL to reference the Version 4 workgroup name. o When upgrading from a Version 3 installation which uses an Access database on systems where the database name was referenced using upper case (BUGTRACK.MDB), an error was generated and the upgrade could not proceed. This has been fixed. o When upgrading the data from Version 3 to Version 4 on some older systems, it was possible to reach the script timeout during the upgrade. The script timeout has now been increased to 30 minutes for the upgrade operation. o When installing on a machine with the Windows password complexity requirement enabled an error was generated and the ProblemTracker anonymous user (PUSR4) was not created. This was because the password which was generated did not always meet the password complexity requirement. The (default) password which is created for the ProblemTracker anonymous user (PUSR4) now meets the complexity & minimum length requirements if they are enabled. o In Version 4, when a web server had more than one web site configured, the Web Site Name pulldown menu in the Workgroup Management System would display "unknown" as a Web Site Name (however, it would still include all actual web site names). This extra (invalid) entry has been removed from the display. o In Version 4, the URL configured for each workgroup by the Workgroup Management System would be based on the hostname of the web server machine. This configuration could result in the wrong URL for systems that use a different host name (e.g. multiple virtual web sites differentiated by host header value). This has been changed to allow users to enter a different hostname, or IP address, and port number for each workgroup. o When using the Workgroup Management system to edit a database name or password, the change would not immediately take effect because the web server was still using the old information. This has been fixed such that the web server application for the workgroup is re-loaded after a database name or password change so that the new values will be used immediately. o In Version 4.0, a new workgroup could be added in the Workgroup Management System with the name "ptadmin". This has been changed such that "ptadmin" cannot be used as a name for a workgroup so that it does not conflict with the Workgroup Management System. o In previous versions, the export operation would silently fail when there was not sufficient file permissions to allow the export folder to be created. This has been fixed to set the appropriate permissions during installation as well as prompt with a detailed error if the permissions are not sufficient when the export operation is used. o When upgrading a database from Version 3.0.5 to Version 4.0, a system error was generated. This has been fixed. ============================================================= 10.0 Changes in ProblemTracker Version 4.0 ============================================================= 10.1 Enhancements ---------------- o Source Code Control has been integrated into ProblemTracker. Source code files can be associated to a problem record. In addition, difference and history functions are available to compare archived versions of source code files. o Unlimited Workgroup Support has been automated. Workgroups can now be installed, modified, or removed using a central interface called the Workgroup Management System. o An Advanced Query section has been added to allow building of complex queries. Various operators such as "AND", "OR", and "NOT" are available to create queries that include and / or exclude multiple options within each field. o Multinationalization has been added to allow ProblemTracker to support virtually all languages within a single workgroup (even within a single problem report) at the same time. Multinationalization can represent any language whose characters are represented by the UTF-8 (Unicode) character set (international language standard). o Controlled Branching has been implemented as a workflow enhancement. This option allows definition of multiple transitions from a particular state along with task fields for each transition. o The option "Restrict Task Operation to Current Assignee" has been implemented and can be found on the General Preferences page in the Admin section. This will prevent users from marking a task complete on a record to which they are not assigned. o A Default Add State for each product can now be configured within workflow, allowing newly added problem records to be routed to more than one possible state. o Email notification has been expanded to allow notification to be sent when a problem record is edited or tasked. In addition, email notification options have been expanded such that the original reporter of the problem report as well as User Groups can receive notification email messages. o Personal Preferences can now be found by clicking on the link on the Home Page (previously these preferences were found directly on the Home Page). o The date values in ProblemTracker have been changed from a string value to a date data type. This will allow the date values to be independent of language settings. This will also allow users to configure their own Date and Time preferences in the Personal Preferences section irrespective of the settings on the server where ProblemTracker is installed. o Users may now configure the maximum number of records per page for query results in the Query and Home pages. The default setting is 20 records per page and the maximum setting is 60 records per page. This setting can also be configured at the database level in the Admin / General Preferences page. o The default URL for the ProblemTracker login page is now http://servername/workgroup/ptlogin.asp where servername is the TCP/IP name of the server where ProblemTracker is installed and workgroup is ptdev, ptweb, ptdev2, etc. Previously, this URL was http://servername/workgroup/ptlogin.htm. o The default URL for the ProblemTracker customer bug page is now http://servername/workgroup/Internet/user_add.asp where servername is the TCP/IP name of the server where ProblemTracker is installed and workgroup is ptdev, ptweb, ptdev2, etc. Previously, this URL was http://servername/workgroup/Internet/user_add.htm. o The Database Tools section has been moved from the Admin section to the Workgroup Management System. o The Upgrade operation has been moved from the Admin section to the Workgroup Database Tools section. o Workgroups can now be blocked (and subsequently unblocked) via the Workgroup Management System to prevent users from accessing ProblemTracker during maintenance or troubleshooting. o In previous versions, connections to the ProblemTracker databases were managed using ODBC Datasource names. ProblemTracker has been changed to use OLE-DB for connecting to the ProblemTracker databases. o The options Attachments and Source Code Files have been added as options for fields in Report Layouts. o The following User Group privileges have been added in this release: View Fields View Attachments View Source Code List View Record History Edit Fields Edit Attachments Edit Source Code List o The ProblemTracker installation set up program will check the web site selected to see if there is a port number specified (other than the default) and update the shortcuts accordingly. For example, if the default web site is set to use port 8500, the shortcut for the Workgroup Management System will be saved as http://servername:8500/ptadmin/uwslogin.asp. o A Format for Printing option has been added to the View page. o Default Home Queries have been added as saved queries. "Assigned to Me" is the query that this displayed as the top report on a user's home page. "Reported by Me" is the query that is displayed as the second report on a user's home page. o Default Report Layouts have been added for the Home Page reports. Home Report1 is the layout used by the "Assigned to Me" report (the report displayed at the top of a user's home page). Home Report2 is the layout used by the "Reported by Me" report (the report displayed at the bottom of a user's home page). o The ability to query by user group has been added. In the Assigned To and Reported By fields on the query and advanced query pages, user groups can be selected as criteria. User groups are denoted in these pulldown menus as [User Group]. o When a user who is still the assignee for Problem records is deleted from ProblemTracker through the User Administration section, a list of active users will be displayed so that a new assignee can be selected for these records. o The default timeout for users to be automatically logged out of ProblemTracker is 12 hours. This timeout can be adjusted to a different setting via IIS. o The installation set up program now creates a Local Windows User Account as a member of the "Guests" group on the machine where ProblemTracker is installed for use with the workgroups created by the Workgroup Management System. This user will be created with the name "PUSR4" where is the TCP/IP name of the machine where ProblemTracker is installed. The installation set up program will also configure this user as the IIS anonymous user for access to the workgroup and as the Component Services (MTS Explorer on NT 4.0) Identity for each workgroup package. This allows you to explicitly enable or disable access to files (or other system resources) for unauthenticated users of ProblemTracker (rather than for all IIS anonymous users in general). In previous versions, the default IIS anonymous user IUSR_ was used for such access the ProblemTracker workgroups. o The "Query Groups" option has been renamed to "State Groups". The function or operation of this option remains the same as previous versions. o The Default Assignee column and the corresponding "Default" buttons have been removed from the User Administration section. Default assignments should be handled using the "Workflow Properties" page in the "Define Workflow" Administration section. o A utility to clean up Date formats within a ProblemTracker database has been added. Users who have a database with more than one date format in use will need to use this utility to complete the upgrade process to Version 4.0. o The Help document has been split into 3 guides: User's Guide, Administrator's Guide, and Workgroup Management System Guide. These Help guides can be accessed on the machine where ProblemTracker is installed by going to Start -> Programs -> NetResults ProblemTracker 4 -> Help Library These guides can also be accessed within the Workgroup Management System and each workgroup, respectively. o The following Help section have had new information added. New sections are marked with (*): Introduction: Glossary of Terms Setup: Preparation for Installing ProblemTracker Setup: Using Oracle 8i (or later) Database (*) User's Guide: Operations: Logging In User's Guide: Operations: Advanced Queries (*) User's Guide: Operations: Viewing Records User's Guide: Operations: Editing Records User's Guide: Operations: Source Code Control (*) User's Guide: Operations: Marking a Task Complete User's Guide: Operations: Printing Records Administration Guide: Overview Administration Guide: General Preferences Administration Guide: User Administration: Privileges Administration Guide: Customizing the Data Record Administration Guide: Customizing Workflow Administration Guide: Email Administration: General Email Configuration Administration Guide: Email Administration: Email Notification Preferences Administration Guide: Source Code Control Integration: Overview and Requirements (*) Administration Guide: Source Code Control Integration: Enabling Source Code Control Integration (*) Administration Guide: Customer Bug Page Administration Guide: Database Administration Administration Guide: Supporting Multiple Projects (Workgroup Administration): Overview (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Logging In (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Adding a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Editing a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Viewing a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Deleting a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Managing Aliases (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Moving a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Migrating a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Repairing a Workgroup (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): User Administration (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Logging Workgroup Information (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Viewing Global Information (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Blocking and Unblocking Workgroups (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Managing Web Server Security (*) Administration Guide: Supporting Multiple Projects (Workgroup Administration): Upgrading Workgroups (*) 10.2 Fixes --------- o When specifying a Date range in the Query page in previous versions, if a valid date was typed in the "Before" field, an invalid date could be typed in the "After" field without generating an error. This has been fixed so that both fields are validated when attempting to run a query. o When specifying a Date range in the Query page while using an Access database in previous versions, if a date using "." as the delimiter was typed in the "Before" and / or "After" fields, a System Error would be generated. This has been corrected such that the results are displayed without an error. o When specifying a Date for a chart calculation in the Summary page while using "." as the date delimiter in an Access database in previous versions, a System Error would be generated when attempting to generate the chart. This has been corrected such that the chart is displayed without an error. o When using Netscape 4.7 and attempting to run a History query using a PRN number, the user is not prompted to select a comparison operator (<,>, or =). This has been corrected such that a comparison operator must be selected when using the PRN field for a History Query. o When a running a History query with the dd/mm/yyyy date format selected, the results were not being sorted in chronological order because the dd (day) portion of the date field was being used to sort instead of the mm (month) portion of the date field. This has been corrected such that the results of the history query are sorted in chronological order when using the dd/mm/yyyy date format. o When using the "Format for Printing" option in previous versions, the query title would change to "Query Results for Product: All" instead of displaying the Product selected. This has been corrected to allow the title to display the correct product name. o When using a pipe character | (or vertical bar) in the name of a pulldown menu option in previous versions with an older set of Access drivers installed, a syntax error message would result. This is no longer an issue in the latest version as newer Access drivers allow use of the pipe character within pulldown options. o When using a comma as part of a user group name and selecting this group in the "Make Visible to These User Groups" field on the Add page, the user group would be saved as two user groups in previous versions. This has been corrected to allow a user group name with a comma to be displayed correctly. o In previous versions, in some cases using embedded curly braces within a text field would result in a system error. Curly braces can now be used within a text field. o In previous versions, a database error was generated when "." was used alone in a floating type field. Now, if "." is typed alone in a floating field, the user is prompted to enter a valid value without generating a database error. o In versions 3.6 and 3.6.1, if you had auto login enabled and a previous session still active while trying to login through another browser, the login would fail due to the previous session. If you then selected "No" to cancel your login attempt, no action would result. This has been corrected such that you will return to the login page when selecting "no" under the circumstances described above. o In previous versions, after using the edit, task, or view operations from a list of query results, then attempting to return to the query results, the user would return to the first page of query results. This has been corrected to allow a user to return to the same query results instead of being sent to the first one by default. o In previous versions, state names with double quotes were not displayed in a Summary chart. This has been changed so that state names with double quotes are displayed correctly within Summary charts. o In version 3.6.1, when adding Pulldown12 to the schema in the ptweb workgroup, the system would go to the User Administration page. This has been corrected so that Pulldown12 could be added correctly. Support ------- Support information is available in the ProblemTracker online help. Click on the Help icon after logging into ProblemTracker. Or, from the machine on which ProblemTracker is installed, select Start->Programs->NetResults ProblemTracker->ProblemTracker Help. Then scroll down to the Support section near the bottom of the table of contents. Support is also available on the NetResults web site. Browse to http://www.problemtracker.com , then click on the Support button (on top of web page), then click on the appropriate link in the Support menu. And, if you are evaluating the product or have a current support agreement with NetResults, support is available via e-mail on business days (Monday through Friday, excluding holidays) from 5am to 5pm Pacific. Additional support options (e.g. phone support, extended hours) may be purchased (send e-mail to sales@n2r6.com or browse our web site in the ProblemTracker product info section for information on additional support options). Support email should be sent to the following address. pt_support@netresultscorp.com When reporting a bug, please include any information displayed on the screen regarding the problem. In many cases if you get a generic database error message, you can scroll further down on the page to find more detailed error information. Please provide the required information listed at the following page to help us assist you as quickly as possible: http://www.problemtracker.com/pt_support.html