2021.1 Service Update

In Workplace Manager, the Device Detail page, as well as the Autotask and ConnectWise Integration pages have been streamlined to make more efficient use of available space.

Device Detail

We've made some enhancements to available report recipients for reports generated through Workplace Online. With this enhancement, if you access those reports from Workplace Manager, using the Manage Team function, you can send the report to any user(s) on the team, as well as any Workplace Manager user. Workplace Online reports accessed by Administrators or Super Administrators on the team can be sent to any user(s) on the team.

We've edited our tooltips for the team shares interface to further clarify the meaning of your available options.

For general information about team and public shares, please refer to Manage project, folder, and file team shares.

When the PDF version option is selected for a public share, the expected behavior is that any files that can be converted to .pdf will be converted, and that the .pdf version will be downloaded. Additionally, any files that cannot be converted to .pdf will be available to download in their original form.

In this issue, when a file could not be converted to .pdf, it was simply not available for download.

The download options now function as designed.

When one's primary Workplace account is a Workplace Manager account, it was in some cases not possible to connect properly to MS Teams. The feature now operates as expected, regardless of primary account type.

For more information about this feature, please refer to The Microsoft Teams integration.

Online editing policies within Workplace were applied by the system to items that had been publicly shared. Online editing policies, however, should apply solely to users, not to public shares.

The issue has been resolved and all public shares now function as designed, regardless of online editing policy settings.

Workplace Server did not recognize some external paths as valid sync paths. The issue has been resolved.

In a single case, restore from backup failed because several files in the backup set were infected with a virus. Those files could not and should not be restored, of course, but in this case they caused the remainder of the restore operation to fail. In our issue resolution, we've ensured that you can always restore from a backup, even when there are virus-infected files in the set; only those files will be excluded from the restore operation.