Syskit Point 2022.2.3
This article lists improvements and bug fixes in Syskit Point version 2022.2.3
Start a free trial and tell us what you think.
Product version: 2022.2.3
Build number: 109
Release date: Mar 31, 2022
Get the Latest Version
New to Syskit Point? Get the latest Syskit Point version from Azure Marketplace. Find all steps described in detail in the deployment article.
See detailed step-by-step instructions on how to upgrade Syskit Point in the upgrade article.
Improvements & Bug Fixes
Improved User privacy options when accessed by Collaborators.
While setting up Access, Admin can now select ‘Give Collaborators access to subordinate user's activities’, replacing the previously available option ‘Show audit reports to Collaborators’. This will not be automatically enabled.
If enabled, the Collaborators will be able to view the OneDrive tile, the Analytics & Usage tile, and Audit Log Reports when accessing User details or workspaces they manage.
For more details on Role-Based Access take a look at this article.
Fixed an issue where archiving a Microsoft Team would result in the following error:
Failed to execute Templates backend request ArchiveRequest.Fixed a bug where active Guest Users in Syskit Point were marked as inactive.
After setting up the Guest User Expiration Policy, the assigned User receives an email once a Guest User is marked as inactive.
The assigned User then has a choice whether to Keep or Delete the inactive Guest User.
Due to this bug, active Guest Users were reported as inactive to the assigned User.
Fixed a bug with data column filtering on Overview screens for item selection of more than 10k items. When filtering to select more than 10k items for any column on Overview, it would show that there was no data available to display.
Fixed an issue where HTTP requests used an expired access token instead of requiring a new one. Instead of generating a new access token, Syskit Point would retry action with a previously used token.
Fixed an issue with triggering new hangfire jobs while existing ones are still in progress. If a hangfire job was active for longer than 30 minutes, it was triggered to start again.
Last updated