This document contains the Specification Compliance Manager known issues that were discovered before and since the release of Specification Compliance Manager 22.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 1647078 |
Requests made from Swagger API documentation page fail with error code 401Using the Swagger API documentation page to make requests against the server using the "Try it out" function always fail with error code 401 (HTTP Unauthorized). Although the Swagger API documentation page mentions the how to submit a token as part of the HTTP Authorization Header, the page itself is not configured to submit tokens the Specification Compliance Manager server.
Workaround: Use a third-party REST client for API testing and configure the Authorization Header as described in the Swagger API documentation page.
|
Reported Version: Specification Compliance Manager Server 22.0 Resolved Version: N/A Added: Feb 28, 2022 |
|
| 1837941 |
Typ-only parameter health passes even though coverage metric failsWhen a specification with a typical-only limit is associated with an incomplete dataset with condition coverage below the threshold, the parameter health erroneously shows as passing. The expected health status should be failing since the coverage threshold is not met.
Workaround: Apply a lower-bound (min.) and upper-bound (max.) limit to the specification.
|
Reported Version: Specification Compliance Manager Server 22.0 Resolved Version: N/A Added: Feb 28, 2022 |
|
| 1849626 |
Specification without conditions values will not render when viewing it in compliance details windowSpecifications without any values for one or more condition columns will not be rendered when viewing them in the compliance details window.
Workaround: There is currently no known workaround for this issue. |
Reported Version: Specification Compliance Manager Server 22.0 Resolved Version: N/A Added: Feb 28, 2022 |
|
| 1780276 |
Specification details are not displayed if the category name contains certain Unicode charactersWhen a category name contains certain Unicode characters, attempting to view the associated specifications fails because the specifications are not rendered properly in the "Specifications" view and the "Compliance" view.
Workaround: Remove any Unicode characters from the category name.
|
Reported Version: Specification Compliance Manager Server 22.0 Resolved Version: N/A Added: Feb 28, 2022 |
|
| 1796060 |
Mapping against spec conditions with infinitely repeating values does not matchData containing condition values with infinitely repeating values after the decimal place do not match with the mapped specification condition values.
Workaround: There is currently no known workaround for this issue. |
Reported Version: Specification Compliance Manager Server 22.0 Resolved Version: N/A Added: Feb 28, 2022 |
|
| 1867000 |
Specification name containing forward slash character fails to load when attempting to drilldownWhen attempting to view the compliance details window for a specification with a forward-slash character ("/"), the compliance details fail to load.
Workaround: Avoid using the forward slash character in specification names.
|
Reported Version: Specification Compliance Manager Server 22.0 Resolved Version: N/A Added: Feb 28, 2022 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country