2020 Release 03
Notes
- The method of storing technician records has changed for Track-It! 2020 Release 03 and later. After upgrading to Track-It! 2020 Release 03, all existing SQL login accounts for groups and technicians that were created during the initial Track-It! installation are removed. These SQL login accounts are no longer needed because we have redesigned the authentication process in Track-It! 2020 Release 03. The upgrade does not delete the Technician User details, however the passwords of all technicians who use Track-It! credentials are reset to system default. After the upgrade is complete, these technicians must change their password at first log in.
The passwords of technicians who use Windows Integrated Authentication (WIA) are not affected by the upgrade. For more information, see the following topics: - If a technician changes the login method from Track-It! credentials to WIA, the associated Track-It! credential becomes invalid and the technician can no longer log in by using the Track-It! credentials.
If you are using a Microsoft 365 email mailbox, then you must configure EWS to process the incoming emails for the following reasons:
- EWS uses Modern Authentication, which is the method that Microsoft recommends for keeping the Microsoft 365 mailboxes secure.
- Modern Authentication supports OAuth 2.0 access tokens and the Microsoft Azure Active Directory Authentication Library (ADAL) to sign in to your Microsoft 365 email mailbox.
This topic contains information about enhancements in 2020 Release 03 of the Track-It! product, and provides instructions for downloading and installing the product update.
For enhancements or features added in earlier releases, see
20.19.xx and 20.18.xx features
.
For enhancements or features delivered in this release in comparison to Track-It! 11.4, see Track-It! 11.4 vs. Track-It! 20xx.
Enhancements
This product update includes the following enhancements:
| Enhancement | Description |
|---|---|
| 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: |
| 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: |
| 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:
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: |
| 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. |
| 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. |
Downloading and installing the product update
For instructions on downloading and installing the update, see Installing.
Comments
Hello. The link don't works : (For more information, see) Upgrading from one build of Track-It! 20xx to another.
Hi, Laurent. Thank you for your input. We have now fixed the faulty link.
Log in or register to comment.