July 2022 Release Notes

Announcements & Updates
1

What’s new

What’s updated

Policy management

  • Resolved an issue where default policies were not initialized as expected during Kabuto to Syncro migration

Invoices

  • Resolved an issue where Scheduled Invoices may not have run as expected on July 14, 2022
  • Resolved an issue where, in certain circumstances, deleting an item from a multi-page invoice would not update the display as expected

Mac agent

  • Resolved an issue that caused an “Error occurred during the installation” message to appear when installing the Syncro Mac Agent on macOS Monterey 12.3

Windows agent

  • Resolved an issue where the asset thumbnail of an RDC Windows device would not update as expected

Reporting

  • Resolved an issue where setting a scheduled report run date would not save the date as expected
  • Resolved an issue with the Splashtop end user charges report, where contacts were incorrectly listed twice

Alerts and Notifications

  • Resolved a short-duration issue where SMS Text Messages to certain carriers were failing to be received by the recipient

Integrations

  • Resolved an issue where AutoPrinter would not auto-print invoices

Policy Management

  • Resolved an issue where users migrating from Kabuto and/or RepairShopr to Syncro would not have the latest Policy Inheritance model

Scripting

  • Resolved an issue where the mouse cursor would be accidentally hidden when in the Script Editor

Ticketing

  • Resolved an issue where recurring tickets were not running if a worksheet was attached
  • Resolved an issue in the Tickets tab where the Ticket list would show the issue “Type” dropdown as the “issue” instead of the “type”
  • Resolved an issue where certain conditions would cause the ticket comments “Restore previously entered information” to not display as expected
  • Resolved an issue in ticket comments where pasting text would not move the cursor to the end of the pasted item
  • Resolved an issue where, in certain cases, opening the Tickets tab would cause a “500 Error” error message
1 Like