NetResults Tracker Fixes

PRNs marked with * do not apply to the NetResults Tracker Online hosted service.

Version 6.7.4

PRN 5981 User password changes could be very slow in a workgroup with a large number of Record History entries (e.g. millions). User account updates that only change a password are now significantly faster for such workgroups.
   
PRN 5988 When Alert settings were configured for newly added records and they were configured with different recipients based on a pulldown value, the email notification message was sent to all recipients specified across all pulldown values instead of the recipient(s) configured for the selected value. This has been corrected such that the email notification will only be sent to the correct recipient(s).

Version 6.7.3

Fixes for issues that occur in Version 6.7.2

PRN 5945 * When simultaneously moving and upgrading a SQL Server workgroup from any previous Tracker version or doing an in-place upgrade of a SQL Server workgroup using Version 6.5.1 or older, an upgrade error would occur. This has been corrected such that the upgrade can be completed without error.

Fixes for issues that occur in Version 6.7.2 and older

PRNs 5938, 5953, 5958 Multiple history entries were logged when a pulldown item or workflow state were deleted and replaced with a new value or when a form's workflow was replaced. This has been corrected such that multiple history entries are not created in these scenarios.

Version 6.7.2

PRN 5873 When querying for records using the "before" option on the Last Updated Date field, then editing the set of query results, only the Last Updated Date was changed in the records. Any other changes entered on the Edit Query Results page were not applied. This has been corrected so that all changes are applied.
   
PRN 5905 When restricted users updated their password in the Preferences section, a system error would occur. This did not affect password updates via the Account Info section. This has been fixed so that Restricted Users can update their password via Preferences or Account Info.
   
PRN 5906 * A workgroup configured with the Authentication option set to something other than the default "NetResults Tracker" option can have user sessions that are not cleaned up when the session timeout occurs. The workgroup configuration has been corrected such that it will have sufficient permissions to clear out the stale user sessions.
   
PRN 5932 A system error will occur when restoring a transition with New State set to "Prompt with <State Group>" or New Assignee set to "Prompt with <User Group>". This has been corrected such that the system error will not occur when restoring a transition with one or both of these options selected.

Version 6.7.1

Fixes for issues that occur in Versions 6.6.1 and 6.7.0

PRN 5721 When using Internet Explorer 10 or 11 with certain Form configurations involving multiple levels of dependent pulldown fields where one of the intermediate pulldown fields is required on the Add, Submit or Task pages, you cannot create or task a record. This has been corrected.

Version 6.7.0

Fixes for issues that only occur in Feature Pack 1 for Version 6.6.1

PRN 5648 When a Pulldown field configured with "Search" as the Display Style is present on a form, the field cannot be set with search criteria to run a standard query and dependencies are not enforced between pulldowns on the Query Page. This has been corrected such that search pulldown fields can be set with search criteria and dependencies are enforced between pulldowns on the Query Page.

Fixes for issues that occur in Version 6.6.1

PRN 5651 Text is not being wrapped in TextArea fields when using Internet Explorer 11. This has been corrected such that the text is wrapped correctly when entered into a TextArea field.

Fixes for issues that occur in Versions 6.6.0 and 6.6.1

PRN 5295 In certain configurations, a system error will occur when attempting to edit a set of records when the Assigned To and Reported By fields are both selected in the Sort By criteria. This has been corrected such that Assigned To and Reported By can both be selected as sort criteria without triggering an error when editing a set of records.
   
PRN 5299 When a form includes a Pulldown field configured as a User Pulldown, a system error will occur when adding a record via the Submit Page. This has been corrected such that a system error will not occur when adding a record via the Submit Page for a form that includes a User Pulldown field.
   
PRN 5631 A set of records cannot be edited while using the Internet Explorer 10 browser. This has been corrected such that a set of records can be edited with Internet Explorer 10.
   
PRN 5639 A system error will occur when attempting to upload an attachment during a Task operation that was initiated from a set of results on the Query Page. This has been corrected such that an attachment can be uploaded without error during a Task operation that when initiated from a set of query results.
   
PRN 5655 When multiple pulldown option menu items have been selected as criteria on the Query Page, the Clear button will not de-select all values. This has been corrected such that the Clear button will de-select all values and select "*" (match any value in the pulldown field).
   
PRN 5656 When using the Internet Explorer 10 or 11 browsers to view a report on the Home, Query or History pages where the field names have multiple rows, overlapping can occur in the column name, making them unreadable. This has been corrected such that the field names will no longer overlap when using Internet Explorer 10 or 11.
   
PRN 5696 Forms are available on the Submit Page despite the Add privilege being disabled for the user group(s) selected in Unregistered User Options. This has been corrected such that only those forms to which the user groups have the Add privilege enabled will be available on the Submit Page.

Fixes for issues that occur in Version 6.5.0, 6.5.1, 6.6.0 and 6.6.1

PRN 5666 When a Text field is configured as the Unregistered User Email with validation enabled, the script used for the validation takes a long time to validate an email address with a large number of characters. This has been changed such that the validation will be done more quickly.

To read about the features (enhancements and fixes) in Versions 6.6.0 - 6.6.1, click here.