README.TXT Release Notes for NetResults ProblemTracker Version 4.0.3 © 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.0.3 **************************************************************** 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 are in section 2.0. Upgrade instructions for users of 3.05 - 3.6.1 are in section 3.0. And, upgrade instructions for users of 3.0 - 3.04 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 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, or Windows 2000 Server (Windows 2000 Server recommended) 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 ============================================= 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.0 - 4.0.2 to ProblemTracker Version 4.0.3 ============================================================================================= 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.0.3 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.0.3. To do this, login to the web server machine as Administrator and then run (double-click from Windows Explorer) pbtrk403.exe. 5. Login to the Workgroup Management System (WMS) by going to Start->Programs->NetResults ProblemTracker 4->Workgroup Management System->Login Page You must use the Repair operation to update the files for each of your workgroups. To do this, click on the repair icon on the Button bar. Select a workgroup name from the pulldown menu, then click on the Repair button below the pulldown menu. A confirmation page will be displayed. Click on the Repair Workgroup button, then click OK to proceed. Click OK after the repair operation has completed. 6. Perform step 5 for each workgroup in the Workgroup Management System. 7. If you are upgrading from 4.0 or 4.0.1, then for each workgroup do the following. Skip this step if you are upgrading from 4.0.2. a) Login to the workgroup as Admin by browsing to http://servername/workgroup and entering Admin as the username. b) Click on the Admin icon in the button bar. c) Click on the Maintenance button in the Admin page. d) Click on the "Apply DB Updates" button in the maintenance page. This will apply (if necessary) all database updates from the 4.0 A patch through 4.0.2. This operation is safe to run multiple times, so if you are unsure as to whether or not to run it (perhaps you did not run it when first upgrading to 4.0.2) you should perform this operation. e) After the message "Operation Complete" appears in the status bar, click the Logoff icon in the button bar. 8. Reactivate your anti-virus software and re-start IIS services. Your system is now upgraded to ProblemTracker 4.0.3 for all workgroups. ============================================================================================= 3.0 Upgrading from ProblemTracker Version 3.0.5 - 3.6.1 to ProblemTracker Version 4.0.3 ============================================================================================= 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.0.3 on the same machine where you have ProblemTracker 3 installed. If you are installing ProblemTracker Version 4.0.3 on a different machine than where you have ProblemTracker 3 installed, please review the following FAQ entry for instructions: http://www.netresultscorp.com/pt_faq_howdoi.htm#moveupgrade40 5. If you have previously installed a ProblemTracker 4.0 Preview Release on your machine, you will need to delete all workgroups within a ProblemTracker Version 4.0 Preview Release through the Workgroup Management System, then uninstall the ProblemTracker Version 4.0 Preview Release before you can install ProblemTracker Version 4.0.3. To delete the workgroups that you have in a ProblemTracker Version 4.0 Preview Release, login to the Workgroup Management System by going to Start / Programs / NetResults ProblemTracker 4 / Workgroup Management System / Login Page. For each workgroup, click on the delete icon to the left of the workgroup name on the Workgroup Management System Home Page. On the next page, click on the Delete Workgroup button, then click OK to confirm this action. Once all workgroups have been deleted, logout of the Workgroup Management System. Uninstall the ProblemTracker Version 4.0 Preview Release by going to Start / Programs / NetResults ProblemTracker 4 / Repair-Uninstall. Select the "Remove" option. Then, select the option to "Remove components and databases". After the uninstallation has been completed, proceed to the next steps. 6. Install ProblemTracker Version 4.0.3. To do this, login to the web server machine as Administrator and then run (double-click from Windows Explorer) pbtrk403.exe. Enter your license key(s) information by going to Start->Programs->NetResults ProblemTracker 4->NetResults License Manager 7. 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.0", then click on the Continue button. 8. 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. 9. In the New Workgroup details section, enter information for the new workgroup including Workgroup Name, Description, Location, template, 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. 10. 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 Continue button to complete the Upgrade operation. Click OK to confirm. A message confirming that the upgrade was successful will be displayed. 11. Go back to the Workgroup Management System and click on the Home icon in the button bar. The upgraded workgroup will now appear on the list on the Home Page. Click on the Workgroup Database Tools icon to the left of the workgroup name from the list on the Home page. A separate window will launch to show the Workgroup Database Tools page. Scroll down to find the button labeled "Upgrade to 4.0". Click on this button, click OK to confirm the action, then click OK after the operation is successful. 12. 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. 13. Repeat steps 6 - 11 for each workgroup you wish to upgrade to ProblemTracker 4. 14. Login to each workgroup to confirm that the upgrade was successful. 15. There are significant changes to the way your Version 3 data will be represented after upgrading to Version 4.0.3. Please review the details at: http://www.netresultscorp.com/pt_40information.html#upgrade 16. After upgrading all the workgroups to Version 4, login to each of the workgroup 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.0.3 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. 17. Now you have successfully upgraded to ProblemTracker 4.0.3. 18. Reactivate your anti-virus software. ============================================================================================= 4.0 Upgrading from ProblemTracker Version 3.0 - 3.0.4 to ProblemTracker Version 4.0.3 ============================================================================================= 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.0.3 on the same machine where you have ProblemTracker 3 installed. If you are installing ProblemTracker Version 4.0.3 on a different machine from where ProblemTracker 3 is installed, please review the following FAQ entry for instructions: http://www.netresultscorp.com/pt_faq_howdoi.htm#moveupgrade40 5. If you have previously installed a ProblemTracker 4.0 Preview Release on your machine, you will need to delete all workgroups within a ProblemTracker Version 4.0 Preview Release through the Workgroup Management System, then uninstall the ProblemTracker Version 4.0 Preview Release before you can install ProblemTracker Version 4.0.3. To delete the workgroups that you have in a ProblemTracker Version 4.0 Preview Release, login to the Workgroup Management System by going to Start / Programs / NetResults ProblemTracker 4 / Workgroup Management System / Login Page. For each workgroup, click on the delete icon to the left of the workgroup name on the Workgroup Management System Home Page. On the next page, click on the Delete Workgroup button, then click OK to confirm this action. Once all workgroups have been deleted, logout of the Workgroup Management System. Uninstall the ProblemTracker Version 4.0 Preview Release by going to Start / Programs / NetResults ProblemTracker 4 / Repair-Uninstall. Select the "Remove" option. Then, select the option to "Remove components and databases". After the uninstallation has been completed, proceed to the next steps. 6. Install ProblemTracker Version 4.0.3. To do this, login to the web server machine as Administrator and then run (double-click from Windows Explorer) pbtrk403.exe. Enter your license key(s) information by going to Start->Programs->NetResults ProblemTracker 4->NetResults License Manager 7. 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.0", then click on the Continue button. 8. 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. 9. In the New Workgroup details section, enter information for the new workgroup including Workgroup Name, Description, Location, template, 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. 10. 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 Continue button to complete the Upgrade operation. Click OK to confirm. A message confirming that the upgrade was successful will be displayed. 11. Click on the Home icon in the button bar. The upgraded workgroup will now appear on the list on the Home Page of the Workgroup Management System. Click on the Workgroup Database Tools icon to the left of the workgroup name from the list on the Home page. A separate window will launch to show the Workgroup Database Tools page. Scroll down to find the button labeled "Upgrade to 3.0.5". Click on this button, click OK to confirm the action, then click OK after the operation is successful. Then, click on the button labeled "Upgrade to 4.0", click OK to confirm, then click OK after the operation is successful. 12. 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. 13. Login to the workgroup. 14. For each Date field that appears in the "In Use" list (the one on the left side), select it, then click on the "Remove >>" button, then after it appears in the "Not In Use" list click on the "<< Add" button. 15. Repeat steps 6 - 13 for each workgroup you wish to upgrade to ProblemTracker 4.0.3. 16. There are significant changes to the way your Version 3 data will be represented after upgrading to Version 4.0.3. Please review the details at: http://www.netresultscorp.com/pt_40information.html#upgrade 17. After upgrading all the workgroups to Version 4, login to each of the workgroup 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.0.3 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. 18. Now you have successfully upgraded to ProblemTracker 4.0.3. 19. Reactivate your anti-virus software. ============================================================= 5.0 Changes in ProblemTracker Version 4.0.3 ============================================================= 5.1 Enhancements ---------------- There are no enhancements in release 4.0.3. This release only contains fixes. 5.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. ============================================================= 6.0 Changes in ProblemTracker Version 4.0.2 ============================================================= 6.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). 6.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. ============================================================= 7.0 Changes in ProblemTracker Version 4.0.1 ============================================================= 7.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 7.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. ============================================================= 8.0 Changes in ProblemTracker Version 4.0 ============================================================= 8.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 (*) 8.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. ============================================================= 9.0 Changes in ProblemTracker 3.6.1 ============================================================= 9.1 Enhancements ---------------- o The following Help sections have had new information added: User's Guide: Operations: Deleting Records Administration Guide: User Administration: Users Administration Guide: User Administration: Privileges Administration Guide: Customizing the Data Record Administration Guide: Customizing Menu Values Administration Guide: Customizing Workflow Administration Guide: Customer Bug Page 9.2 Fixes --------- o In the Edit page, the options for the Status pulldown were not sorted in alphabetical order as they are in the Add, Task, and other pages. This has been fixed so that the options in the Status pulldown are sorted alphabetically on all pages. o Customers who have added their own custom HTML to the Customer Bug Page (through the Inet Page Options section of Admin) and use the variable "i" or "j" in their HTML, may have encountered a JavaScript error while using Internet Explorer as their browser when trying to submit a problem report through this page. This has been fixed to allow the variables "i" or "j" to be used in the custom HTML without generating a JavaScript error. o While using ProblemTracker 3.5 or later with some SQL Server 7.0 systems, users running a query that sorted by PRN in descending order as the primary (left-most) sort order field would receive query results displaying one record per page rather than up to 20 per page. This appears to be a defect in certain SQL Server 7.0 systems (though not all). A code workaround has been added so that this function works correctly (displaying up to 20 records per system) on all SQL Server 7.0 systems. o While using ProblemTracker 3.6 (only), when tasking a record which has "Product" (field type = Product) and "Assigned To" (field type = Assignee) as Task Fields, ProblemTracker would incorrectly assign the record to the State Manager for the next state instead of the user selected in the "Assigned To" field. This has been fixed so that the record will be assigned to the user selected in the "Assigned To" field during the Task operation. o In versions 3.1.4 or later, the ProblemTracker installation utility would automatically configure the web server anonymous user for ProblemTracker directories to IUSR_HostName on the local machine (machine on which IIS 4.0 or IIS 5.0 is installed) as that is the anonymous user which is configured for use by IIS when it is first installed on most systems. However, in some environments, the anonymous user being used is a domain level user (Domain\IUSR_HostName) rather than a local user (IUSR_HostName). The installation utility now configures new workgroup installations to inherit the anonymous user from the parent directory configuration to automatically preserve any configuration created by your web site administrator after the IIS installation. This change will not affect existing workgroups (those you are just upgrading). ============================================================= 10.0 Changes in ProblemTracker 3.6 ============================================================= 10.1 Enhancements ---------------- o Floating license support has been added. - In addition to your existing static licenses (one license per user account), you can now purchase additional floating licenses for use by infrequent users of ProblemTracker. As with static licenses, each floating license allows one user to access (login to) ProblemTracker; however, you may create up to ten user accounts per floating license. With floating licenses you can allow infrequent users of the system to "share" your floating licenses. - If you have both types of licenses, you can use User Administration to configure which users have a static license (so they can always login to the system) and which users must share your floating licenses. This configuration may be changed at any time (within the limits of the number of licenses of each type you have purchased). - The ProblemTracker License Manager tool now allows you to enter both types of licenses. Your existing (static) licenses will be displayed in the License Key 1 field. Any new floating licenses you purchase will be entered and displayed in the License Key 2 field. o User sessions (logins) are now displayed. A new administrative function (User Sessions) displays a list of active logins (sessions where the user has not logged off). It can also be used to terminate a session (logoff the user) if it is no longer in use or if you must perform a maintenance operation with no active users. To get the most benefit from this new feature, we recommend that you remind your users to click the Logoff button to end their session (simply browsing to another web site or exiting their browser will not end their session). o The (most recent) History Comment is now included in the email notification message associated with a change in status, change of owner (assignee), and deletion of a record (all but the Add operation). So, if users choose to include a reason for a change in the History Comment which is displayed at the top of the Edit/Task/Delete page, it will be included in the associated email message. o The following Help sections have been added or have had significant new information added (sections with a * are new). Introduction:Glossary (*) Setup:Entering License Information User's Guide:Operations:Logging In User's Guide:Operations:Querying Records User's Guide:Operations:Printing Records (*) Administration Guide:User Administration:Users Administration Guide:User Administration:User Sessions (*) o The display length of the attachment field has been shortened so that the browse button (which most browsers display to the right of the field) will be easier to find for users with low resolution displays. The maximum actual length of the file path for file attachments remains the same (254 characters). o Home page queries have been streamlined to improve performance for systems with large numbers of problem records. o Access template databases now include a warning which is displayed to any user who opens the database using Microsoft Access. The warning reminds users that direct database edits are not supported (as they bypass constraints enforced by ProblemTracker web pages and will corrupt the database). 10.2 Fixes --------- o An option (pulldown) menu value with the name "None" can now be deleted as long as it is not the default value for the option menu (as there must always be a default). This also applies to option menu values that were originally named None when the system was first installed, but were subsequently renamed. To delete any of these values, login as Admin, click on the Admin icon, click on Option Menus, click Edit Items, then click the (now visible) Delete button next to the option menu value. o After migration from Access to SQL Server, some Internet Explorer users who had disabled persistent cookies at some point after using ProblemTracker, but before the migration to SQL Server, got error messages when attempting to use the View function (or some Query functions) until they enabled persistent cookies. This has been fixed. o If a user has no first name, then the display for Assigned To under "Records matching..." section of the Summary page will not default to "*", instead it defaults to the user with no first name. This has been fixed such that "*" is always at the top of the list when you first click the Summary icon. o When Product is a Task Field, ProblemTracker did not recognize the change in Product when it assigned the record to the State Manager during the Task operation (if State Manager was indicated in the "Assign to on Next" property of the state in Define Workflow). This has been fixed. ============================================================= 11.0 Changes in ProblemTracker 3.5.1 ============================================================= 11.1 Enhancements ---------------- o The Inet Page (Customer Bug Page) now displays the problem record number (PRN) on the pages that confirms that a record has been added. o Additional information has been added to the following Help sections: Preparation for Installing ProblemTracker located in Setup; Adding Records (attachments section) and Record Attachments in the User's Guide; and Security Model and Privileges in the Administration Guide. o Rather than displaying an error for requesting data from dates in the future, the Summary function (charts & graphs) just doesn't display values for dates beyond today. Only if all dates requested are beyond today (e.g. the start date is in the future) will it display an error message. o If there is an error connecting to the database while processing a Summary (charts & graph) request, more detailed error information is now displayed. 11.2 Fixes --------- o Override Record-Level Security (user group) privilege did not work on the Home, Query results, and Task pages (it was as if the user did not have the privilege on those pages). Now it is functional for all pages. o When a user with Add Attachment via Add Page privilege added a new problem report using a Netscape browser, if they did not actually include an attachment, the status message would state "Add Attachment failed" (even though no attempt was made to add an attachment). This has been fixed. o If a there was an error adding a file attachment from the Add page, the specific error was not displayed (e.g. "Access Denied" was not displayed). The new version will display error details if a file attachment was not added in the Status bar. o Installation on a system using Internet Information Server (IIS) where the (virtual) web site that was used for Problem- Tracker was configured to disable anonymous authentication resulted in authentication errors when attempting to browse to ProblemTracker. The new installation program automatically configures anonymous authentication for (and only for) ProblemTracker virtual directories. Security can be added later either by using IP address filtering or SSL (https) encryption via the web server and/or by configuring the system according to the Web Server Security section of the Setup manual in the ProblemTracker Help. o Installation on a system with an older version of Internet Information Server (IIS) that is no longer supported (IIS 3.0 or prior), could result in a misleading error message if a user selected IIS 4.0 or IIS 5.0 as their browser (both of those are supported). If IIS 4.0 or IIS 5.0 was selected on a system with IIS 3.0 or prior, the messages state that Netscape had been detected, but IIS had not. The message has been updated to provide a more detailed explanation of the situation. ============================================================= 12.0 New Features and Changes in ProblemTracker 3.5 ============================================================= o Charts and Graphs, beta Release 1 Interactive Bar Charts, Pie Charts, and Line Charts of various statistics gathered using problem records and record history are now available as a part of the Summary operation. o Query results are now paged (20 per page). o Old records can now be selectively deleted (purged) from the database in a single operation (all records matching a query may be deleted). o All records (and associated record history) may be permanently removed (to restart with new records, but save existing configuration such as workflow, users, problem record definition, etc.). o An attachment can be added directly from the Add page (along with the problem report itself). Available to users who are members of a user group with the new Add Attachment privilege. Upgraded systems will have this privilege off for all groups except for Admins. o An attachment can be added directly from the Inet Page (Customer Bug Page). Available if the new Add Attachment option is checked in the Inet Page Options page in the Admin section. By default this is turned off for upgraded systems. o A user group may be given the new Override Record- Level Security privilege to allow members of the user group to view all records irrespective of their record visibility/security settings. This can be useful for environments where Record-Level Security is used to keep "external" users from viewing each others' records, but where "internal" users should be able to easily view all records. o Sort order (ascending vs. descending) may be specified for each individual sort field in a Query. o A special user name "LoginUser" may be used in the query page when specifying Assignee or Reporter. If it is used then when the query is actually run, the value will be the user who is logged in. This can be especially useful for defining a single Home query (at the "Users" User Group level) for all users in the system. o The number of pulldown menus has been increased from 10 to 20. So you can configure up to 20 pulldown menus in a single problem record. o Adding or removing large numbers of users from a User Group has been simplified. Simply click the Users button next to a User Group, then select the users to be added or removed and click an add or remove button. o Added more automated configuration via the installation program. o SQL Server 6.5 is no longer supported for new installations; however, ProblemTracker 3.5 will work with existing (upgraded) SQL Server 6.5 installations (those at Service Pack 2 or higher). o Fixed installation program defects related to sites with large numbers of virtual directories, reinstall after a failed uninstall, certain types of WSH installations, and file system permissions. o Fixed disabled Cancel button at the bottom of Edit Result Set page for Netscape Navigator. o Fixed defects related to use of a case sensitive SQL Server installation. o Fixed defect related to name change of a user that was defined as Assigned To on Next or Assigned To on Previous for one or more states. o Various Help page updates, including a fix for the instructions regarding adding workgroups beyond 5 (the workgroups that are installed using the installation program). 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 ProblemTracker section (left side of web page). 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. Also, please locate the file named webdb_errors.txt in the ptcgi directory and send its contents (if the file exists).