Syskit Point 2023.1.3
This article lists improvements and bug fixes in Syskit Point version 2023.1.3.
Last updated
This article lists improvements and bug fixes in Syskit Point version 2023.1.3.
Last updated
Start a free trial and tell us what you think.
Product version: 2023.1.3
Build number: 17
Release date: Mar 28, 2023
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.
Want to try out the Configuration Inventory module? Contact us.
See detailed step-by-step instructions on how to upgrade the Configuration Inventory module in the Configuration Inventory upgrade article.
Optimized and improved the Manage Policies screen. The report now loads a large number of workspaces faster. Additionally, custom metadata columns are now visible on the report to help with searching and filtering. The Owners column was also added to the report. It shows the number of owners per workspace, which can be useful when applying ownership-related policies.
Improved the responsiveness of the Policies screen. The screen now better handles devices that use scaling.
Fixed a bug where running the Add to Groups action from the User details screen would fail.
Fixed an issue where the My/All Workspaces screen in Syskit Point Teams app would erroneously show duplicate workspace rows for workspaces with multiple policies assigned.
Fixed an issue with Named Locations and Conditional Access Policies reports where comparison would not work if there are multiple locations or conditional access policies with the same name.
Fixed an issue where Sensitivity labels data was not correctly synced due to breaking changes in Microsoft API response.
Please note! Due to breaking changes in data sync and reports required to support API response changes and multiple objects (for example, conditional access policies) having the same name, expect the following behavior when comparing snapshots created with the new version of Configuration Inventory Module with older snapshots:
Comparing two new snapshots is expected to work in all cases.
Comparing new and old snapshots is expected to work in case there are no objects with the same name in both snapshots.
Comparing new and old snapshots if they contain objects with the same name in either of the snapshots is expected to fail and result in an error due to breaking changes.
