Tracker Features

Version 3.6.1

Enhancements

• 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

Fixes

• 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.
• 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.
• 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.
• 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.
• 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).

Version 3.6.0

Enhancements

• 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.
• 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).
• 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.
• 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 (*)
• 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).
• Home page queries have been streamlined to improve performance for systems with large numbers of problem records.
• 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).

Fixes

• 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.
• 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.
• 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.
• 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.

To read about the features in Version 3.5.1 and 3.5, click here.