PRNs marked with * do not apply to the NetResults Tracker Online hosted service.
Fixes for issues that only occur in Versions 6.6.0
|When Tracker is installed on Windows Server 2008 (IIS 7.0) or Windows Server 2008 R2 (IIS 7.5) and a user is prompted to change their password via the "force reset password" option or due to a conflict with password policies, an error will occur when the user resets their password, causing them to be unable to login. This has been corrected such that a user can change their password without an error.
|PRN 5172 *
|A log file is kept with entries for each attempt to send an email that fails and for each email where tracing has been enabled (for instance, when sent from the administrative interface for testing email connectivity). In version 6.6.0, an entry was made for all emails even if there was no error and tracing had not been enabled. In version 6.6.1, entries are made only for failures or when tracing is enabled. Also, the log is now limited to a maximum size of 10 MB.
Fixes for issues that occur in Versions 6.5.0, 6.5.1 and 6.6.0
|When the Force Reset Password every X days option is enabled and a user is in more than one workgroup and the user changes his/her password in one workgroup, the date of the password change is not reflected in other workgroups. This has been corrected such that the date of the password change will be reflected in all workgroups in which the user is added.
|When a Text field is configured as the Unregistered User Email with validation enabled and is required on the Add & Submit Pages, the user is forced to enter a value into this field on the Edit Page. This has been corrected such that the user is not forced to enter a value into this field on the Edit Page.
Fixes for issues that only occur in Versions 6.5.0 and 6.5.1
|When a pulldown that is dependent on another pulldown has its default value set so that it is not public, a system error will be displayed when browsing to the Submit Page. This has been corrected such that the default value of a pulldown field cannot be set so that it is not public.
|When a pulldown is involved in a dependency, only the first 100 option menu items are displayed on the Add, Edit, Task and Submit pages. This has been corrected such that all appropriate option menu items will be displayed.
|The Maximum Items shown per search property is not applied when configured on a specific form for pulldowns configured with the "Search" Display Style. This has been corrected such that the field will reflect the form-specific value.
|A system error will be displayed when a user with non-ASCII characters in the User ID enables the Remember Password option. This has been corrected such that the systen error will not occur for User IDs that contain non-ASCII characters.
Fixes for issues that occur in Versions 6.0.0, 6.0.1, 6.5.0 and 6.5.1
|Pulldowns involved in a dependency chain could not be displayed as radio or vertical radio style pulldowns in Safari browser. This has been corrected to allow pulldowns to be displayed as radio or vertical radio buttons.
|When using SQL Server with a Text field as a key field, the Text field content was being truncated in the Link Field search list. This has been corrected such that the Text field content is not truncated.
|Some field properties set at the form level were being overridden when the field was edited at the global level even when the "Use Global Field Properties" option was unchecked. This has been corrected such that the field properties specified at the form level will be properly applied when the "Use Global Field Properties" option is unchecked.
|The text in the Alerts email notification messages has been changed to better reflect the duration of time that has elapsed since the alert was originally triggered.
|In Version 6.0.x, a user is not forced to enter a value into a date field that is configured as required and initialized during the Task operation. This was changed to enforce the required property.
|In some cases, items removed from a link field during the edit or task operations in a workgroup where Record Visibility is enabled were not actually removed. This has been corrected such that the linked items will be removed as expected.
|When a state is renamed, some "previous state" entries in the record history are not properly updated, resulting in incorrect results when running history reports involving previous state values. This has been corrected such that when a state is renamed, the related history entries are updated correctly. Any entries that were not properly updated due to this issue will be automatically corrected during the upgrade.
|In Versions 6.0.0, 6.0.1 and 6.5.1, Float, Integer, Reporter and YesNo fields configured as task fields that were required and not initialized did not enforce the required property. This has been changed such that a user will be forced to enter/change the value so it is different from the default value.
To read about the features (enhancements and fixes) in Versions 6.5.0 - 6.5.1, click here.