2020 Release 03

Updates to upgrade paths supported

The upgrade paths supported for Track-It! 2020 Release 03 are updated.

For more information, see Upgrading-from-one-build-of-Track-It-20xx-to-another.

Added support for Notes in templates

You can now create, edit, and delete notes in Ticket and Assignment templates. For more information, see the following sections:

• Key considerations
• Notes in templates (2020 Release 03)
• To add, edit, or delete a note in a template (2020 Release 03)

Update to format of Total Time Spent field

The format of the field is updated for Tickets and Assignments in the Ticket form, Assignment form, and the grid view.

For more information, see the following sections:

• Key features for tickets
• Key features and considerations for assignments

Creation of SQL log files by default

When you upgrade to Track-It! 2020 Release 03, the following SQL log files are created by default:

• SMSQLTRC.LOG
• SMSQLERR.LOG

For more information, see To perform an upgrade.

Added Mark Notes as Private field

You can now make all ticket notes public or private by default by using the Mark Notes as Private field. This field is added under Configuration > Application Settings > System Settings.

For more information, see the following sections:

• Configuring-system-settings
• Adding notes to a ticket record
• Adding notes to an assignment record

Update to Work Order Templates

The Migration Tool migrates the template notes that are attached to the Ticket and Assignment templates.

For more information, see Work Order Templates in Data-that-you-can-migrate.

Added IMAP component to LogConfig utility

You can now generate log files for the IMAP component.

For more information, see Viewing-with-log-files.

Update to BCM 20.08 compatibility

Track-It! 2020 Release 03 supports BMC Client Management 20.08. See Software requirements.

Updates to importing users from an Active Directory

If the character length of an Active Directory field exceeds the allocated character length of a Track-It! field, the data is truncated.

For more information, see Key considerations for importing users.

Updates to log in methods

If a technician changes log in method from Track-It! credential to Windows Integrated Authentication (WIA) or Pass-through Authentication, its Track-It! credential becomes invalid.

See Logging-in-to-and-logging-out-of-Track-It.

Updates to log in after upgrade

After upgrading to Track-It! 2020 Release 03, technicians that use Track-It! credentials must change their password when logging in to Track-It! for the first time after upgrade. You must change the password irrespective of the password policy that might be configured.

Updates to log in method for data segregation

You can now log in to the DBUtility with WIA and Pass-through Authentication.

For more information, see Segregating-data-visible-to-groups.

Updates to the DBLogin utility

By using the DBLogin utility, System Administrators can now reset the password of technicians who use Track-It! credentials to the default technician password.

For more information, see Changing the user password by using the DBLogin utility.

Updates to migrated technicians

Migrated technicians that have WIA enabled can log in to Track-It! by using their Windows user account.

For more information, see Data-that-you-can-migrate.

Updates to licenses and licensed users

If the total number of named licenses assigned to technicians are consumed because of overallocation of licenses through the License Update page, then the technicians with a named license cannot log in to Track-It!. For more information, see Licenses.

Updated method of storing technician records

Starting with Track-It! 2020 Release 03, the method of storing technician records has changed.

For more information, see To perform an upgrade.

Added the SQLLoginElimination utility

You can remove the SQL login accounts that were not removed during the upgrade.

For more information, see To perform an upgrade and To remove the SQL login accounts by using the SQLLoginElimination utility.

Updates to known and corrected issues

The known and corrected issues topic is updated.

For more information, see Known-and-corrected-issues.