README.TXT Release Notes for NetResults ProblemTracker Version 3.6.1 © Copyright 1997-2001 NetResults Corporation, All Rights Reserved. NetResults is a registered trademark of NetResults Corporation. ProblemTracker is a trademark of NetResults Corporation. **************************************************************** Release Notes for Version 3.6.1 **************************************************************** Upgrade Instructions -------------------- You can upgrade any installation of ProblemTracker 3.0 or later to this version by installing this directly over your existing installation. However, please make sure you reply "No" (the default) if you are asked whether or not to overwrite your existing database. If you are currently using a version prior to 3.6, you will need to follow the instructions in section 2 or 3 to upgrade your data. 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. ================================================================ 1.0 Backing up your active database ================================================================ Prior to any upgrade operation, please be sure to backup your existing database environment. 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 "C:\Netscape\SuiteSpot\Docs" for Netscape Enterprise 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 "C:\Netscape\SuiteSpot\Docs" for Netscape Enterprise 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 Users ========================= 1. You may backup SQL Server 7.0/2000 databas(es) by using SQL Server's backup or data export operation. Backups may done to a hard disk as well as to tape. Please review your SQL Server documentation for further information. The database(s) to backup include one or more of the following: ptdev, ptdev2, ptdev3, ptdev4, ptweb. It is REQUIRED that you either copy the database file(s) to a safe place (Access only) or perform a backup (SQL Server or Access). UNDER NO CIRCUMSTANCES IS NETRESULTS RESPONSIBLE FOR THE LOSS OF ANY DATA AS THE RESULT OF THE UPGRADE PROCESS. ================================================================= 2.0 Upgrading ProblemTracker 3.6 to ProblemTracker 3.6.1 ================================================================= 1. Backup your existing ProblemTracker database (see section 1.0). 2. Install ProblemTracker 3.6.1. To do this, login to the web server machine on which ProblemTracker is installed as Administrator and then run (double-click from Windows Explorer) pbtrk361.exe. Your system is now upgraded to ProblemTracker 3.6.1 for all workgroups supported by the installation program. The installation program currently supports up to five workgroups: Software Development - ptdev, Web Development - ptweb, and Additional Software Development 2,3,4 - ptdev2,ptdev3,ptdev4. If you have manually added any workgroups beyond the five supported by the installation program, please follow the instructions on our web site at http://www.NetResultsCorp.com/pt_upgrade_extra_wgs.html to upgrade those workgroups now. ================================================================= 3.0 Upgrading ProblemTracker 3.1.4 - 3.5.1 to ProblemTracker 3.6.1 ================================================================= 1. Backup your existing ProblemTracker database (see section 1.0). 2. Install ProblemTracker 3.6.1. To do this, login to the web server machine on which ProblemTracker is installed as Administrator and then run (double-click from Windows Explorer) pbtrk361.exe. 3. Login to ProblemTracker as Admin (default password is Admin). You should be notified that a database upgrade is required and will be sent to the Database Maintenance page. If you do not receive this notification, please do the following: 1) Click on "Admin" in the navigation bar. 2) Click on the "Maintenance" button. 4. Click on the "Upgrade to 3.6" button. 5. Repeat the steps 2-4 for every ProblemTracker workgroup you wish to upgrade (i.e. ptdev,ptweb,ptdev2,ptdev3,ptdev4). Your system is now upgraded to ProblemTracker 3.6.1 for all workgroups supported by the installation program. The installation program currently supports up to five workgroups: Software Development - ptdev, Web Development - ptweb, and Additional Software Development 2,3,4 - ptdev2,ptdev3,ptdev4. If you have manually added any workgroups beyond the five supported by the installation program, please follow the instructions on our web site at http://www.NetResultsCorp.com/pt_upgrade_extra_wgs.html to upgrade those workgroups now. ================================================================= 4.0 Upgrading ProblemTracker 3.05 - 3.1.3 to ProblemTracker 3.6.1 ================================================================= 1. Backup your existing ProblemTracker database (see section 1.0). 2. Install ProblemTracker 3.6.1. To do this, login to the web server machine on which ProblemTracker is installed as Administrator and then run (double-click from Windows Explorer) pbtrk361.exe. Make sure you install the same workgroups as your previous installation (Software Development = ptdev, Web Development = ptweb, Additional Workgroups are ptdev2, ptdev3, and ptdev4). Make sure you reply "No" if you are prompted to overwrite an existing database. 3. Login to ProblemTracker as Admin (default password is Admin). You should be notified that a database upgrade is required and will be sent to the Database Maintenance page. If you do not receive this notification, please do the following: 1) Click on "Admin" in the navigation bar. 2) Click on the "Maintenance" button. 4. Click on the "Upgrade to 3.6" button. 5. Repeat the steps 2-4 for every ProblemTracker workgroup you wish to upgrade (i.e. ptdev,ptweb,ptdev2,ptdev3,ptdev4). Your system is now upgraded to ProblemTracker 3.6.1 for all workgroups supported by the installation program. The installation program currently supports up to five workgroups: Software Development - ptdev, Web Development - ptweb, and Additional Software Development 2,3,4 - ptdev2,ptdev3,ptdev4. If you have manually added any workgroups beyond the five supported by the installation program, please follow the instructions on our web site at http://www.NetResultsCorp.com/pt_upgrade_extra_wgs.html to upgrade those workgroups now. ================================================================ 5.0 Upgrading ProblemTracker 3.0 - 3.04 to ProblemTracker 3.6.1 ================================================================ ** IMPORTANT UPGRADE NOTE *** If you are upgrading an existing installation of version 3.04 or earlier, please perform the following operation to ensure the ability to properly perform queries using date fields: Disable and then enable all Date fields currently in use as a part of this upgrade procedure: 1. Backup your existing ProblemTracker database (see section 1.0). 2. Install ProblemTracker 3.6.1. To do this, login to the web server machine on which ProblemTracker is installed as Administrator and then run (double-click from Windows Explorer) pbtrk361.exe. Make sure you install the same workgroups as your previous installation (Software Development = ptdev, Web Development = ptweb, Additional Workgroups are ptdev2, ptdev3, and ptdev4). Make sure you click "No" (the default) if asked whether or not to overwrite an existing database. 3. Login to ProblemTracker as Admin (default password is Admin). You should be notified that a database upgrade is required and will be sent to the Database Maintenance page. If you do not receive this notification, please do the following: 1) Click on "Admin" in the navigation bar. 2) Click on the "Maintenance" button. 4. Click on the "Upgrade to 3.05" button. 5. Click on the "Upgrade to 3.6" button. 6. Click on "Admin" in the navigation bar. 7. Click on the Define Schema button 8. 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. 9. Repeat the steps 3-8 for every ProblemTracker workgroup you wish to upgrade (i.e. ptdev,ptweb,ptdev2,ptdev3,ptdev4). Your system is now upgraded to ProblemTracker 3.6.1 for all workgroups supported by the installation program. The installation program currently supports up to five workgroups: Software Development - ptdev, Web Development - ptweb, and Additional Software Development 2,3,4 - ptdev2,ptdev3,ptdev4. If you have manually added any workgroups beyond the five supported by the installation program, please follow the instructions on our web site at http://www.NetResultsCorp.com/pt_upgrade_extra_wgs.html to upgrade those workgroups now. ============================================================= 6.0 Changes in ProblemTracker 3.6.1 ============================================================= 6.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 6.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). ============================================================= 7.0 Changes in ProblemTracker 3.6 ============================================================= 7.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). 7.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. ============================================================= 8.0 Changes in ProblemTracker 3.5.1 ============================================================= 8.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. 8.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. ============================================================= 9.0 New Features and Changes in ProblemTracker 3.5 ============================================================= o Charts and Graphs, Preview 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). ============================================================= 10.0 New Features and Changes in ProblemTracker 3.1.6 ============================================================= o Fixed bug that may intermittently result in an error when attempting to connect to SQL Server systems. The error message includes "Login failed for user '(null)'." Though it could also include something other than (null) as the user. If you are using ProblemTracker 3.1.5 with SQL Server, please upgrade to 3.1.6, as even if this error is not appearing now, it may appear in the future. ============================================================= 11.0 New Features and Changes in ProblemTracker 3.1.5 ============================================================= o Changed the following operations to make it faster to add multiple items (one after the other): - Add User - Add User Group - Add Option (Pulldown) Menu Item - Add (Workflow) State o Verified support for the recently released (general availability version) of SQL Server 2000; although not fully documented yet (should be updated in the next Problem- Tracker release), the system does work with SQL Server 2000. While support for SQL Server 7.0 will continue, SQL Server 6.5 may not be supported in future releases. o Fixed some pages that did not work properly when SQL Server is used in "case-sensitive" mode (by default SQL Server is case insensitive). The fixed pages include some of the pages used in workflow configuration as well as those used to add a file attachment. o Fixed some defects in the new (as of 3.1.4) installation program related to handling international date support and program folder selection. o Updated/added FAQ entries (on NetResults' web site) to document how to move a ProblemTracker installation as well as how to "migrate" from Access to SQL Server. o Added additional information to "System Error" messages (so less information needs to be gathered by the customer to assist in tracking down the cause of the error). o Added some email tracing (to assist in tracking down problems related to sending email). o Fixed bug related to displaying URL fields when the URL field contains certain special characters (typically a form GET URL). ============================================================= 12.0 New Features and Changes in ProblemTracker 3.1.4 ============================================================= o New setup program provides automatic configuration of - IIS 4.0 - IIS 5.0 - ODBC (DSN creation and deletion) - MS Access database - SQL Server 7.0, and 2000 (local and remote) - Windows 2000 and Windows NT 4.0 file system access control lists. o New setup program "Modify" feature allows addition and deleletion of individual workgroups (including automatic configuration of web server, ODBC, SQL Server, and file system access control lists). o New setup program "Repair" feature automatically reinstalls program files (if they are accidentally deleted or modified). o New setup program "Remove" feature allows you to remove all installed files as well as all created databases. Or, you can remove all installed files, but leave databases (to simplify the process of moving to a new web server machine or reconfiguring the existing web server while preserving existing data). o Windows 2000 Server support. o Internet Information Server (IIS) 5.0 support. o Updated Help sections on Setup (all subsections), Saved Queries & Reports, Database Administration, Multiple Project Support (Workgroup Administration), Customer Bug Page, Uninstalling ProblemTracker. o Fixed bug in which the StateGraph function did not operate correctly and presented an error if the non-US date formats are configured. (patch 3.1.3a) o Fixed the following bug. (patch 3.1.3b) If an Admin user deletes a Query Group that is in use in a Saved Query or was the most recently used value for Status the last time a user ran a query (clicked on Run Query in the Query page), then when the Saved Query is run or the user clicks on the Query icon, an error is displayed which includes the following line: Last Query: SELECT * FROM Process WHERE StateName='None' This fix includes an option (number 6) on the Admin Maintenance page which fixes any existing problems after the Query Group has been deleted. It also includes a fix so future Query Group deletes don't cause this problem again. To apply the fix for any existing problems, do the following for each workgroup (ptdev, ptweb, ptdev2, etc.). Login to ProblemTracker as Admin, click on the Admin icon in the navigation bar, click on the Maintenance button, click the GO>> button next to item 6 (Patch 3.1.3b) to repair the existing data. ============================================================= 13.0 New Features and Changes in ProblemTracker 3.1.3 ============================================================= o Modified upgrade procedures to improve compatibility with older Access drivers. o Added "Trial License Period" warning on Home page display. o Updated Help sections on Queries, Saved Queries & Reports, Login, and Support. o Updated description on date range for Date fields in Query page from "On or before" to "before" (which is actually what it does). o Fixed bug which excluded the Default Assignee from appearing in the pulldown menus for "Assigned to:" o Fixed "CGI Misbehaved" error when running the State Graph function (in Summary page) or the Database Administration Utility in some situations (depending on ptcgi directory permissions). o Fixed bug which sometimes displayed April 1, 1873 as the value for a Date field in Email (when field should have been blank). o Fixed bug which effectively disabled "Logout" function if web server security was applied to pt_admin.exe. Workaround of exiting browser window no longer needed. ============================================================= 14.0 New Features and Changes in ProblemTracker 3.1.2 ============================================================= o Fixed bug which resulted in the Assignee from the previous successful Add operation to be omitted from the subsequent Add page pulldown menu. o Added page in the Setup section in the ProblemTracker Help that discusses configuring International Date support ("Setting International Date Format"). o Fixed CGI crash (resulting in "CGI misbehaved" message) that occurred if there was a database error and the ptcgi directory was configured such that the "effective user" (typically the IIS Anonymous User) did not have write permission (that is NT permissions on the actual ptcgi directory, not IIS (web server) permissions). Added a new pttmp directory (created on installation of 3.1.2) that now contains any error information that the CGIs may write as well as temporary files used in email creation. ptcgi directory now only requires NT "Read" (really read & execute (RX)(RX)) permission. pttmp directory requires NT "Change" permission. Minimum acceptable NT permissions are (RX)(X) on ptcgi and (RWXD)(RWD) on pttmp. To check these, from Windows Explorer, right-click on the directory, click on Properties, click on Security tab, click on Permissions button. o Fixed incorrect handling (display) of & and " characters in the Attachment description field. o BigText and RelNum fields are no longer allowed as SortBy fields since the databases cannot sort by these data types. o Upgrade requirement feature added. The ProblemTracker user is now notified if a database upgrade is required at login time. o Fixed bug in the enforcement of a the "required" property of a pulldown field in the problem record when performing multiple Add operations in a row. It was properly enforced on the first Add, but was not being properly enforced for Adds done immediately after the first Add. o International date configuration format bugs fixed. Default (non-displayed) date format problems fixed. User is now warned about importance of matching the date format/delimiters with a format acceptable to the database in use. o Fixed bug in International date-time support for the Inet (Customer Bug) page. The date/time format was not being properly initialized in the field when the "Now" button was clicked. o History record Invalid field value now always matches the status of its parent problem record. The upgrade process will remap any history records which exhibit this problem. o An Edit Query Results operation in which the user updates a RelNum field now functions correctly (previously resulted in a database error). o The Edit operation when invoked from a Query Result return was missing the File/URL Attachment type specification pulldown. ============================================================= 15.0 New Features and Changes in ProblemTracker 3.1 ============================================================= o Uploadable file attachments added. In addition to existing URL attachments, files from the user's platform may now be automatically uploaded to the server as an attachment. o International date formats now supported. The following formats are now possible (database system permitting). Date Formats - mm dd yyyy dd mm yyyy yyyy mm dd Date Delimiters - "/","-","." (Note: date formats must comply with date formats supported by the localized database version installed on the server system) o Per-product default (initial) assignee is now supported. The default assignee for a problem record is now determined by the State Manager assignments. The default assignee is the State Manager who is assigned to the default state (e.g. Reported) for the product which is specified in the problem report (value of the Product field). For backward compatibility, the global default assignee specified in the User Administration page (check mark in the default assignee column next to one user), will be used if the default state manager (for the selected product) is set to TBD. However, in future releases, the global default assignee will be removed. If, at that point, you wish to continue to use a single default assignee for all problem reports (irrespective of which product is specified in the problem report), you should configure the same user as the State Manager for the default state (e.g. Reported) for all products. o Record locking during Edit/Task/Delete operations added to prevent simultaneous edit of ProblemTracker records. Record locking can be enabled/disabled and applies per user/per record. Stale record locks (e.g. user exits browser) can be cleared by Administrator or original user. o Saved Report Layouts now supports 20 configurable fields instead of 10. o Microsoft Access to Microsoft SQL Server migration procedure has been simplified in ProblemTracker and detailed in the Help documentation. o A "True Delete" operation has been added. This feature can be configured via the "General Preferences" Admin function. When "True Delete" is enabled, deleting a record permanently removes it and all attachments from the database. One history record is left as a reminder of the delete operation. o Documentation upgraded to reflect latest Netscape Enterprise Server edition. o "Reported By" field no longer shows up by default for the externally visible Internet User Add page (Customer Bug Page). o Release Number subfields (i.e. b,c,d) now correctly appear when using the "Format for Printing" option. These previously showed up as blanks in this display page. o In earlier releases, if the database type were changed, the Administrative user was required to logout prior to running additional ProblemTracker operations. o Ampersand character which was incorrectly being mapped in the Saved Report name pulldown list has been corrected. o "DefaultPrintFormat" preference is no longer entered into the database on every login. Previously, the database table which contained this value could increase in size with every login. o Sample Access template databases now match the .CSV template files used for importing into SQL Server databases. o Display bug in the Home Page query has been fixed. This bug appeared when the visibility restriction was set too high and the Home Page query resulted in an empty set return. o Fixed bug which prevented groups alphabetically following the "Users" group from being displayed during an add operation in the "Make Visible to These Groups" field. o Fixed a group name mapping bug which occurred when a group was renamed. o Fixed a bug in the Add operation which prevented FLOAT data types from being saved in the database when a problem record is first added. o Fixed an upgrade bug in going from 3.0->3.05 when using the SQL Server database. Requirements ------------ NetResults ProblemTracker 3 has the following requirements: Client Requirements: o Any platform on which either Netscape Navigator (version 3.0 or greater) or Internet Explorer (version 4.0 or greater) is available. o Netscape Navigator (version 3.0 or greater) 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 (128 MB recommended) o 4 GB Hard Drive (ProblemTracker uses up to 30 MB of hard disk space) o Windows NT 4.0 Workstation or Server, or Windows 2000 Server (Windows NT 4.0 Server or Windows 2000 Server recommended) o Microsoft Internet Information Server 4.0 or 5.0 (recommended), or Netscape FastTrack or Enterprise Web Server version 2.0 or greater. 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 and 2000 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).